If they reply to users on those communities their replies will federate if the users aren't blahaj users. I've seen people instance banned from blahaj.zone replying to comments and posts of non-blahaj users in blahaj communities federate to other servers. Since the federation is handled by the server of the one they're replying to.
It's the same way it works on Mastodon or Miskey. If they post to the community itself, it won't federate, but their replies can still federate. That's why in Lemmy 1.0 communities will store the bans of site banned users so this won't be possible anymore. I've heard piefed already does that.
Update: Admiral patrick removed the repository along with all Tesseract communities in response to the drama. Hopefully this means he’s stepping away from the project for good.
They're probably hoping it'll blow over and that people will forget and forgive them for it. We can't let that happen or they'll do the same thing again, or worse.
I’m only aware of this blacklist because of the recent change, but it has existed since 2024. We should remove this and any other interface that implements similar filtering, regardless of what those filters are designed to remove.
It's a severe overstep of a developer to silently run their own blacklist for content, servers, or people on someone else's server without their knowledge, doesn't matter if it had the best intentions. Once you go down the route of trying to trick admins into not knowing you are doing it you lose all trustworthiness.
He could easily have made it a backdoor to collect the login creds of admins he disliked so he could trash their servers later. Who's to say he didn't honestly.
They did and it should work just fine like that until Lemmy 1.0 drops since the API v3 compatibility is slightly broken in 1.0 unfortunately.
@ada@lemmy.blahaj.zone could probably add this fork back but it might not seem worth it because it will break in Lemmy 1.0 and it's still software made by a transphobe.
I'm happy to see this blowing up. Hopefully more people become aware of this developer's disgusting behavior, and either don't use Tesseract at all, or contribute to db0's fork to help keep it afloat. Since he's been talking about getting rid of it completely after Lemmy 1.0
I don't know if they plan on keeping it long term, if they do though, it definitely should have a better name, Something which isn't associated with the idiot who currently did this. Also in their fork they should remove the user agreement page since it implies this same enforcement.
So better hope someone can pick it up to maintain the changes to it whenever that comes around. Hopefully there won't be any need to keep up with the main Tesseract build if the Dev's actions in response to this are anything to go off of.
Did you notice what he replaced the image with? I Think it might be an AI generated Anubis picture but it could also be a generic one. Either way ugly as fuck.
Good call, I don't see anything good coming from them in the future either. It's definitely concerning that this person is a mod on piefed.social, makes me feel like people need to stay away from that instance and its communities.
Also I wonder if Ada should be made aware of this person, considering their prolific history of acting in bad faith.
Update, it seems like the Tesseract Dev and owner of Dubvee.org has responded to this, by shutting off his instance and redirecting the domain to this picture:
Real mature of him. I would encourage not using Tesseract anymore or if you must, using the Fork db0 provides, and contributing to that instead of the main one.
What I mean is, there is no reason for a frontend to do what Lemmy already does in the transparent way it does it. I used Tesseract for its community moderation tools and I think other's do as well.
It just doesn't make sense to do censorship in the UI tool exclusively when Lemmy has those options already, it would be like hiding someone from the UI while not blocking their account in the backend. Moderation tooling should be tied into the real features that we already have in the backend or it's not really doing anything.
Lemmy though has its own instance moderation tools so it's also just unnecessary. The entire reason he did this is the hope that instance admins won't notice it and that even if they do they might not be able to control it without recompiling.
I said it before and I'll say it again, there is no reason a frontend developer should be making decisions about censorship on other people's instances, no matter how reasonable it seems. That's what they are trying to do. It's why they hardcoded it and also why they changed the message to say "not compatible". This is a major overstep from a developer to try to block or censor content on instances that are not their own, and is a breach of trust.
When you write code that runs on other people's machines you need to hold yourself, or otherwise be held to a higher standard than if you're just writing shit for yourself or for fun. Crap like this doesn't meet that standard.
If they reply to users on those communities their replies will federate if the users aren't blahaj users. I've seen people instance banned from blahaj.zone replying to comments and posts of non-blahaj users in blahaj communities federate to other servers. Since the federation is handled by the server of the one they're replying to.
It's the same way it works on Mastodon or Miskey. If they post to the community itself, it won't federate, but their replies can still federate. That's why in Lemmy 1.0 communities will store the bans of site banned users so this won't be possible anymore. I've heard piefed already does that.
Update: Admiral patrick removed the repository along with all Tesseract communities in response to the drama. Hopefully this means he’s stepping away from the project for good.
I bet he wears the same yucky underwear every day.
They're probably hoping it'll blow over and that people will forget and forgive them for it. We can't let that happen or they'll do the same thing again, or worse.
It's a severe overstep of a developer to silently run their own blacklist for content, servers, or people on someone else's server without their knowledge, doesn't matter if it had the best intentions. Once you go down the route of trying to trick admins into not knowing you are doing it you lose all trustworthiness.
He could easily have made it a backdoor to collect the login creds of admins he disliked so he could trash their servers later. Who's to say he didn't honestly.
They did and it should work just fine like that until Lemmy 1.0 drops since the API v3 compatibility is slightly broken in 1.0 unfortunately.
@ada@lemmy.blahaj.zone could probably add this fork back but it might not seem worth it because it will break in Lemmy 1.0 and it's still software made by a transphobe.
Probably promoting his own biases while also blocking spam to justify its existence.
I'm happy to see this blowing up. Hopefully more people become aware of this developer's disgusting behavior, and either don't use Tesseract at all, or contribute to db0's fork to help keep it afloat. Since he's been talking about getting rid of it completely after Lemmy 1.0
Nope he went through the effort of replacing them with something:
::: spoiler Slop anubis pic
:::
Don't mind that I didn't include all 3 of them, they're all carbon copies of each other.
I don't know if they plan on keeping it long term, if they do though, it definitely should have a better name, Something which isn't associated with the idiot who currently did this. Also in their fork they should remove the user agreement page since it implies this same enforcement.
So better hope someone can pick it up to maintain the changes to it whenever that comes around. Hopefully there won't be any need to keep up with the main Tesseract build if the Dev's actions in response to this are anything to go off of.
Did you notice what he replaced the image with? I Think it might be an AI generated Anubis picture but it could also be a generic one. Either way ugly as fuck.
Good call, I don't see anything good coming from them in the future either. It's definitely concerning that this person is a mod on piefed.social, makes me feel like people need to stay away from that instance and its communities. Also I wonder if Ada should be made aware of this person, considering their prolific history of acting in bad faith.
Pretty sure it's deliberate, that person is a well known troll and contrarian.
Correction, *would help. You need to actually have it in order for it to help you.
We also defederated feddit.org for apologizing for and promoting Zionist liberal apologia.
Update, it seems like the Tesseract Dev and owner of Dubvee.org has responded to this, by shutting off his instance and redirecting the domain to this picture:
Real mature of him. I would encourage not using Tesseract anymore or if you must, using the Fork db0 provides, and contributing to that instead of the main one.
What I mean is, there is no reason for a frontend to do what Lemmy already does in the transparent way it does it. I used Tesseract for its community moderation tools and I think other's do as well.
It just doesn't make sense to do censorship in the UI tool exclusively when Lemmy has those options already, it would be like hiding someone from the UI while not blocking their account in the backend. Moderation tooling should be tied into the real features that we already have in the backend or it's not really doing anything.
Lemmy though has its own instance moderation tools so it's also just unnecessary. The entire reason he did this is the hope that instance admins won't notice it and that even if they do they might not be able to control it without recompiling.
I said it before and I'll say it again, there is no reason a frontend developer should be making decisions about censorship on other people's instances, no matter how reasonable it seems. That's what they are trying to do. It's why they hardcoded it and also why they changed the message to say "not compatible". This is a major overstep from a developer to try to block or censor content on instances that are not their own, and is a breach of trust.
When you write code that runs on other people's machines you need to hold yourself, or otherwise be held to a higher standard than if you're just writing shit for yourself or for fun. Crap like this doesn't meet that standard.