Fediverse

32412 readers

1358 users here now

A community to talk about the Fediverse and all it's related services using ActivityPub (Mastodon, Lemmy, KBin, etc).

If you wanted to get help with moderating your own community then head over to [email protected]!

Rules

Posts must be on topic.
Be respectful of others.
Cite the sources used for graphs and other statistics.
Follow the general Lemmy.world rules.

Learn more at these websites: Join The Fediverse Wiki, Fediverse.info, Wikipedia Page, The Federation Info (Stats), FediDB (Stats), Sub Rehab (Reddit Migration)

founded 2 years ago

MODERATORS

[email protected]

Great ATProto blog post on the reasoning behind their design architecture (atproto.com)

submitted 1 day ago by [email protected] to c/[email protected]

55 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 1 day ago* (last edited 1 day ago) (1 children)

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

[–] [email protected] 3 points 19 hours ago* (last edited 19 hours ago) (2 children)

But what about the DIDs, the things used to actually identify accounts within the ATproto ecosystem:

But Bluesky has developed its own DID method, did:plc. Today, did:plc stands for "Public Ledger of Credentials", however it originally stood for "Placeholder DIDs", with the hope of replacing them with something else later. The way that did:plc works is that Bluesky hosts a web service from which one can register, retrieve, and rotate keys (and other associated DID document information). However, this ledger is centrally controlled by Bluesky.

It's literally not possible to have a functional PDS without registering with a Bluesky server and they maintain indefinite control over the ledger. All your data is tied to this DID, it's how the entire protocol is designed to identify stuff, how decentralised is your data if it's dependent on Blusky (the company) assigning you an identity?

[–] [email protected] 2 points 5 hours ago* (last edited 5 hours ago)

This is false, they support did:web which ties your identity to ownership of a DNS name (which is its own can of worms, but not controlled by bluesky like PLC).

Unless you mean that you still have to register your pds it to get indexed by the relay, so people can read your posts without querying your server directly (which is possible but discouraged). This is actually an advantage over mastodon/activitypub however, your personal pds will not crash if a post goes viral (unlike a personal mastodon instance).

[–] [email protected] 1 points 17 hours ago (1 children)

i forgot the DIDs
Oh no

[–] [email protected] 2 points 5 hours ago

They support did:web too if you don't like did:plc