thread_muting_you_promised.png

@wjmaggos @sim @jeremiah @Moon @realcaseyrollins

> don't you think obviously lefty, gay or ethnic minority accounts get more of that crap than you do?

Notably, the block-happy admins, who are almost all white and from the US or EU, block most Japanese instances. "Ethnic minority".

It is annoying that you maintain the presumption that the people on the other side of the wall get more harassment (go ask r000t, graf, etc.) or that they're not almost all white or that there is less diversity on this side, or that relative numbers for any of that are relevant to begin with. I have personally seen those people harass a gay black teenager, but nearly everyone on this side of fedi loves Jojo. Given that your definition of "harassment" is so broad that it includes anyone typing a mean word, I feel fairly certain that nearly all of the notifications I have gotten about the loli question qualify under your definition. This means that, per your definition, I have gotten more "harassment" on some days than these people get in a year; see the first attachment for an example.

So, who gets more "harassment", per your definition? You insist these things without quantifying them; that would be fine if you had any empirical evidence, but you do not have that, either.

Ultimately, I have figured out the sort of place I want to be: somewhere where I answer for myself and no one else is responsible for what I say, so no one has authority over what I say. Having figured that out, I set up this server, made my home on it, and opened registrations so that others could do the same if that kind of thing was appealing to them. I would not change it unless I changed my idea of what sort of place I want to be. "Want something else; people don't like that you want this." is insufficient: my sense of right and wrong matters more to me than grasping at a chance to be more popular with people whose opinions I do not care about. I feel bad for these people, I would like to help them; I do not feel the need to cater to their whims any more than I would if I were passing by Skid Row and the residents informed me that I was not welcome. They are not my peers, and I have no desire to get their approval, but they're free to keep doing what they are doing. Meridith Patterson expressed, more or less, the same sentiment from a somewhat gentler perspective:

> When weird nerds watch the cool kids jockeying for social position on Twitter, we see no difference between these status games and the ones we opted out of in high school. No one's offered evidence to the contrary, so what incentive do we have to play that game? Telling us to grow up, get over it, and play a game we're certain to lose is a demand that we deny the evidence of our senses and an infantilising insult rolled into one.
> This phenomenon explains much of the backlash from weird nerds against "brogrammers" and "geek feminists" alike. (If you thought the conflict was only between those two groups, or that someone who criticises one group must necessarily be a member of the other, then you haven't been paying close enough attention.) Both groups are latecomers barging in on a cultural space that was once a respite for us, and we don't appreciate either group bringing its cultural conflicts into our space in a way that demands we choose one side or the other.

That is from her piece "When Nerds Collide" which is worth considering but given that you are a broadcast-only account and not interested in reading, and don't appear to have taken into consideration anything I said and have said, here is the link just in case someone else is interested: https://medium.com/@maradydd/when-nerds-collide-31895b01e68c .

To try to put it yet another way, the people that do #fediblock are like people that don't use bloatfe because they think it is unattractive: they are wrong, but they are not wrong in a way that makes my life worse.

A week is well past my limit on arguing a moot point with someone that continues repeating lies and does not bother addressing (let alone actually answering) any objections, but moves onto the next talking point. I do not wish to put effort trying to have a conversation and getting nothing but concern-trolling and talking points as a response. If you were interested in talking about these things instead of just pushing talking points, you would have done so at least once in the last week. (In general, I avoid people that want to converse in that manner, as a bot made of meat created by a father and mother is still as much a bot as one made from symbolic logic by a programmer: https://freespeechextremist.com/notice/AIB2yWD51ohVAc7ekK .) So I'm the hell out of this thread; see second attachment.

...And not only that, but I had to dig the text of this post out of a 2.6GB core file. The browser crashed and this was, I am certain a sign that I have wasted too much time on this topic. If that hadn't been possible to recover the text, I probably would have just muted without saying anything. (PROTIP: JS strings are UTF-16 in memory, so just running "strings" on the core won't help you, because 0x0070 will reside in memory as a 0x00 and a 0x70 (though which is first is a matter of endianness), meaning that the minimum length won't be met. `strings|grep` didn't work so I figured they must all be UTF-16. I thought about iconv but that would have required two passes (in case the browser doesn't align UTF-16 on 2-byte boundaries) and I don't trust iconv to begin with and all the text I put here was ASCII anyway, so I know how to do the conversion: delete every other byte. `strings -n 1 core | tr -d '\n' | sed 's/\./.\n/g' ` works if you don't mind a lot of manual editing after managing to extract it. If I were doing it again I probably would have skipped every other byte and run strings on each half. `time sh -c "strings -n 1 core | tr -d '\n' | sed 's/\./.\n/g' > /tmp/x"` yields 36 seconds, give or take. I can't come up with a good way to do `#include <stdio.h>\nint main(int c, void *v){FILE *f[2] = {stdout, stderr}; int r; for(r=getchar(); r!=EOF&&r>0; r=getchar())putc(r,f[(c++)&1]); return 0;}` in the shell without taking two passes, but if you toss in a couple of calls to popen()/execve() and filter both stdout/stderr instead of just writing them directly, then that ought to have better throughput and let us avoid the `tr -d` hack, but we're out of one-liner territory by that time. Trying to figure out a reasonably efficient way to get the contents of a <textarea> out of a seamonkey core dump is more fun than bashing my head against the "Please understand that we do not want their approval" wall, so anyone with thoughts on *that* should please tag me in a different thread because bloat treats muted threads the same way Stalin treated friends that fell out of favor.)
notifications_about_the_loli_question.png
thread_muting_you_promised.png

Public

thread_muting_you_promised.png

Notices where this attachment appears