Code for people interested app/admin/routes.py#L373 (removed since posting), app/cli.py#L1026

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.

    • Skavau@piefed.socialEnglish
      2·
      2 hours 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.

      • qaz@lemmy.worldOPEnglish
        1·
        26 minutes ago

        Yes they’re keywords, but they also happen to be the exact names of threadiverse 8 communities, so that’s pretty specific to me.

    • OpenStars@piefed.socialEnglish
      11·
      2 hours 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

      (Edit: I forgot to add the link to source)

      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!:-)