0x1C3B00DA

0x1C3B00DA , 2 months ago

They have a pronunciation guide in their FAQ on the website. There is no branding that would be obvious/intuitive to everyone

0x1C3B00DA , 2 months ago

There is no better. Maybe they pick a name that's more intuitive for you, but it'd be less intuitive for someone else.

0x1C3B00DA , 2 months ago

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

0x1C3B00DA , 2 months ago

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.

0x1C3B00DA , 2 months ago

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.

0x1C3B00DA , 4 months ago

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

0x1C3B00DA OP , 4 months ago

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

0x1C3B00DA OP , 4 months ago

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

0x1C3B00DA , 4 months ago

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

0x1C3B00DA , 5 months ago

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.

0x1C3B00DA , 5 months ago

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.

0x1C3B00DA , 5 months ago

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.