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

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
2 replies
0 recast
3 reactions

Phil Cockfield pfp
Phil Cockfield
@pjc
FYI Adrienne - it was a bug, now fixed (thanks to @gabrielayuso.eth) Public read-only casts are open for business - pulling in the wider world not yet assimilated into the borg! (or anti-borg, depending on your vantage point).
1 reply
0 recast
1 reaction

Phil Cockfield pfp
Phil Cockfield
@pjc
Feels like new behavior, right? I'm sure this worked publicly before...and from a protocol growth perspective, it would make sense to have it visible. I wonder if this was some kind of move to stop crawling/scraping by other networks?
1 reply
0 recast
0 reaction