Not only are they federating with each other, but they implemented Group to Group following to help prevent duplicate posts. Its a feature that’s been requested for lemmy/kbin/mbin, so it’ll be interesting to see how well it works for them.

which makes it that Mastodon’s implementation will not be compatible with other fediverse implementations

What a surprise! I never would have expected Mastodon to ignore compatibility with the rest of the fediverse /s

But wait, there’s more, we’re standardizing our Groups implementation so other projects can take advantage of our App and Client API.

So its compatible with lemmy but uses a different API and they want their API to be the standard for the threadiverse? This is why we should be using the C2S, but since we’re not you should just stick with the lemmy api since that’s where the client ecosystem is already at.

I wish you luck and would love to see better Interoperability, but mastodon has been against better Article support from the beginning. I’m not sure much has changed there

The author wrote this FEP by reverse engineering the Hubzilla implementation. The point of proposing it is to find and answer questions like these.

OpenWebAuth has been in use on the fediverse since before WebFinger became so widely used.

Like I said in a previous comment, this FEP was written by reverse engineering the existing implementation. It’s still a proposal so it still has to go through a discussion period where issues like this can be worked out and it can be updated

It shouldn’t be this hard to implement a standard structure for social media (groups/channels/sub-reddits) with an allegedly standardised protocol.

Wait til you see mastodon’s proposed Group implementation, which they’re intentionally making incompatible with existing Group implementations

That’s not applicable. Sublinks is using the same standard as Lemmy/kbin/mbin, i.e. ActivityPub. In a decentralized system based on an open standard, plurality of implementations is a good thing. We shouldn’t want lemmy to be the only one.

There are 500 million posts on Twitter every day. Do you read them all? There are 2.8 million subreddits. Have you browsed them all?

Nobody subscribes to every twitter acct or every subreddit so nobody is expecting to have every single post delivered to them. The fediverse has a legitimate problem where ppl don’t actually receive all the posts of accts they’re subscribed to. It’s silly to compare what the OP is complaining about to not being able to see every post on twitter/reddit.

Meta can not EEE the fediverse. The worst they can do is create their own distinct fediverse. But anyone who doesn’t want to participate will still be using the open fediverse. They can’t take your instance or force it to update to their standards.

But if you have to install an extension, how does this differ from current extension that already do this? What could the url scheme do that using http urls couldn’t?

It looks like I was mixing up some facts. The Genius case was denied because genius doesn’t own the copyright to the lyrics they were publishing. I can’t find the case now, but there was a case where a judge said scraping was allowed because it wasn’t a given that the scraper had read a ToS.

Genius (the lyrics company) tried to license the content on their website and a judge said that can’t be legally binding because there’s no guarantee the scraper read it. It seems like the same would apply here.

Their step one is:

identify medium-to-large sized Fediverse servers

which means it’ll be weighted toward mastodon servers. I hope they account for that somehow.

Not every instance is running mastodon. This would be useful for other software that don’t have it built in

Just a heads up: there’s a mastodon specific community at https://lemmy.ml/c/mastodon that would be more appropriate for this post.

If you click the tag link right above the title, it takes you to the list of all articles the author has written about it.

The mastodon dev team is notoriously opinionated. A lot of forks/frontends start because the dev wants features that mastodon has refused.

I know that’s how reddit works but this isn’t reddit. We don’t have to do things the same and we have a wider fediverse to integrate with, which necessitates different solutions.

Your argument about multiple tags for a single topic seems to be the biggest benefit of managed tags, but I don’t think that’s even a bit deal. On other fediverse services, the same thing happens and users eventually settle on a single tag for a topic. Tags in a feed will also be truncated so not all of them will be displayed without interaction. That’ll incentivize users to pick the right tag even more

ah, I see. That makes sense, thanks