If you are unfamiliar with the problem, someone is spamming CP on Pawoo with a demand that people block Pawoo. FSE does not block instances, so we will not block Pawoo. Since I also don't negotiate with terrorists, if it keeps up I will subscribe to whatever relay Pawoo is on and we will be extremely federated and FSE's TWKN will be full of posts that just say "ohha"/"nemui", pictures of waifus, and photos of Japanese bar food. I am an asshole and I am completely unreasonable and unwilling to budge on anything ever.
Temporary MRF in place, should prevent us having to deal with the problems. If likes act funny, it's because I did it wrong. It is on git.fse ( https://git.freespeechextremist.com/gitweb/?p=fse;a=commitdiff;h=a127699b862c3d509a126ccde7e0d0ad4882ebf1 ), but it will not work out of the box on instances running a newer version of Pleroma, a bunch of shit moved around (and the guy that moved it for no reason has since been removed from the team), so some assembly is required if you're on 2.3 or above. (No, I don't remember what you have to change; I do recall it being trivial. I'd ask @sjw but non-reply posts I create no longer federate there for some reason, I figure he would prefer to stay federated with Pawoo. Just look at noop_policy.ex in your repo. I was actually going to adapt an MRF that I wrote for Poast when they were being spammed by a flood of KF accounts, but I couldn't find where I put it and I have a habit of dashing these things off and just dropping them in /tmp, which is a ramdisk.)
I'd like to discourage people from blocking Pawoo. Someone is using CP to get people to block Pawoo, and people are responding by blocking Pawoo, which means that you are demonstrating that this tactic works. You can't block an instance just because some random asshole shows up, but you sure as hell do not want to encourage people to use this as a tactic. The better option is to render the tactic useless and then put that guy into the woodchipper for posting CP.
@p@sjw >I will subscribe to whatever relay Pawoo is on I doubt they are subscribed to anything. Largest instances on the network just don't need any additional duct tape to get federated. Maybe a fake firehose-based relay. >non-reply posts I create no longer federate there for some reason NoEmptyPolicy, I assume.
I don't think they are, either, but that is the extent. Same thing as with fediunblock, I intend to demonstrate that the tactic is not just useless but counterproductive. If the backlash is insufficient, this is all computers: a very small number of people can provide sufficient backlash against anything.
@colonelj@sjw@p PLR did blackhole FSE after both of their admin accounts got deactivated, in order to try and prevent Pleroma from sending activities there and wasting queue slots (bug 2765 seems ot be relevant there).
@p@sjw i don't believe any of the nodes i've named have placed a block on fse to keep their posts from federating with us, which is what I believe you are saying.
No, they are not. I'm also not doing this: see previous remarks about interminable interrogations and me abandoning accountability. If I was going to do that, I'd say I did it. Poking the blockbots, I do that with my own account and tell people about it. The Strangelove bot, the Iron Dome, I talk about these things all the time. If I was fucking with them, I'd say I was.
> how do you say fse doesn't block nodes while rightfully blocking nodes like freak.universtiy/youjou.love/etc?
We don't. They quarantine or block FSE, but they are not blocked from here. The overlap between those instances and hentai.baby does mean that a large number of people from there have had their accounts instance-blocked. For example, "Spag" and "Proud Degenerate" are kill-on-sight, as is the former admin of hentai.baby.
@p@sjw how do you say fse doesn't block nodes while rightfully blocking nodes like freak.universtiy/youjou.love/etc? what sort of talmudic word trickery would explain this?
@p@sjw i just stripped avatar media which broaaadly solved the problem for us without having to block the instance or write any custom mrfs. i like this solution in that it does the least it has to to solve the problem for now (in a sense "denying" even the "victory" of forcing one to even strip avatars)
i just hope they're having enough fun with avatar media only and they don't force me to also strip media generally
> i like this solution in that it does the least it has to to solve the problem for now (in a sense "denying" even the "victory" of forcing one to even strip avatars)
Yeah, the idea is that this solution doesn't affect any legitimate Pawoo accounts that people on FSE are following. I suspect that FSE's not on the CP-spammer's radar, but we'll find out one way or another. At any rate, there are about 850k people there ( http://demo.fedilist.com/instance/pawoo.net ), including a couple of people that I am following, and there is one asshole spamming CP and I refuse to let that guy fuck it up for everyone. PARANOiA_-Respect---.3k.mp3
Or maybe it actually is the same guy, because I haven't gotten any of these notifications, for either of those bots. I had assumed that they were trying to avoid pinging people that had banhammers.
@mint@sjw Yeah, so the unlikely case that FSE is on their radar might be slightly more likely if they are avoiding me and doing the minimum required to bypass the MRF.
@Kyonko802@sjw It happened on the chans a long time back, it has happened on forums. It's the dirty bomb of the innanets: easy to do, creates a big panic, just requires you to make a nailbomb but with radioactive shit instead of random shrapnel, and ensures that the person doing it ends up dead, arrested, or glowing in the dark.