my original point was more that atProto maybe was inspired by the “decentralized distribution of data” that p2p has

In my brain i somehow got the idea that anyone could theoretically access the data without going through bsky and trying to write my guess down i somehow got spun up on that paragraph

sorry if i got you wrong again

i forgot the DIDs
Oh no

thank you

After reading the article i think you might be wrong with this one.

From what i got now is that there are 3 layers

First is storage which can be completly or is decentralised

Then backend/server/application layer which can be bsky or whatever ticktok alternative gets made which is not decentralised

and then user layer/view which depends on the application

What i want to say is that the relay can be exchanged through something else and then entirely including moderation and all

So pro atProto is:

• data seems to be actually decentralised
• applications sharing the data
• everyone gets the data

And pro ActivityPub is:

• more alternatives of the same application/server
• way better control over data (federation & defederation)
• servers interact with each other nativly (atPr seems to let the servers only interact with data)
• more efficient (servers can update clients, in case of at least bsky clients have to ask servers)

pro ActivityPub? (unsure about the technical details)

• moderation? As in shared lists
• able to host by individuals? As in i dont need an compute intensive relay

I think they meant mostly the decentralised distribution of data.
At the end of “Generic hosting, Centralised product development” it says

Even though product development is centralized, the underlying data and identity remain open and universally accessible as a result of building on atproto. Put another way, ownership is clear for the evolution of a given application, but since the data is open, it can be reused, remixed, or extended by anyone else in the network.

So theoretically everyone can access the data but before it reaches the end users it goes through centralised applications like bsky

I know all you guys comment about fediverse(activityPub) is not bsky(atprotocol) but can we enjoy this stupid quote for a moment?

However, if the internet is functioning properly and you have a computer, an internet connection, and an IP address you can host a document on the web.

That statement is so redundant.
“internet functioning properly” = “an internet connection”
and you cant have an internet connection without an ip adress. On Lan you may have the option to let the device decide BUT it still needs one!

I dont think the entire article is bad or something but let me have my nitpickings.

• its too long, and with that i mean half the thing is 3 concepts that could have been explained shorter
• too many fancy words (i am not a native & my reading comprehension gets worse at all those extravagant marketing words, so thats my error)
• not including the one picture of the protocoll/network topology. I needed to keep that in my brain to not get confused Masto Post with Topology
• that one paragraph at the post start but can happen to anyone so its simply hilarious

Yesterday i managed to successfully host a simple html safely (its more of a network test)
The path is nginx->openwrt->router to internet Now i only need to:

• backup
• set up domain (managing via cloudflare)
• set up certificates
• properly documentbthe setup + some guides on stuff that i will repeat

and then i can throw everything i want on it :D