this post was submitted on 02 Feb 2024
201 points (91.4% liked)
[Outdated, please look at pinned post] Casual Conversation
6590 readers
1 users here now
Share a story, ask a question, or start a conversation about (almost) anything you desire. Maybe you'll make some friends in the process.
RULES
- Be respectful: no harassment, hate speech, bigotry, and/or trolling
- Encourage conversation in your post
- Avoid controversial topics such as politics or societal debates
- Keep it clean and SFW: No illegal content or anything gross and inappropriate
- No solicitation such as ads, promotional content, spam, surveys etc.
- Respect privacy: Don’t ask for or share any personal information
Related discussion-focused communities
- !actual_discussion@lemmy.ca
- !askmenover30@lemm.ee
- !dads@feddit.uk
- !letstalkaboutgames@feddit.uk
- !movies@lemm.ee
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Not sure it's possible to avoid entirely, as the community here grows we get more of all types, it's hard to have a truly only-positive community when moderation is voluntary and the masses have full reign to submit literally anything.
Do you think a technology solution would help? Sentiment analysis on posts and gently redirect people to other communities instead of outright blocking them?
Maybe the only real solution is personal resilience and recognizing that we don't need to feel negative feelings just because we received a negative communication
You can't fix a people problem with process.
For example I've worked in DevSecOps for 10+ years, whenever consulting my first step is to implement a CI that picks up Pull Requests, builds them and runs a code analysis tools (e.g. pep8, spotbugs, eslint, etc..) and have the CI comment the Pull Request. The idea is to get an understanding of the projects technical debt and stop things getting worse and ensure the solution 'just works'.
Teams with huge amounts of technical debt will find a way to disable it when your not looking. They will develop all kinds of reasons and in reality the technical debt was created because of cultural issues in the team.
So I've learnt its important if you spot a team doing that, the solution isn't locking it down the solution so they can't disable it or more process. But forcing out the technical leader and sitting with the team and working out why each one is fighting the tool and not seeing them as an asset and teaching them to be better.
Earlier in my career the biggest lesson I learned was infosec was first and foremost a culture problem. Similar to your experience, working with people individually, meeting them where they are, listening, understanding, guiding, and modeling a better mindset all helps given enough time.
There are cases where some of those people just aren't willing to work with you. It's still possible to change the culture around them by influencing it more than they do. For every belligerent person, you can find one or more advocates
Yes, same experience here. People will go the path of least resistance except if you actively collaborate with them to make it work.
Very true, hopefully by the time we get there we'll have more mods tools to allow to identify bots and trolls.
Do you think a technology solution would help? Sentiment analysis on posts and gently redirect people to other communities instead of outright blocking them?
I'm not too sure, I'm always dubious about technology solutions for psychological issues.
Yes, I guess so, also why I made this post. I feel better already.