Content pfp
Content
@
0 reply
0 recast
0 reaction

Phil Cockfield pfp
Phil Cockfield
@pjc
I thought FC/Warpcast content was visible publicly (ReadOnly) without an account, and an account was only necessary to write to the protocol. But when I shared a post recently, I got a report back that they couldn't see the content - and when I open the example link below in an incognito chrome window, indeed nothing is shown. Is this intended or a new change? I'm sure I've shared public links to non-FC people before. Can someone help update my mental model so I can understand how this is working now, please? https://warpcast.com/july/0xd0b1559c
4 replies
2 recasts
13 reactions

Gabriel Ayuso pfp
Gabriel Ayuso
@gabrielayuso.eth
bug - team looking into it.
1 reply
0 recast
4 reactions

JB Rubinovitz ⌐◨-◨ pfp
JB Rubinovitz ⌐◨-◨
@rubinovitz
Also wondering about this because sometimes Readwise can save post content and sometimes it can’t
0 reply
0 recast
1 reaction

adrienne pfp
adrienne
@adrienne
I sent a warpcast link to a friend recently and they said they couldn’t see the cast and it was asking them to create an account I didn’t verify tho
1 reply
0 recast
3 reactions

torii.base.eth pfp
torii.base.eth
@torii-stories
Following! I know I have sent casts to non users in the past and they were able to read just fine. Hope this gets fixed soon, and it is indeed a bug—a bug they intent to squash
0 reply
0 recast
1 reaction