It’s pretty long and includes some insightful details about implementation (making the blocklist’s usage at the discretion of the instance admin though not transparent of its contents and defaulting it to enabled) but this quote boils down the underlying sentiment pretty well:
“These are all rough edges of the threadiverse which I am attempting to round off so we might actually be able to retain some level headed people instead of scraping the bottom of the barrel by being a dumping ground for people rejected by civil society."
When you examine the list, by and large, it’s pretty reasonable. Lots of false news, state propaganda, spammers, etc. But also the entire lemmy.blahaj.zone instance (where many of lemmy’s trans denizens call home). We’re included in what the lead developer describes as “bottom of the barrel” “people rejected by civil society.”
Though I do fear the backlash. You’ve got a bunch of malicious spammers, hate-mongers and blackhat state actors who now have an open window to cause a lot of harm (harassment & general sowing of discontent) with the convenient smoke screen of upset trans folks who it can be blamed on.
also, I have to call him not just a dumbass but a malicious dumbass.
“Someone leaked the list. Why am I on it??”
A: The list was never hidden just not advertised (lest people game it). I also could have encrypted it, but I merely compressed it for efficiency. If you’re on the list, then one of the 10 reasons above applies.
the file in question was placed obscurely. updated without directly calling out what it was. and published without notifying users.
seems a lot of effort went into obfuscating the true purpose of the file.
while on the subject of obfuscation. he claimed he “compressed it for efficiency”.
he compressed it, then base64 encoded it. why? why compress it to only expand the size of the file by encoding it??
@ptz@dubvee.org is a dumbass and a shitty dev if he thinks any of the bullshit he said was worth the time it took to say it.
Here’s their full explanation: https://lemmy.world/post/49817942
It’s pretty long and includes some insightful details about implementation (making the blocklist’s usage at the discretion of the instance admin though not transparent of its contents and defaulting it to enabled) but this quote boils down the underlying sentiment pretty well:
When you examine the list, by and large, it’s pretty reasonable. Lots of false news, state propaganda, spammers, etc. But also the entire lemmy.blahaj.zone instance (where many of lemmy’s trans denizens call home). We’re included in what the lead developer describes as “bottom of the barrel” “people rejected by civil society.”
Though I do fear the backlash. You’ve got a bunch of malicious spammers, hate-mongers and blackhat state actors who now have an open window to cause a lot of harm (harassment & general sowing of discontent) with the convenient smoke screen of upset trans folks who it can be blamed on.
I’ll give a short description of the long post.
also, I have to call him not just a dumbass but a malicious dumbass.
the file in question was placed obscurely. updated without directly calling out what it was. and published without notifying users.
seems a lot of effort went into obfuscating the true purpose of the file.
while on the subject of obfuscation. he claimed he “compressed it for efficiency”.
he compressed it, then base64 encoded it. why? why compress it to only expand the size of the file by encoding it??
@ptz@dubvee.org is a dumbass and a shitty dev if he thinks any of the bullshit he said was worth the time it took to say it.