Live data from Hacker News

At Protocol: Building the Social Internet

atproto.com

21–30 of 43 posts

Re: At Protocol: Building the Social Internet

#22

I think it would be interesting if the file servers had read/write/list/delete permissions on files. For both groups and users. It would mean the public stuff could see your files but private projects could exist. Eg. Maybe I don't want my At Protocol version of Figma making all my drawings public. If they could be shared in a group (anyone in a list in that folder or whatever). Maybe this is coming, but would intere…

The ability to make information private fundamentally conflicts with how ATProto is designed. All records have to be sent to all Relays and AppView nodes on the network to provide a "global view" of the network. So there's no way to keep records private without locking out some user's servers from viewing them, and since AppViews are centralized indexing services, they won't function without being able to see the entire network.

Re: At Protocol: Building the Social Internet

#24
post #19

The summary of what this is about is: "Atproto is a big-world open social protocol. Users publish JSON records into repositories. The changestreams of those records then sync across the network to drive applications." It's too bad that information isn't on the front page. You have click "GET STARTED" and scroll down

Is it really, at the end of the day, a server that serves your data over JSON (aka a social media post) and offers feeds (ala an RSS model) of the changes of that data and provides services for discovering the schema of that JSON (aka its lexicon)?

Re: At Protocol: Building the Social Internet

#27

I think it would be interesting if the file servers had read/write/list/delete permissions on files. For both groups and users. It would mean the public stuff could see your files but private projects could exist. Eg. Maybe I don't want my At Protocol version of Figma making all my drawings public. If they could be shared in a group (anyone in a list in that folder or whatever). Maybe this is coming, but would intere…

The ability to make information private fundamentally conflicts with how ATProto is designed. All records have to be sent to all Relays and AppView nodes on the network to provide a "global view" of the network. So there's no way to keep records private without locking out some user's servers from viewing them, and since AppViews are centralized indexing services, they won't function without being able to see the ent…

Yeah, apps wouldn't be able to only listen to the firehose.

There are some proposals for private files. However, I'm outside the AtProto world so not sure what exactly the suggested implementations are. I just hope they give enough control.

I think the technology could potentially be used for way more than microblogging. I would love to use webapps that store the data on my devices and share it with specific people. The data and access under my control.

[1]: https://dholms.leaflet.pub/3mhj6bcqats2o

Re: At Protocol: Building the Social Internet

#28
post #18

I didn't understand what this was until I did some more digging around. Apparently, it's a decentralized way to interact with social media. A protocol created by Bluesky which allows social networks to communicate directly. This is similar to how different email clients like Gmail and Outlook can send messages to each other.

Yes, but to nitpick slightly: the focus of this protocol is to let people use their own data with social media sites. It might not matter much while the site is active, but separating data ownership from the site makes moving platforms in the future much, much more feasible. Data like posts, friends lists, block lists, likes, comments, etc. Obviously, this was informed by people's experiences with Twitter, especially…

though technically your data lives within Bluesky's servers (kind of like your money lives in a bank) so in some ways it's still the bank's money though it's allotted to you

Re: At Protocol: Building the Social Internet

#30
post #28
post #18

Earlier quoted context omitted.

Yes, but to nitpick slightly: the focus of this protocol is to let people use their own data with social media sites. It might not matter much while the site is active, but separating data ownership from the site makes moving platforms in the future much, much more feasible. Data like posts, friends lists, block lists, likes, comments, etc. Obviously, this was informed by people's experiences with Twitter, especially…

though technically your data lives within Bluesky's servers (kind of like your money lives in a bank) so in some ways it's still the bank's money though it's allotted to you

Actually your data does not live in Bluesky’s servers if you don’t want it to.

Mine doesn’t.

At least another 20-30,000 people’s doesn’t either.

Post reply on HN