8 ms·
This article goes into a lot of detail, more than is really needed to get the point across. Much of that could have been moved to an appendix? But it's a great
by skybrian 10mo ago
This article goes into a lot of detail, more than is really needed to get the point across. Much of that could have been moved to an appendix? But it's a great metaphor. Someone should write a user-friendly file browser for PDS's so you can see it for yourself.
I'll add that, like a web server that's just serving up static files, a Bluesky PDS is a public filesystem. Furthermore it's designed to be replicated, like a Git repo. Replicating the data is an inherent part of how Bluesky works. Replication is out of your control. On the bright side, it's an automatic backup.
So, much like with a public git repo, you should be comfortable with the fact that anything you put there is public and will get indexed. Random people could find it in a search. Inevitably, AI will train on it. I believe you can delete stuff from your own PDS but it's effectively on your permanent record. That's just part of the deal.
So, try not to put anything there that you'll regret. The best you could do is pick an alias not associated with your real name and try to use good opsec, but that's perilous.
- DustinBrett 10mo agoI think that is the general style of overreacted.io posts.
- seridescent 10mo ago> Someone should write a user-friendly file browser for PDS's so you can see it for yourself. https://pdsls.dev/ https://pdsls.dev/ can serve this purpose IMO :) it's a pretty neat app, open source, and is totally client-side edit: whoops, pdsls is already mentioned at the end of the article
- danabramov 10mo agoMy goal with writing is generally to move things out of my head in the shape that they existed in my head. If it's useful but too long, I trust other people to pick what they find valuable, riff on it, and so on. >Someone should write a user-friendly file browser for PDS's so you can see it for yourself. You can skip to the end of the article where I do a few demos: https://overreacted.io/a-social-filesystem/#up-in-the-atmosphere https://overreacted.io/a-social-filesystem/#up-in-the-atmosp.... I suggest a file manager there: >Open https://pdsls.dev https://pdsls.dev. [...] It’s really like an old school file manager, except for the social stuff. And yes, the paradigm is essentially "everyone is a scraper".
- skybrian 10mo agoThanks! I saved a link to pdsls. I think there's room for improvement in making the UI user-friendly; maybe I'll try it someday.
- danabramov 10mo agoThe devs are responsive to feedback if you mention @pdsls.dev on Bluesky! I often point out small issues and they get fixed the next day.
- ascorbic 10mo agofwiw, I don't agree. These detailed articles are excellent.
- ryanjshaw 10mo agoThis was a great article. Have you got any thoughts on Farcaster and its Snapchain?
- verdverm 10mo agoPrivate data will come to ATProto, it's not a finished protocol
- ximeng 10mo agoWhat’s the plan for this? Sharing with a specific group (DM, group chat, feeds from people you follow) are critical to social media.
- danabramov 10mo agoSee https://www.pfrazee.com/leaflets/3lzhui2zbxk2b https://www.pfrazee.com/leaflets/3lzhui2zbxk2b for some recent thoughts from a team member.
- verdverm 10mo agoBnewbold's comment on GitHub is still the best resource. It's far more specific in scope and details. Paul's note is more theoretical / philosophical
- ximeng 10mo agohttps://github.com/bluesky-social/atproto/discussions/3363 https://github.com/bluesky-social/atproto/discussions/3363 - maybe this one?
- verdverm 9mo agoyes, that is the one everyone is using as a guiding light for where we think Bsky is headed for their private data needs, which is group-shared / not e2ee because key mgmt is an unsolved problem at scale. They need to support creators with subscriber only content. E2EE will emerge from the messaging space first, i.e. Signal / MLS like Bsky is likely to put out a short-term gap filler this year for personal-private data, which kind of already exists today for Bsky only. This work would make that same feature in the per-user repo available to all apps. Right now it's hard coded to a specific NSID and single db row
- swyx 10mo ago> So, much like with a public git repo, you should be comfortable with the fact that anything you put there is public and will get indexed. whats the sota on atproto encryption dan? just publish encrypted stuff with sha 256 and thats it?
- danabramov 10mo agoAFAIK nothing special for it at this point, so whatever you would do with a public cleartext broadcasting platform.
- extraduder_ire 10mo agoYou can use pdsfs[0] to mount a user's pds locally using FUSE read-only. It's mentioned in the blogpost. I remember seeing a tool posted for mounting them read-write, if you sign in, but can't remember where to find it. 0: https://tangled.org/oppi.li/pdsfs https://tangled.org/oppi.li/pdsfs