Recent searches
Search options
We stay strong against hate and hatred, and in response to the recent abuse campaign on our platform, we have renewed our commitment to fight for a better world. We apologize to everyone who was greeted with an abusive message this morning.
Read about the recent incident and our position on our blog: https://blog.codeberg.org/we-stay-strong-against-hate-and-hatred.html
Thanks to all your kind words of support, this is much appreciated. #StaySafe
@Codeberg Props on taking a stand on this.
One thing I'd like to suggest is that any functionality that can be used for unsolicited contact with other users, especially mass contact (e.g. @'ing accounts in comments) should be heavily rate-controlled, limited to a small number per day (or per unit of moderation latency) and possibly even held for moderation entirely for new accounts without good repuration/standing except when @'ing someone who's already working on one of their own repos.
@dalias @Codeberg Yeah, agreed. Reputation systems or even basic social graph adjacency checks (“Have these users interacted before? Have both of these users interacted with the same repositories before? Do these users have overlapping organization memberships?”, etc.) have performance costs, and can be tricky to balance, but are well worth it. Would actually be a really neat case study to show how to add that sort of protection to an existing code base.
@MrDOS
Hmm, we kinda had all these ideas as well. However, someone needs to get started and build it.