Rereading my comment, it comes off a little brusque so I want to clarify a bit. I think user-defined multireddits are a good feature and could exist alongside my own proposal. Users having more control over their own feed is a good thing.
But my proposal has a different goal, which is to reduce duplication of links and keep conversation more centralized. It's not a feature most users would even be aware of because it's only manageable by community mods.
Community Grouping #3071 is an issue I created and it's specifically not related to multis. Its purpose is to allows mods to unite their distinct communities into a logical community.
But #1 is predicated on #2. If developers are aware of the risk of EEE, then they won't try to remain compatible with Meta extensions, which means development of the open AP ecosystem will continue at the same pace.
Yes I read that and explained why I don't think its relevant. Facebook can't slow down progress on the fediverse because:
I've never really understood the EEE argument here. XMPP was an open proptocol, Google embraced it and attracted users, then extended it and took those users away. But according to this article, Google didn't extinguish XMPP. It's still around and serving its niche community.
That's already the situation the fediverse is in. This is a niche community and there are already existing social media companies that the majority of internet users are on. If Facebook joins the fediverse, it brings billions of new users to the fediverse. If they then leave the fediverse, ActivityPub will still be here and all of us on the real fediverse will still be here, in a niche community. Everyone here has already chosen the fediverse despite it being a clunky, unpolished, niche network. How is EEE a relevant fear for the fediverse?
The numbers for lemmy are probably way outdated. Take a look at https://lemmyverse.net/communities. It lists 636 instances but FediDB only has 302. And remember most of this growth has only come in the past week or two.
Also, mastodon only has 1.25 million active users according to FediDB, though that's probably outdated too.
This article seems needlessly antagonistic. Lemmy and kbin are new software (kbin has been live for about a month). Of course there are incompatibilities right now. Those will be worked out. Also, I'm not really sure which incompatibilities they're talking about. Lemmy/Kbin posts show up and can be replied to on other fediverse services. you can even create a post in a lemmy community from a microblog acct.
A key thing to remember is that the entire fediverse is built by hobbyists. Gargron and mastodon did a bunch of marketing to get grants/donations but the rest of the fediverse is built by individual people in their free time. Fixing these issues will take much longer than a corporate network would take.
Sidenote: There is no primary fediverse application. I know they meant mastodon because its the most well known but that's happenstance and bad journalism. Mastodon wasn't the first fediverse application and I think lemmy/kbin will outgrow it soon.
EDIT: To address OPs callout:
no one has done an especially good job explaining why the fediverse is better than centralized solutions
This feels like the author is ignoring a lot of writing about this. The main argument is its better because you're not beholden to someone else's interests, especially corporate interests that will never be aligned with the average user. (See reddit debacle)
Lemmy doesn't federate hashtags so they'll appear in the post on other fediverse services but they won't appear in hashtag feeds/searches.
EDIT: FYI, there's a cross-post button on lemmy. it's the button that looks like a copy button (A square overlaid and offset over another square).
It's not as common to push users to apps on desktop, but its a tried-and-true practice on mobile. I'm sure companies would do it if they could, but app stores and app lockin aren't as strong on desktop as on mobile
Users can block those with extensions so the data isn't as reliable
A lot of kbin users are coming from reddit and don't care about its additional (microblogging) features. Using a Lemmy-API powered app would give them exactly the experience they're looking for. And there's nothing stopping these Lemmy-API apps from adding support for the kbin extended api.
Fedilab is an app that was originally built for Mastodon and uses the mastoapi but also supports some Pleroma specific features. Apps don't need to be directly one-to-one tied to services.
I'm sure there are special cases where residents would need bathroom access directly from their apartment, but are there any good reasons for private bathrooms, other than convenience?
To me, one of the most interesting things about converting non-residential building to residential is the potential for different ways of living. A shared bathroom and kitchen with offices surrounding a communal area could lead to a more communal lifestyle for residents.