FinchHaven sfba @FinchHaven@sfba.social
Public

@strypey

Clicked through on that @ naturzukunft2026 link for some reason

"The spec is ActivityPub, but federation is unfortunately Mastodon."

No

is a protocol

It requires some sort of implementation via software into some sort of distribution/app

Mastodon (for one) is only *one* distribution/app

There are others

These others may

--> or may not <--

"federate" with each other to varying degrees

They are all *different* and "varying" implementations of the ActivityPub protocol

I don't know why this is so hard to understand, but it sure seems to be...

cc @naturzukunft2026naturzukunft

🫧 socialcoding.. @smallcircles@social.coop
Public

@FinchHavenFinchHaven sfba @strypey

I do not think that @naturzukunft2026naturzukunft misunderstands this.

There's a difference between the protocol and the on-the-wire reality, and in the latter is the post-facto interoperability leader.

For there to be interoperabiity in a particular domain there needs to be agreement on data formats and msg exchanges, and the specs don't provide full coverage nor clear guidance on this. Though has a section on use cases it was designed to handle, they aren't fully specified.

Of course it is perfectly fine, and highly encouraged to model a domain in the best possible way, but you won't be "part of the fediverse" until you implement enough of the post-facto Mastodon microblogging interop quirks.

We don't have a good ecosystem-level extension approach, and the constitutes a best-effort. A bandaid that allows to present a best-practice in hopes it gets further adoption.

I'm not sure that JSON-LD offers solace though.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116080870425090781 on your instance and quote it. (Note that quoting is not supported in Mastodon.)