Am I correct that with #ActivityPub, any org can run a server with their name in the domain and each member getting their own username, but using #ATproto, every individual would need to get their own domain name?
-
Am I correct that with #ActivityPub, any org can run a server with their name in the domain and each member getting their own username, but using #ATproto, every individual would need to get their own domain name? I guess subdomains are possible. And those would probably just redirect, the structure and costs meaning they probably don't actually represent an app view or PDS or whatever?
-
Am I correct that with #ActivityPub, any org can run a server with their name in the domain and each member getting their own username, but using #ATproto, every individual would need to get their own domain name? I guess subdomains are possible. And those would probably just redirect, the structure and costs meaning they probably don't actually represent an app view or PDS or whatever?
@wjmaggos
- atproto requires a DNS name (and the TXT record points to a DID which points to a PDS)
- activitypub requires a URI (which in most cases you just HTTP GET directly, optionally following HTTP redirects)
- you could satisfy both by assigning subdomains or letting users bring their own domainso alice.social.example and https://alice.social.example could be used ~equivalently, but https:// social.example/alice wouldn't work as an atproto identity.
-
R relay@relay.an.exchange shared this topic
-
@wjmaggos
- atproto requires a DNS name (and the TXT record points to a DID which points to a PDS)
- activitypub requires a URI (which in most cases you just HTTP GET directly, optionally following HTTP redirects)
- you could satisfy both by assigning subdomains or letting users bring their own domainso alice.social.example and https://alice.social.example could be used ~equivalently, but https:// social.example/alice wouldn't work as an atproto identity.
I don't understand your equivalent example.
as I understand it, AP would use @alice@example.com while AT would use alice.example.com. then bob and carol etc.
AP would have one server for all the users, both data store and how they post/read etc. would AT require a different PDS for data for each account and then have most people still use bluesky or maybe blacksky for posting/reading etc? I know they could run their own app view but the cost would be much higher than an AP server etc.
-
I don't understand your equivalent example.
as I understand it, AP would use @alice@example.com while AT would use alice.example.com. then bob and carol etc.
AP would have one server for all the users, both data store and how they post/read etc. would AT require a different PDS for data for each account and then have most people still use bluesky or maybe blacksky for posting/reading etc? I know they could run their own app view but the cost would be much higher than an AP server etc.
@wjmaggos oh, the @alice@example.com you see is not the real identifier, it's a third thing altogether that usually forwards to a URL, via something called WebFinger (which mastodon requires, but activitypub doesn't require it).
AP uses the same URLs you would be able to load in a web browser because it's a web spec. So for example you are https://liberal.city/users/wjmaggos as far as AP is concerned. You *could* be https://wjmaggos.liberal.city/ but mastodon doesn't currently support that.
-
R relay@relay.mycrowd.ca shared this topic
