so even then, encrypted with...?
Post by chris co
yeah that was with a twetch key of course
What the chain says
- Block
- 963 585
- Time
- 2026-08-23T15:04:06Z
- Signer
- 1Pif9p9Cdd7mngkkU1CUZ3RvmT5ToP3xcE
- App
- twetch
- Type
- reply
- Content type
- text/markdown
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
1Pif9p9Cdd7mngkkU1CUZ3RvmT5ToP3xcE UnverifiedReplies (3)
so same issue
"that would mean those posts could only be seen on twetch"
yes. which is fine with me. twitter with micropayments. but i think the original idea of "tweets etched on chain" would be lost, as whatever is etched on chain with the twetch encryption key would only be consumable through the twetch server. we would then need a twetchetch for twetches etched on chain.
yep and the future of twetch is not guaranteed
but then again the future of any on chain blob data
is not guaranteed
paywalls are a bad direction
especially if they do not work properly
as in keep the data private till paid
and only viewable to those who have paid
would be better to focus on more fun stuff imo
that doesn't try to be something it is not