Code for people interested https://codeberg.org/rimu/pyfedi/src/branch/main/app/admin/routes.py#L373

I commented it out, rebuild the Docker containers and it works now 👍

EDIT: People seem to misunderstand what it does. It prevents it from federating automatically when populating the community search, importing from another instance or from Lemmyverse. It’s not a full block, and you can still add it manually. Not only that, but it’s also already partially removed since I posted this.

  • OpenStars@piefed.social
    link
    fedilink
    English
    arrow-up
    36
    ·
    edit-2
    13 hours ago

    If you dont like it, fork it. Stop bothering us about it

    -devs of PieFed

    Oh wait no, that’s the devs of Lemmy when asked the same request. (edit: ‘asking’ to ‘asked’)

    Hopefully Rimu will be more accommodating when you ask him? (codeberg issue creation prefered)

    It might be time to move this away from a hard-coded list now, if the expectations that someone installing an instance is going to read through the code is lower now than previously.

    • qaz@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      38 minutes ago

      Wasn’t that only blocking slurs and not specific communities?

      • RaivoKulli@sopuli.xyz
        link
        fedilink
        arrow-up
        1
        ·
        29 minutes ago

        As we know from TikTok having a filter for those totally prevents people from using slurs.

        But I think the bad practise here is hardcoding, not having it as a feature in general.

    • Mr. Satan@lemmy.zip
      link
      fedilink
      arrow-up
      10
      ·
      6 hours ago

      What a shit show of a discussion on that issue… Not only is hard coding bad design in general[1], but doing so for constantly evolving and highly context dependent word list is even worse. Reading the discussion I see their decision as extremely short sighted and arrogant if not just stupid.



      1. Having hard coded configurations has it’s uses, but it’s a strong red flag that might complicate maintenance down the road, and should be used with caution. ↩︎

      • OpenStars@piefed.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 hours ago

        Yes, likely very bad design on their part (if it is hard-coded not once but 3 times and if all 3 of those represent the same use cases), though until a few months ago not many PieFed instances existed except to test the evolving codebase, so this is all VERY new.

        See also this discussion of so many frustrating and LONG-STANDING bugs in Lemmy that the instance admins of slrpnk.net will switch to PieFed that (reportedly) is less buggy overall.

        All of the Threadiverse software is still new-ish and under active development - PieFed more than most, and what blows me away is how it is doing so even without a NLNet grant, just entirely freely developed by real people making actual contributions in return for basically nothing at all. Somehow this software being developed in a Western nation is out socialism-ing the literal communists, who btw also make it impossible to donate directly to the development of code without also supporting the heavily politicized lemmy.ml instance (which people have noticed a LOT of time is spent on moderating… time that could have been spent on code development, e.g. in fixing those long-standing bugs?).

        TLDR: the entire Threadiverse is new, and PieFed has “potential”. At least as much if not significantly more so than Lemmy. It will be good to see both of them improved in the future.