It was by the largest (by a fair margin) socialist-aligned subreddit, but in practice it was like 60% shitposts. Was originally associated with the eponymous podcast, but the hosts have repeatedly said they disliked it.
aeshna_cyanea
joined 3 months ago
they were originally refugees from the reddit ban of r/chapotraphouse (which, while cringy, was not nearly as bad as r/the_donald that got banned in the same wave. but the reddit admins had a thing for being "fair and balanced")
yep literally this. don't most routers nowadays have a dns server with a hosts file you can edit?
Did you know we have these things called computer files that can store information. There's even one in your router specifically for storing IP addresses
This was me up to about age 24. I just read books instead
These guys seem cool but they're not the archive.org from the op article
Yes, this is the strongest argument against it and the biggest flaw. They keep saying in interviews that they are treating their future selves as adversaries and they do open source most everything but I would be a lot happier if the protocol development was spun off into a separate org from the for profit service. If it dies, this will be what killed it. But I hope they make it (by it I mean the tools for everyone else to make the ecosystem).
Yes, and I've been yelling at them about the problem of scaling down for a while, since the same "relay" service needs to be both a firehose and a full mirror. This requirement (and thus scalability) of running a relay is becoming a big problem even for the main devs. According to them however you can mitigate this to a reasonable amount for a home lab (~8 cores, 16gb ram, ~2Tb ssdl) if you simply don't store any backlog and just retransmit posts https://bsky.app/profile/why.bsky.team/post/3lbjdux6ubc2f
This is what they're doing internally to manage the load and are also working on implementing relay sharding/scoping to let you just index a small slice of the network, which should eliminate the problem. https://github.com/bluesky-social/atproto/discussions/3036 and here's someone implementing a proof of concept third party version https://bsky.app/profile/pet.bun.how/post/3lbwnx2rxxs2o
It's true that the main devs' priorities are building the large scale parts first and then worrying about downscaling, the whole point was always to replace twitter and work at a similar scale, which requires hard tradeoffs. I do worry that they'll run out of money before they can do the work to let the ecosystem become sustainable by itself.
But I have faith (for now) because they have people I know from when they worked on secure-ssb and dat protcols, which are truly decentralized but never took off for other reasons.
Thats the opposite of what I said. You can use the same data with multiple services at the same time, in fact this is already possible. The whole thing would be kinda pointless otherwise.
Oh I thought you meant decentralized currency. What you're describing is just standardized storefront apis though, the vendors don't need to talk to each other (federate) for it. unless i'm missing something
The entire point is that your pds can interact with multiple "instances" of bluesky or whatever other apps people build on the protocol.
For example there is a reddit/hn clone that people can post on (keeping their same identity) when the official bluesky service goes down. The reddit clone is fully independent from the twitter clone, but they use the same protocol and (unlike AP) the same hosting and authentication infrastructure.
Whereas on Lemmy and mastodon, my accounts are totally separate. And unlike AP, your data lives on your own pds and is never hostage to the owner of the instance that actually runs the load bearing interactivity. If they become compromised or shut down you can switch to another. No cooperation from the old owner required (unlike activitypub).
view more: next ›
If you disapprove of internet companies caving to authoritarian politics, I have bad news for you about Yandex