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
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.
Hasbro is probably gambling that it’s the IP that made the money, and not Larian being magic in a bottle as a developer
This is probably true, but how can executives be so stupid? Every review I read praised Larian specifically and how the made a huge game with no microtransactions and tons of little loving touches. You have to be willfully ignorant to think it was the IP and not the developer and their work that people were responding to.
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
I think the developer of PieFed is mistaken because the microblogging projects also use shared inbox a lot. My understanding is that for certain classes of posts, they actually just use it over a user’s individual inbox and the remote server is responsible for delivering it from the shared inbox to the user’s timeline.
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.
As long as there are multiple communities for the same topic, users are going to post the same links to multiple communities. The software has to handle it better. I submitted a proposal to solve it, but one of the lemmy devs have said explicitly that they won’t implement it and they don’t think duplicate posts are an issue.
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.
re: Mastodon I see it as the largest use case of the social web today. But there are many others as you well know. We just stood up a peertube instance today for example and I love my pixelfed account. I have been following kbin and Lemmy with lots of interest though reluctant to sign up and engage mostly cause I am worried about spreading myself too thin across all these amazing activitypub services.
This was my point. You shouldn’t need an account on all of these services. You should be able to interact from your single Flipboard account. But its likely that, like most new fediverse services, you were testing mostly (or probably solely) against Mastodon. Despite Flipboard having more in common with link aggregators like kbin/lemmy, yall went for mastodon compatibility first.
A lot of people are worried about large orgs/companies like Flipboard/Meta joining the fediverse and controlling it, but Mastodon itself has been in that position for a long time. It’s controlled and limited the fediverse for a while and people keep reinforcing its control instead of expanding on the fediverse’s plurality.
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.
If you take a look at their CEOs fediverse acct, you’ll see he’s pretty caught up in the mastodon hype. He’s coming at the whole thing from the perspective of mastodon being the platform, instead of the weird disjointed fediverse. People have tried explaining things he’s not understanding fully, and he kinda brushes it off. I think even in a decentralized network, there are some ppl who still need some centralized platform to focus in on.
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
Not only are they federating with each other, but they implemented
Group
toGroup
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.