What's one big thing we could do to make it easy for new users to follow others and engage more in the Fediverse while encouraging a diversity of instances?

Eliminate the flow below and make it seamless to follow and engage with posts across instances.

@mike

hey mike nice to see you. 😀

that was the big advantage twitter had over RSS feeds. it was possible to centralize subscriptions, but it required cooperation among the different vendors. and i think people in this world will resist centralization.

@davew Nice to see you too Dave!!

Ironically unless this is solved there will be a constant gravitational pull toward everyone just being on one mega instance because the experience will be so much easier. And with players like Meta circling they'll have a distinct advantage.

Somehow we need to find ways to fortify the many independent instances that exist today and one of the ways to do that is to make it easier for them to collectively provide a great user experience.

@davew @mike,

There’s a vulnerability in plain sight right now, based on @Mastodon not supporting the Client-Server aspect of #ActivityPub.

Net is effect:
Clients are Mastodon-specific rather than ActivityPub based (what the #Fediverse is supposed to be about).

As you know, this is how the beginning of the end starts, since there’s no longterm protection from open standard compliance.

@davew @mike @Mastodon Users shouldn't have to trust Mastodon to do the right thing re its #API (which is an opinionated #ActivityPub implementation).

Mastodon cannot get blinded by its short-term growth (which is still minuscule in the grand scheme of things re #SocialMedia) and forget the ultra-importance of a #Fediverse where clients and servers are loosely-coupled.

A number of us have watched this movie repeatedly, over some 30+ years. The outcome is predictable.

/cc @atomicpoet @judell

@kidehen @davew @mike @Mastodon @atomicpoet @judell I do think the time has passed where C2S is an option. Nobody wants to implement it. My suggestion was to take the Mastodon API that everyone is already using, essentially rename it to the "Fediverse Client API", and start managing it as a standard just like we already do with ActivityPub and take Mastodon out of the picture as the king of the clients.

@gabek @mike @atomicpoet @davew @judell @kidehen @Mastodon

I don't see why the time would be passed for #C2S and though there aren't full implementations yet, I notice an uptick in interest on exploring the options.

@helge @gabek @mike @atomicpoet @davew @judell @Mastodon @smallcircles "The question about Client To Server can be boiled to: Should ActivityPub Servers convert the json-ld objects making up the Activity in their own proprietary format? If you say yes, you get Mastodon. If you say no, you get a Client To Server implementation."

Yes to the question, but that isn't leading to generic ActivityPub clients that work with other #Fediverse servers.

Follow

@kidehen

What's the source of this quote? What dispute exactly prompted it?

I also wonder how this interacts with the encryption certificates involved in the protocol.

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.