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.

This is certainly not spam but rather a blog response, a time honored practice as old as blogging itself.

OP’s article links to the source article (albeit via its fedipost rather than its blog post; maybe best to link both) and contributes to the online discourse with a long form reply, detailing a possible solution.

Mischaracterizing such a clearly well-intentioned contribution as “blog spam” is disingenuous.

edit: thanks for retracting your comment. I hope my retort won’t dissuade you from continuing to engage in this community :)

Thank you!

I think Lemmy should come up with a meta cross post type. Where the post only exists once, but it’s indexed in multiple communities, and moderators of those communities can remove the cross post. Without affecting the original post.

This is effectively how the Community-following-Community proposal works. I’ll repost what I commented in this thread:

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.

There is already a FEP for this functionality: https://socialhub.activitypub.rocks/t/fep-d36d-sharing-content-across-federated-forums/3366?u=erlend_sh