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.socialEnglish
    363·
    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.worldOPEnglish
      1·
      55 minutes ago

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

      • Skavau@piefed.socialEnglish
        1·
        47 seconds ago

        These aren’t specific community *blocks (they’re not blocks as such). They’re keywords. It jus so happens that “196” was a community as well, although that has now been removed.

      • OpenStars@piefed.socialEnglish
        1·
        1 minute ago

        Wait until you see what is coming up next in Lemmy:

        latest case in point: the next version will hardcode lemmy.ml as a source to pre-fetch popular communities

        it uses lemmy.ml as the source of truth for that, and there is no way to change that

        At least PieFed allows you to edit the list. I still agree that it should not have been hard-coded, but this is not a case where Lemmy is a shining beacon of all goodness and PieFed is pure shit - both have their flaws, and Lemmy’s is MAJOR (and unchangeable) whereas by comparison, PieFed’s is fairly minor as these things go.

        Plus haven’t the PieFed devs already changed the code in response to this very thread? (In 2 of the 3 places, but I haven’t taken time to actually look directly myself, and the 3rd place should also be changed too, if it hasn’t been already, to remove the list from being hard-coded.) The PieFed devs, instead of telling the userbase to piss off and only reluctantly change things after a large outcry, are (especially by comparison, but also very much objectively too?) VERY responsive to feedback? I bet you will even be thanked for bringing this to their attention… though in the future you could also try submitting a codeberg ticket:-).

        Anyway, you are helping make the installation experience more streamlined and smooth for future users, so (while I have nothing whatsoever to do with the devs), I will say thank you just by myself!:-)

      • RaivoKulli@sopuli.xyz
        1·
        47 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
      111·
      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.socialEnglish
        2·
        3 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.

      • OpenStars@piefed.socialEnglish
        1·
        11 minutes ago

        Eventually, but only reluctantly and after first telling the userbase to simply piss off and stop asking.

        In contrast, the PieFed devs seem to have edited their codebase within mere minutes of this discussion having started to have already started changing things in highly positive directions, even prior to being officially asked on codeberg.

        The contrast there is eye-opening, and I hope indicative of what the future holds for the Threadiverse. There are far too many LONG-STANDING issues remaining in Lemmy that only continue to get ignored as the years drag on… Lemmy is their codebase, you exist at their leisure, whereas PieFed is ours, able to be modified in ways that we collectively want it to. Obviously I mean on the spectrum, aka “PieFed has highly responsive devs”, who not only receive but even outright ask for advice on things like prioritization (see e.g. last year’s [email protected], although nowadays they are doing that via codeberg issue tickets).