Tom Brown🏒
@herestomwiththeweather.com
Software developer and beer league hockey player
[bridged from https://herestomwiththeweather.com/ on the fediverse by https://fed.brid.gy/ ]
[bridged from https://herestomwiththeweather.com/ on the fediverse by https://fed.brid.gy/ ]
Reposted by Tom Brown🏒
back in 2023 when Threads launched, a friend working there said Zuck pushed everyone to create a mastodon-compatible twitter clone so they could pitch it as an open source API to distract the US govt from breaking Meta up, which ultimately worked
November 18, 2025 at 11:03 PM
back in 2023 when Threads launched, a friend working there said Zuck pushed everyone to create a mastodon-compatible twitter clone so they could pitch it as an open source API to distract the US govt from breaking Meta up, which ultimately worked
Reposted by Tom Brown🏒
But on a related topic, if the ATProto would start supporting WebFinger based discovery rather than just its own limited .well-known path, then some of the stuff would be gotten for free
(And this is very much a non-IndieWeb answer as WebFinger is not in line with the general approach of IndieWeb)
(And this is very much a non-IndieWeb answer as WebFinger is not in line with the general approach of IndieWeb)
Not sure why #ATproto uses /.well-known/atproto-did to discover handles rather than using #WebFinger like #Mastodon and having a rel-self to a did:plc URI
Feels needless to have two discovery layers? And would have enabled the same handle resolution for both Mastodon and Bluesky?
Feels needless to have two discovery layers? And would have enabled the same handle resolution for both Mastodon and Bluesky?
Mastodon uses a rel-self, type-application/activity+json link to the absolute URL of the user (/users/foo)
@atproto.com / @bsky.app could have done the same and had a rel-self link to the did:plc URI (eg. did:plc:z72i7hdynmk6r22z27h6tvur)
Reference for #ATproto docs: atproto.com/specs/handle...
@atproto.com / @bsky.app could have done the same and had a rel-self link to the did:plc URI (eg. did:plc:z72i7hdynmk6r22z27h6tvur)
Reference for #ATproto docs: atproto.com/specs/handle...
November 11, 2025 at 9:54 PM
But on a related topic, if the ATProto would start supporting WebFinger based discovery rather than just its own limited .well-known path, then some of the stuff would be gotten for free
(And this is very much a non-IndieWeb answer as WebFinger is not in line with the general approach of IndieWeb)
(And this is very much a non-IndieWeb answer as WebFinger is not in line with the general approach of IndieWeb)