mastodon.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
The original server operated by the Mastodon gGmbH non-profit

Administered by:

Server stats:

383K
active users

Chris Trottier

For what it's worth, people on aren't hostile to .

They want to read Mastodon posts.

It's incredibly sad that people on Bluesky can't talk to Mastodon and vice versa.

@fediversenews

@atomicpoet@mastodon.social maybe they should add AT protocol support to mastodon

@atomicpoet@mastodon.social they don't seem to want to support anything other than activitypub.. maybe i should ask glitch-soc

@atomicpoet @fediversenews if only the community #Bluesky serves had some say in the decisions made about whom their instance can talk to. I wonder what such a system would look like.

social.tummyacid.netkitchen

@atomicpoet @fediversenews

Has anybody performed a technical review of ATProtocol? As far as I'm concerned, Dorsey can claim "decentralized" all he wants, but until someone else comes along and says, "yea, I'll build on that," it's all just hand-waving. Or is Dorsey just going to run all the instances and pretend you have a choice?

@RL_Dane @atomicpoet @fediversenews

Right?! So many questions.. who will maintain the spec? At least ActivityPub has W3C behind it, for better or for worse.

@ikeacurtains @RL_Dane @atomicpoet @fediversenews W3C doesn't do anything. It's not behind nor is it upfront. They just gave a platform for community group to create their own standard. W3C have many standards that are practically dead right now. Only adoption can save protocols. Nothing else matters

@ikeacurtains @atomicpoet @fediversenews

Reminds me a bit of the (false) decentralisation argument for cryptocurrency. 👉 If the demand of computational resources can in practice only be met by few potent players (e.g. big corporations like Nvidia) then it's not decentralised. It's only distributed among an elitist club that can negotiate secretively.

Which is what can easily happen, when Dorsey e.g. decides to only federate with those who pay well.

There's https://github.com/atsign-foundation/at_server to run the server.

Or, the specification is at https://github.com/atsign-foundation/at_protocol, if someone wants to build their own compatible server.

There's not much documentation on how to run the server, but there are recent commits, so, at least the code appears to be up-to-date. Someone with some familiarity with dart can probably figure it out.

@ikeacurtains@mstdn.ca @atomicpoet@mastodon.social @fediversenews@venera.social

GitHubGitHub - atsign-foundation/at_server: The core software implementation of the atProtocol.The core software implementation of the atProtocol. - GitHub - atsign-foundation/at_server: The core software implementation of the atProtocol.

@danjones000 @atomicpoet @fediversenews

Which is all well and good, though I doubt that running this server magically gets me my own local instance of Bluesky.

@ikeacurtains @atomicpoet @fediversenews

ATP is just a protocol. Federated, rpc based, extensible protocol. It can do anything, so can AP. The only valuable metric is protocol adoption. If ATP happen to have more instances and more users then AP then AP will be forgotten pretty quickly. That happened already with ostatus and many other efforts.

This willingness of BlueSky to read Mastodon posts, sounds like the construction of a trojan horse.

First you make the connection to Mastodon and use it as marketing to how many people can be reached through BlueSky.

And once you have enough users yourself, you follow Musk's path with Twitter: you either cancel the API or you start charging for it to every user who wants to stay connected with people they follow on Mastodon.

@atomicpoet @fediversenews

@atomicpoet @fediversenews They (generally) can read our posts, given that they can be accessed via HTTP(S) like any other page on the open web.

The same cannot (as far as I know) be said in reverse. And that’s the whole problem.

@philip @atomicpoet @fediversenews I think it could be done. The tools in the Bluesky GitHub repository should be enough to locate the PDS of a user from their DID, then walk the merkle tree to display all their posts. Generate HTML output and you’ve got a Bluesky web viewer. As far as I know everything is public by design.

github.com/bluesky-social/atpr

GitHubGitHub - bluesky-social/atproto-ecosystem: list of projects and implementations in the AT protocol ecosystemlist of projects and implementations in the AT protocol ecosystem - bluesky-social/atproto-ecosystem

@MetalSamurai
Can you give me a pointer as to how to identify it's register once I have the DID for a given handle. Don't I need that to access the DID document?
@philip @atomicpoet @fediversenews