The event that played out yesterday in the #FediBlock tag is illustrative of why instance admins generally find the tag useless. What was conceived as a tag to highlight extremely blatant dangers has devolved into personal feuds and grievances, watering down the entire project.
For more discussion, see this excerpt from "Findings Report: Governance on Fediverse Microblogging Servers" (https://fediverse-governance.github.io/)
@toolbear Oh wait I missed this! They did offer this as well in the update from Tuesday.
"Recently to deal with CSAM on Lemmy, Haidra developed an image interrogation service. This allows you to automatically scan images during upload to reduce mod burden and then flag them for further review, or block their upload entirely, for example."
@toolbear Personally, I found the "twokitties" post about Nivenly to be overblown and making a lot of gestures toward nefarious action that don't really hold up. Unfortunately, it's also the way a lot of people became aware of Nivenly the organization.
I'm not aware of a recent response to the HAIDRA criticisms, though there was significant discussion in August here: https://github.com/nivenly/community/discussions/2
which did result in a number of followup HAIDRA-related posts on their blog: https://nivenly.org/blog/
I am opening this discussion in direct response to a solicitation on the Nivenly Discord for someone to open a thread here to discuss the recent announcement of the addition of Haidra to the Nivenl...
@[email protected] In fact hachyderm.io did previously (as in, back in April) disallow "begposting". This caused a lot of consternation from other instance mods, leading to an admin resignation, and Hachyderm changed their policy at that point.
see: https://dotart.blog/dotart-blog/silencing-hachyderm
(whether twokitties is unaware of the change, or deliberately omitting it for effect, I cannot say...)
@hierarchon @[email protected] @[email protected] agreed. I left a couple comments as followup
https://mastodon.social/@ExecGoofy/111314323456620502
the short version is: please don't dogpile the nivenly github. there is already a thoughtful discussion ongoing, and the project appears to be dead and buried. it seems odd to me that the author did not notice the ongoing discussion, several people on Fedi had linked to it in the past month or so.
@twokitties I sincerely hope that people do not read your post as an invitation to dogpile Github. The discussion so far has been civil, with a number of issues both technical and social raised, and seemed very productive (or, rather, seems to have effectively buried the project).
Telling people "if you are trans and feeling bad, please comment on the Github" is immediately going to pour gasoline on the smoldering remains of a long dead fire. Don't do that.
@twokitties A significant oversight in this is that there HAS been considerable discussion of this on Nivenly's Github page, with a long list of concerns leveled against FSEP. It is far from going "unnoticed" or "out-of-sight".
https://github.com/nivenly/community/discussions/4
The lack of response from Nivenly after weeks seems to indicate the project is DOA. I think the foundation is content to simply let it languish and not push for further action.
