Fedia and Piefed have baked in code to block their users from seeing our replies, posts, and comments, while allowing a form of one way federation.
-
I think this warrants a fediverse wide boycott of all piefed/fedia instances until this is rectified.
-
I think this warrants a fediverse wide boycott of all piefed/fedia instances until this is rectified.
Can you point to the file in the pieced codeberg repo that hardcodes these blocks?
I need to understand if this is a block built into the software, or just an option the operators who deploy piefed have set in a blocklist.
-
Can you point to the file in the pieced codeberg repo that hardcodes these blocks?
I need to understand if this is a block built into the software, or just an option the operators who deploy piefed have set in a blocklist.
It's a default option: https://codeberg.org/rimu/pyfedi/src/commit/f3e863d277932b55a15b1fe5043d750994fb8c14/app/cli.py#L116
Admins can obviously edit it later on, like those instances do:
- https://piefed.zip/c/news@hexbear.net
- https://piefed.zip/instances?page=9&filter=federated&search=
- https://piefed.au/instances?page=6&filter=federated&search=
- https://anarchist.nexus/instances?page=4&filter=federated&search= , which is related to https://lemmy.dbzer0.com/, also federated with hexbear
-
It's a default option: https://codeberg.org/rimu/pyfedi/src/commit/f3e863d277932b55a15b1fe5043d750994fb8c14/app/cli.py#L116
Admins can obviously edit it later on, like those instances do:
- https://piefed.zip/c/news@hexbear.net
- https://piefed.zip/instances?page=9&filter=federated&search=
- https://piefed.au/instances?page=6&filter=federated&search=
- https://anarchist.nexus/instances?page=4&filter=federated&search= , which is related to https://lemmy.dbzer0.com/, also federated with hexbear
Thanks for pointing that out.
That level of opinion in core infrastructure software is very inappropriate. This is disturbing
It would be better to default to dynamically pull from feediseer
-
Thanks for pointing that out.
That level of opinion in core infrastructure software is very inappropriate. This is disturbing
It would be better to default to dynamically pull from feediseer
That can definitely be improved. On the other hand,
List of Piefed instances that currently defederate hexbear:
- https://piefed.blahaj.zone/ , the same way https://lemmy.blahaj.zone/ does
- https://piefed.world/, the same way https://lemmy.world/ does
- https://piefed.ca/, the same way https://lemmy.ca/ does
- https://feddit.online/, the same way https://fedia.io/ does (by the way, Fedia isn't a software, it's called Mbin, and doesn't have such code, so not sure why you're including them into your title)
- https://quokk.au/, it used to be the same when it was still a Lemmy instance
- https://piefed.europe.pub/, the same way https://europe.pub/ does
https://piefed.fediverse.observer/list
As you can see, instances defederating hexbear are instances managed by teams which were going to do so anyway, as they already did on Lemmy. I'm still waiting for an example of an instance that defederated hexbear "by mistake".
Instances who want to federate know how to do so, as we've seen above.
Setting up an instance isn't trivial, assuming that admins would revise the defederation list doesn't seem realistic.
Recent comment from an admin
This is exactly how it works. I started a PieFed instance and made the decision (during setup) to trim the defederation list down to none. Users can block on the account level.
-
That can definitely be improved. On the other hand,
List of Piefed instances that currently defederate hexbear:
- https://piefed.blahaj.zone/ , the same way https://lemmy.blahaj.zone/ does
- https://piefed.world/, the same way https://lemmy.world/ does
- https://piefed.ca/, the same way https://lemmy.ca/ does
- https://feddit.online/, the same way https://fedia.io/ does (by the way, Fedia isn't a software, it's called Mbin, and doesn't have such code, so not sure why you're including them into your title)
- https://quokk.au/, it used to be the same when it was still a Lemmy instance
- https://piefed.europe.pub/, the same way https://europe.pub/ does
https://piefed.fediverse.observer/list
As you can see, instances defederating hexbear are instances managed by teams which were going to do so anyway, as they already did on Lemmy. I'm still waiting for an example of an instance that defederated hexbear "by mistake".
Instances who want to federate know how to do so, as we've seen above.
Setting up an instance isn't trivial, assuming that admins would revise the defederation list doesn't seem realistic.
Recent comment from an admin
This is exactly how it works. I started a PieFed instance and made the decision (during setup) to trim the defederation list down to none. Users can block on the account level.
Now you're talking past me.
The issue is not that there is an option, the issue is not that there is even a suggested option.
The issue is a writer of core infrastructure software is putting their prejudices into the software as a default that have to be opted out of. That is antithetical to federation. That is pushing an agenda. That has no place in core infrastructure software.
Imagine if the Linux kernel by default, hard coded, blocked all IP addresses connecting to China, anybody could go in and remove those blocks, but they're there by default... Infrastructure should not have political opinions baked into it
We can go back and forth about wither this has had a material impact. That's not actually important. What it demonstrates is this software project is not mature yet. They still have too many emotional biases baked in.
I half expected them to have the Lemy.lol block baked in, thankfully they didn't, but it wouldn't have surprised me if they did.
-
Now you're talking past me.
The issue is not that there is an option, the issue is not that there is even a suggested option.
The issue is a writer of core infrastructure software is putting their prejudices into the software as a default that have to be opted out of. That is antithetical to federation. That is pushing an agenda. That has no place in core infrastructure software.
Imagine if the Linux kernel by default, hard coded, blocked all IP addresses connecting to China, anybody could go in and remove those blocks, but they're there by default... Infrastructure should not have political opinions baked into it
We can go back and forth about wither this has had a material impact. That's not actually important. What it demonstrates is this software project is not mature yet. They still have too many emotional biases baked in.
I half expected them to have the Lemy.lol block baked in, thankfully they didn't, but it wouldn't have surprised me if they did.
As I said above,
That can definitely be improved.
What I expect down the line is that there will be a (y/n) option during setup that will allow admins to choose.
As of now, it's not a priority, there is bigger fish to fry. Piefed 1.2 is around the corner (https://codeberg.org/rimu/pyfedi/projects/19472 ), with many improvements that have been required for a while (e.g. communities and username autocompletion)
Let's also not forget that for years Lemmy had a built-in, activated by default slur filter impacting all users, still nobody made a fuss about it, admins just disabled it and called it a day.
-
As I said above,
That can definitely be improved.
What I expect down the line is that there will be a (y/n) option during setup that will allow admins to choose.
As of now, it's not a priority, there is bigger fish to fry. Piefed 1.2 is around the corner (https://codeberg.org/rimu/pyfedi/projects/19472 ), with many improvements that have been required for a while (e.g. communities and username autocompletion)
Let's also not forget that for years Lemmy had a built-in, activated by default slur filter impacting all users, still nobody made a fuss about it, admins just disabled it and called it a day.
Let’s also not forget that for years Lemmy had a built-in, activated by default slur filter impacting all users, still nobody made a fuss about it, admins just disabled it and called it a day.
Lots of people made a fuss about it, which is the reason we eventually removed it from the defaults.
