i was like 'huh, ok, i can sorta see where this is coming from' but then you start reading this and you're like ok yeah that's definitely a joke:
I am pretty sure this is one of the most masterful trolls i have ever seen.
i just fucking hate the smug tone IP rentiers take like they are the responsible adults in the room protecting Truth and Artistry when in reality they are just the fucking footservants of extraction that make all cultural work so precarious.
Always have to remember that when they talk about "vibrant" culture they mean being able to pay $75 for tickets to see an ailing Dave Matthews remind them of the feeling of freedom that only being able to wear a light pastel button-down shirt once a week can deliver.
hahahahahaha go fuck yourselves IP barons. this is almost as good as 'you wouldnt download a car'. Also love the 5 largest publishers in the world not even bothering to change the default wordpress favicon
peers could do an incentiveless bitswap-like thing and set aside some amount of space for randomly rehosting 16kb chunks of other pdfs in swarm. they don't even need to know what they have and the seeding peer doesn't need to tell.
leecher only requests random subtree hashes, seeders only respond to and only announce subtree hashes. contents of subtrees cannot be checked for IP and are not illegal to have. seeders can automatically share all the PDFs in their libraries without needing to upload to a tracker/make torrents because it's just content addressed. allows for multiple pdfs for a single doi.
interesting point i just read posted on some internet website somewhere: there’s no app ecosystem with something comparable to the web’s iframes.
that is, the ability for an app to define a piece of itself that other apps can easily embed inside of themselves.
i think that was tried tho- it was called OLE and OpenDoc and were generally considered disasters.
but then, why are iframes so effective where OLE failed?
"Indigenous-led blockade outside of the Department of the Interior demanding Biden declare a #ClimateEmergency and stop approving all fossil fuel projects, including leases, exports, plastic plants, and pipelines." (https://nitter.it/https:IkiyaCollective/status/1554045777994997761)
or one that was more like a blogpost with comments/replies where you would have more of an expectation for a thread.
for some reason, i think it's the chronological feed as well as the absence of indication that there is a reply in the interface i use that make me feel like toots are more solitary. I also feel like this is one of the places where federation and variation between instances in stuff like character limits matters - eg. a more longform instance/program would have less of an expectation of threaded communication
not IPFS specifically, necessarily, just thinking about a joint browser/client/server #P2P thing yno.
ok i just had the whackiest idea for a browser/client p2p idea. so most of the time that I see it, #IPFS uses the HTTP gateway that has to re-serve the files anyway, i think? but could you also just include the hash of a WASM/JS IPFS client and then have the HTTP server just serve and check the hash of the code payload against the url component lol. you could do it with a http ? query for no loss of backwards compatibility
also notice how they right indent their signatures. the letter writing style and expectations of etiquette are very strong. reminds me of the harnad experience where flaming was still "contact the admin and try to get you banned" in 1987.
https://social.coop/@jonny/108437655069057827
interesting lil linguistic note, they were already using the collective "randoms" to refer to random people, something I thought was much more recent.
then, as now, the tradeoff seems to have been convenience vs. privacy, and the tone is exceptionally angry given the norms of email at the time.
systems/neuro & digital infrastructure, rawdog meatspace cooperator eating digital vegetal
toots containing !/ are crossposted to/from @json_dirs@twitter.com