If you're into this stuff, you might enjoy my "Twitter as a CDN tool", here's pong in a single Tweet: https://twitter.com/rafalpast/status/1316836397903474688 h

If you're into this stuff, you might enjoy my "Twitter as a CDN tool", here's pong in a single Tweet: https://twitter.com/rafalpast/status/1316836397903474688 https://twitter.com/rafalpast/status/1316836397903474688 > Easy for the client, easy for the server, easy to share, only downside that I see is that it makes things a bit obtuse for users There are more downsides: - processing and creating payload can be harder are you're passing plaintext w. ca. 30% size increase on average - base64-encoded assets (e.g. SVGs) would cause a huge performance drop in WebKit (this probably has improved since the last time I ran benchmarks). - since you're encoding content and not its location, you can't easily update the underlying resource (hence to update my version of Pong, I'd need to create a new unique URL). IIRC IPFS suffers (used to?) from a similar issue - not an issue now, but still was 1-2 years ago: some browsers would allow only for 2 or 4kb of text in URL