Content
@
https://warpcast.com/~/channel/live-the-same
0 reply
0 recast
0 reaction
kevang30.base.eth
@kevang30.eth
Let's see how our friend @artlu tool works! 😉 🔥 9da1e198a09f1850337e427a389978a108950d37e0e21a68661c7a18512e965c @hankmoody @wanderlustmom @amartos @noedmb @eljuniordiaz.eth (mute the phrase '!sassy1' to stop seeing SassyHash 💅 in your feed)
3 replies
2 recasts
8 reactions
WanderlustMom
@wanderlustmom
53b786f79695adde31f1f033c45c226245ed35df117d7ce42edae579e6a542c7
2 replies
0 recast
1 reaction
artlu 🎩
@artlu
can I help you debug why this isn't decoding? we can diagnose in private DC or in a public thread... would help me to know if you are on desktop (Win or Mac) or mobile (iPhone or Android), and if you noticed any differences when the encoding works and when it doesn't work tyty
4 replies
0 recast
2 reactions
Haole
@haole
what's the bug? btw can i set only certain people to decode?
1 reply
0 recast
1 reaction
artlu 🎩
@artlu
Bug is most likely on the SassyHash side, where some network paths strip messages of credentials, and my services think it's a non-credentialed message like a DDOS attempt. Don't think it affects Recaster much, but that may just be due to relatively light usage. As for decoding, yes! Wherever you cast, the read permissions reflect the write permissions of that space: - in Main, everyone can decode - in an open channel, anyone can decode - in a members-only channel, members only can decode 93effc0b57c68de8ad48b36adcc963efa4e36b1ccc698c32ca845ba9cd2c0eae (mute the phrase '!sassy1' to stop seeing SassyHash 💅 in your feed)
0 reply
0 recast
3 reactions
