This is cool! Typing with it right now. Have been hoping to see an innovation like this for a long time. (Maybe some proprietary products have come and gone but non-free software doesn’t exist to me unless I really can’t afford to abstain)

It hasn’t been updated in like a year and there is no spell correction. Am I missing something or is this just an acceptable tradeoff for you?

It’s “different from”.

“Similar to”; “different from”; “less/greater than”. “Different than” doesn’t make sense.

Different app

I didn’t watch this video but I suspect the sentiment is similar to Sabine’s (I highly recommend her channel)

The idea is that you browse your feed of subscriptions, not that you literally go to an instance and browse their local feed.

I don’t know if I solved it by disabling and re-enabling the repo but that’s one of the things I tried and later I could see it.

I never used Discord but used google hangouts before switching to Telegram and Matrix (the former for family and the latter for everything else).

We don’t know if axions are a real thing. This is still highly speculative.

No, only comments made after they refederate

I don’t disagree. I want to see topic aggregation as soon as possible too.

My comment was in response to the implication that people who exercise their right to not listen to everyone talking are using defederation as some sort of weapon to fulfil their chaotic, destructive agenda while free-speech instances are merely open to any and all interactions like exemplary participants in a civilised democratic society.

If you actually want to know what my perspective is, I just wrote about it: https://mander.xyz/post/739439

I don’t think of the threadiverse as a link aggregation platform but as a network of communities engaging in threaded discussion. The federated model is an answer to the problem of platform lock-in, the network effect, and the lack of autonomy communities have on proprietary/commercial/centralised platforms.

Each instance separately may fill the role of link aggregator but mainly for that community (instance), with that community’s values and moderation policies. The ability for an instance to federate with other instances with compatible policies is the benefit here.

It may actually help if you view an instance as the community, with its “communities” as its topics.

Without the possibility of creating a meta layer to let users group different communities into a single feed

This isn’t an intrinsic limitation of the protocol but a matter of UX, and given how frequently it is requested it’s bound to be implemented in some way by some project; if not Lemmy then maybe kbin or something new that crops up.

the free side, that talks with everyone

the side that talks at everyone and gets mad when people exercise their freedom from listening to everyone

While I agree with this assessment, I don’t think dictatorship (or authoritarianism more generally) is a solution to this problem. I don’t know what the solution is, but I can speculate about various properties a solution might have, and one of them is that citizens/members of a community should be encouraged to participate in domain-specific politics that they know and care about without requiring them to form opinions about things they don’t know much about.

We are all ignorant about things we don’t spend time trying to understand and we should learn to respect that fact. This applies to leaders as well; no dictator or small group of people – no matter how many advisors they have – could possibly make informed decisions pertaining to all aspects of running a society. Glorifying or worshipping a leader or a party is madness we’re all prone to as we seek simple answers that are consistent with our preconceived notions of how the world works.

Some things I think are needed first:

• greatly improved UX for handling links to content hosted on other instances: you shouldn’t have to use the inconspicuous search function to access it via your instance,
• community collections: aggregating communities by topic each with a clear overview, their own feed and a nice, convenient way to create and view crossposts between them,
• more polished and stable app(s),
• ease of migrating between instances (massive bonus if we can have portable identities),
• a change in how we present the core idea behind the federation model: it’s not about aggregation (this misconception leads to frustration over “fragmentation”), it’s about community self-governance/autonomy and error-correction (as in making it easier for communities to migrate if authority is abused).

Edit: commentes in the wrong thread due to bug

You may need to shift your expectations of the federation model. It’s not trying to solve the problem of needing separate accounts on separate sites (that’s what we need portable identities for and I hope we see that in the near future). It’s trying to solve the problem of enabling self-governing communities and preventing platform lock-in.

I just want to add that I have another anecdote of this (not getting a response) happening to my partner. Don’t know if it’s a technical issue or they’re overburdened.