• 16 Posts
  • 15 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle























  • 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








  • While I am strongly in favor of this, I suspect going fully open source might be ‘too much, too soon’ for ljdawson, as I’m not sure how used they are to open source practices.

    As a gentler stepping stone that doesn’t feel like giving all control away, I would suggest sharing the source code under the PolyForm Noncommercial license: https://polyformproject.org/licenses/noncommercial/1.0.0/

    In other words, a ‘shared-source’ license that makes the code available for review, contributions and even copying, but disallows unauthorized commercial use. This provides a middle road between the fully proprietary protections Sync is used to, and the new open landscape of Lemmy & friends that it is venturing into.

    For Redditors coming here who are unfamiliar with open source, here’s a comprehensive introduction for those who care to find out: https://blog.erlend.sh/open-source-explained

    In short, it is an essential antidote to enshittification.