Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

14K
active users

mstdn.social: AboutStatusProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.8

#atproto

11 posts11 participants2 posts today
Continued thread
Public
Kye Fox

New problems emerge the more I try to use it. Direct AP<->AP works fine. Bridged stuff is inconsistent. Likes, boosts, etc don't go through. Follows don't show even if there's a bridged pair for the following account.

I don't fault the people working on Bridgy but I do know this would be easier to get right if follow relationships were simple data any authenticated app could read.

I haven't heard a positive account of developing anything moderately complex for AP. By comparison, all the AT dev accounts are positive, usually noting how easy it is to work with everything since everything is "on protocol" (the term of art for storing data in lexicons on your PDS) rather than dependent on negotiating implementation differences between the dominant platform and everything else.

#ActivityPub#ATProto#BlueSky
Public
Kye Fox

Trying Ghost's AP implementation just emphasizes what I don't like about AP-in-practice. Between that and all the bridge profiles, there are 4 new profiles, each with their own copy of the data to maintain.

With AT, it's just the one account across all platforms with all the data stored on my PDS.

Worse, to get any notice to posts appearing on them, I have to boost from my existing accounts on each network. That's a lot of trouble! With AT, they would just pull it from the relay, which pulls from my PDS. Or go directly to the PDS in some circumstances.

AP could probably be better in practice, but everyone is required to make it work with Mastodon or essentially be incompatible since it has most of the network on a few servers with a standard ignoring implementation.

#ActivityPub#ATProto#BlueSky
Public *
xszsx

Hello waffle! Been escaping from the dumpster fire that is Big Social for a while now, but only to find that the two main alternatives are not on talking terms with each other, due to technical differences which sucks. I hope wafrn will deliver the ease of moving between ActivityPub and ATProto. Having accounts on both is not ideal.
I'm still wrapping my head around it, a bit woozy from the Millennial tumblr chaotic energy.
Here's some galettes.


#waffle #wafrn #mastodon #bluesky #activitypub #atproto #millennial #tumblr #galette
#galette
Replied in thread
Public *
hallunke23 🇺🇦

Meine 2 Cent zu der Protokollfrage:

ICh wäre dafür, das Ganze auf XMPP Pubsub, hilfsweise auf ActivityPub zu realisieren.

AT ist in meinen Augen ein trojanisches Pferd, weil das Protokoll einerseits zwar prinzipiell eine Zusammenschaltung konkurrierender Diensteanbieter erlaubt, dabei aber Benutzer von einer verdeckten Zentralisierung bei Fa. Bluesky abhängig macht. Z. B. müssen bei AT sämtliche Nutzer mehrfach registriert werden:
• Zuerst bei ihrem eigenen

(1/5) @Sascha #bluesky #ATproto

ExploreLive feeds
About