Live data from Hacker News

ATProto spaces: A new extension to ATProto that enables non-public data

atproto.com

11–20 of 38 posts

Re: ATProto spaces: A new extension to ATProto that enables non-public data

#11
post #3

Earlier quoted context omitted.

"space" is just a common English term for this kinda thing, as you can see in any dictionary ever: Collins: "A particular kind of space is the area that is available for a particular activity or for putting a particular kind of thing in." Cambridge: "an empty area that is available to be used" why do you think Twitter called them spaces in the first place?

> "space" is just a common English term for this kinda thing Isn't that exactly the problem? It's like using "node" for something in your program's design, or "tree" or "type" whatever. Usually it's better to find a more specific name that communicates the intent even better, or at least less common name, as it'll inevitably will clash with something else, and by then you wish you'd name it differently than every oth…

It's funny you said "node" because the first thing it reminds me of is NodeJS. I'll admit I don't know why they called it node. But I have never seen anyone bothered by it either.

Re: ATProto spaces: A new extension to ATProto that enables non-public data

#12
post #3

Earlier quoted context omitted.

"space" is just a common English term for this kinda thing, as you can see in any dictionary ever: Collins: "A particular kind of space is the area that is available for a particular activity or for putting a particular kind of thing in." Cambridge: "an empty area that is available to be used" why do you think Twitter called them spaces in the first place?

Not saying the word doesn't make sense, questioning it's use from a branding/identity standpoint. It's already taken/associated with an aspect of another network that like it or not is still in proximity to whatever AT proto/Bluesky are developing. Just call it something else! ("hardest thing in computer science is naming things" etc etc)

[deleted]

Re: ATProto spaces: A new extension to ATProto that enables non-public data

#13

So is this now just, like, a server?

ATProto is basically old web where you host your own content and advertise an RSS feed except there are aggregators that make everyone’s feed into one big firehouse that you can filter down to content you want to follow, and then view the content with whatever client you want (AppViews which are also servers but they can be pointed to a feed made up of others servers, like a Web Ring!)

I could hate on them for reinventing the wheel but the cryptographic stuff they do with signed merkle trees is pretty clutch, it’s a tricky problem to untangle public key identities from domains so you can migrate your content without losing your identity. There’s still not a good flow for that but at least there’s the groundwork done.

Re: ATProto spaces: A new extension to ATProto that enables non-public data

#14
post #3

Earlier quoted context omitted.

"space" is just a common English term for this kinda thing, as you can see in any dictionary ever: Collins: "A particular kind of space is the area that is available for a particular activity or for putting a particular kind of thing in." Cambridge: "an empty area that is available to be used" why do you think Twitter called them spaces in the first place?

> "space" is just a common English term for this kinda thing Isn't that exactly the problem? It's like using "node" for something in your program's design, or "tree" or "type" whatever. Usually it's better to find a more specific name that communicates the intent even better, or at least less common name, as it'll inevitably will clash with something else, and by then you wish you'd name it differently than every oth…

If I keep it vague I can do things like:

    let { type } = customer;

    type = “premium”;

    setCustomer({ type }); 
It’s only slightly more verbose if I named the variable:

    customerType 
In many cases, the data I’m dealing with is outside my name control and commonly has something like { type } (e.g. )

Re: ATProto spaces: A new extension to ATProto that enables non-public data

#16
post #10

So is this now just, like, a server?

No. Data is stored on your PDS and no one else can shut it down, there is no central server. The only difference from public atproto is when you ask someone else PDS for records in a space you need a token signed by the space authority to show that you have permission to read them.

So your PDS is a central server?

Who would I ask for my private space records but myself?

Re: ATProto spaces: A new extension to ATProto that enables non-public data

#18

Earlier quoted context omitted.

That's directly addressing vendor lock in

A server protocol. Like HTTP.

Sure they are linked by this general category of app layer service protocols, but they are different. ATProto afaik is a bit like activitypub, in which you define a protocol on top of the state representation in a way you can transfer it reliably across instantes that implement them.

It's like http in which you can achieve the same using http, but http isn't prescriptive about any such behaviours, which these protocols address

Re: ATProto spaces: A new extension to ATProto that enables non-public data

#19
post #10

Earlier quoted context omitted.

No. Data is stored on your PDS and no one else can shut it down, there is no central server. The only difference from public atproto is when you ask someone else PDS for records in a space you need a token signed by the space authority to show that you have permission to read them.

So your PDS is a central server? Who would I ask for my private space records but myself?

Think less "private" and more "protected." Like Patreon subscriber perks, paywalled content, or just someone who only wants certain people to see what they post.
Post reply on HN