you can figure this one out w/ a desktop and an afternoon of cryptanalysis... just track the % and relative tx sizes before and after twetch was created
wouldn’t a metanet just be a surveillance network that annotates all the other transactions on chain (at least w/ an init tx followed by categorization txs) : @1 + @5
identifying an automation would be as simple as taking tx constants re: string length of various identifiers and dividing them over the metanet txs sizes
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
18ZWnrQ2ijRHUCKfWMot5iPCEGp4mWe2gL Verified@2 : if $I was CSW $I would prune twetch txs after replaying them in a sub system that gives CSW royalties later when others can’t sync Twetch on chain w/o paying additional tolls
would also include GBs worth of noise every time $I mine a block to clog bandwidth and drives of nodes who try to sync w/o pruning
@2 : you shouldn’t take a synced / unpruned copy of the chain on a hard drive through border security for example as it could cause you to be arrested for kid stuff
When data ownership is even more robust, e.g. encrypting everything on Twetch, users can decide what Twetch can display and can’t display by revoking access to the keys they provide to Twetch to decrypt posts.
This isn’t very far away.
@9962 lets do it