Exactly!

It’s not about Totalizing Enforcement. What it changes is the cultural norm. Not right away but over time.

An age limit on alcohol never stopped anyone of any age to acquire alcohol, but it sets the societal bar for what’s acceptable. You don’t wanna be the parents that gave your kids alcoholic beverages at 13.

It’s always a little jarring how everyone very readily believes that the Scandinavian countries are the happiest in the world, but won’t believe that the incremental policy changes we implement here have any effect 🤷‍♂️

His point is there is no one protocol for the social web. The (open) social web is built on a pluriverse of protocols, like rss, email, irc, matrix, activitypub, atproto…

Studies have identified some of the main sources of microplastics as:

• plastic-coated fertilisers
• plastic film used as mulch in agriculture

WTF?

• plastics recycling.

Uuuuh…

One thing that seems to go unappreciated in the comments is the simplicity of this interop proposal: It is essentially about enabling quote-posting of link-aggregator(Groups) posts.

Bluesky + Frontpage will work this way, and I believe it’ll work exceedingly well. If the ap-net corner of the fediverse isn’t interested in this kind of interop, fair enough. To me however the promise of seamless interop between my social apps was what brought me to the fediverse, so that’s the version of the fediverse I will pursue.

Yeah I get that. What ‘works’ means in the context of local-first is flexible though. This might provide a useful framing: https://blog.jim-nielsen.com/2023/offline-is-online-with-extreme-latency/

In any case, you’re definitely right to focus on your specific use case first without trying to fit it into any specific paradigm. I’m excited to follow Habitat’s progress!

This sounds great!

Are you familiar with the local-first tenets? Seems like a natural fit for the local nature of your app:

https://youtu.be/NMq0vncHJvU

Maybe it’s doable with the new plug-ins system? I’ve asked in the issue.

I’ve been reading a lot of your exchanges on the Lemmy GitHub and I can tell you with a high degree of confidence that you are not the subject of a hazing ritual. What’s going on is a miscommunication issue; there’s no ill will directed towards you.

The Lemmy devs are under a great deal of stress these days due to the recent influx of activity, both on the big Lemmy instances as well as the Lemmy GitHub. You’ve clearly gone to great lengths to investigate various SQL bottlenecks in Lemmy, and this work does not go unnoticed or unappreciated.

The problem you’re likely running into is that the Lemmy devs are trying to address a wide array of issues, whereas you are zoomed in on some very specific performance problems. Whether or not the core devs are wrong when they say your findings are irrelevant is beside the point. What they are really saying is that they do not have the attention bandwidth to try to see what you are seeing right now.

If you find yourself unable to work with the Lemmy project, there are other fedi projects in Rust like Mitra or Kitsune which might be more receptive to your contributions. I’m personally very interested in seeing rudimentary Lemmy (Groups et.al.) compatibility in Kitsune.

The general idea is good, but I still believe the best solution is the ability for Communities to follow other Communities. That is essentially a fully automated version of this sibling proposal.

This has been explained in great detail by ‘jamon’ here:

https://github.com/LemmyNet/lemmy-ui/issues/1113#issuecomment-1595273502

This basically lets Communities opt to federate directly with other Communities, abiding by the same network dynamics as the fediverse at large, I.e. cross-network moderation by (de)federation.

Here’s a succinct description of the problem that C-C following solves:

If you are an active user (not moderator) of Lemmy, the requirement for this becomes apparent almost immediately. One of the biggest strengths of these forum are communities-at-scale. Being able to easily post and interact with large groups of people is the benefit to the user that makes Lemmy (and all other social media) appealing.

As a user, I recently wanted to post to AskLemmy. Almost every single instance has thier own separate AskLemmy implementation. Naturally, I’d tend to post to the one with the most users. But inherently, I’m missing the majority of users by only being able to post to one. I.E., I posted to AskLemmy@lemmy.ml (which had 3k users), but by doing that, I’m missing out on the users from lemm.ee, behaw, lemmy.world which in total are far more than 3k.