Codeberg/Community
54
325
Fork
You've already forked Community
12

is abuse@codeberg.org an unmonitored email address? #2162

Closed
opened 2025年10月07日 20:45:18 +02:00 by Ember · 11 comments

Comment

I have reported multiple users and repositories for blatant violation of part 2.1.5 of the terms of use, yet i have not even received an acknowledgement, is this letting abusive users stay on codeberg intentional?

### Comment I have reported multiple users and repositories for blatant violation of part _2.1.5_ of the terms of use, yet i have not even received an acknowledgement, is this letting abusive users stay on codeberg intentional?

It is being monitored

It is being monitored
Author
Copy link

so, letting abusive users stay on codeberg is intentional then?

so, letting abusive users stay on codeberg is intentional then?

The cases you reported lie mostly outside of Codeberg. We moderate only content on Codeberg, not the fediverse. The one Codeberg repository you reported does not contain illegal content and the software is not in violation of the terms of use.

My opinion regarding the repository in question: Like all tools, software can be used for good and evil and we cannot fix social issues by banning tools.

The cases you reported lie mostly outside of Codeberg. We moderate only content on Codeberg, not the fediverse. The one Codeberg repository you reported does not contain illegal content and the software is not in violation of the terms of use. My opinion regarding the repository in question: Like all tools, software can be used for good and evil and we cannot fix social issues by banning tools.
Author
Copy link

ok, so you allow fascists and people that harass as long as they don't do it on codeberg?

congrats, that's exactly how you create a nazi bar, do better.

My opinion regarding the repository in question: Like all tools, software can be used for good and evil and we cannot fix social issues by banning tools.

https://codeberg.org/Codeberg/org/src/branch/main/TermsOfUse.md#2-allowed-content-usage

Mobbing, stalking, doxxing (exposing someone's personal information), brigading (inciting a group to spam a specific place for any reason), threatening and harassment, as well as encouraging others to do those things.

how exactly is a 'tool' whose only actual use is in violation of the above part of the ToS not a violation of the ToS


of course there is the other part too, that even github does better, i shouldn't have to create an issue here because my reports keep getting strait-up ignored

ok, so you allow fascists and people that harass as long as they don't do it _on_ codeberg? congrats, that's _exactly_ how you create a nazi bar, do better. > My opinion regarding the repository in question: Like all tools, software can be used for good and evil and we cannot fix social issues by banning tools. https://codeberg.org/Codeberg/org/src/branch/main/TermsOfUse.md#2-allowed-content-usage > Mobbing, stalking, doxxing (exposing someone's personal information), brigading (inciting a group to spam a specific place for any reason), threatening and harassment, as well as encouraging others to do those things. how exactly is a 'tool' whose only actual use is in violation of the above part of the ToS not a violation of the ToS --- of course there is the other part too, that even _github_ does better, i shouldn't have to create an issue here because my reports keep getting strait-up _ignored_

ok, so you allow fascists and people that harass as long as they don't do it on codeberg?

Harassment and fascism on other platforms is either a matter for the moderation on those platforms or a matter for the authorities, depending on the case.

> ok, so you allow fascists and people that harass as long as they don't do it on codeberg? Harassment and fascism on other platforms is either a matter for the moderation on those platforms or a matter for the authorities, depending on the case.

The content to the links to mastodon were already taken down when you reported them btw.
And your mail in fact did not get ignored.

The content to the links to mastodon were already taken down when you reported them btw. And your mail in fact did not get ignored.
Author
Copy link

@ncc1988 wrote in #2162 (comment):

ok, so you allow fascists and people that harass as long as they don't do it on codeberg?

Harassment and fascism on other platforms is either a matter for the moderation on those platforms or a matter for the authorities, depending on the case.

Even when the fascists are on your platform? It's father baffling how you don't see that this is a major problem.

@ashimokawa

The content to the links to mastodon were already taken down when you reported them btw.
And your mail in fact did not get ignored.

On mastodon, yes, however on codeberg the user is still up.
Is this really the sort of person you want here?

And how exactly am I supposed to know that when I get no feedback whatsoever, and none of the people violating the ToS get removed?

@ncc1988 wrote in https://codeberg.org/Codeberg/Community/issues/2162#issuecomment-7653490: > > ok, so you allow fascists and people that harass as long as they don't do it on codeberg? > > Harassment and fascism on other platforms is either a matter for the moderation on those platforms or a matter for the authorities, depending on the case. Even when the fascists are _on your platform_? It's father baffling how you don't see that this is a major problem. @ashimokawa > The content to the links to mastodon were already taken down when you reported them btw. > And your mail in fact did not get ignored. On mastodon, yes, however _on codeberg_ the user is still up. Is [this](https://todon.nl/@schratze/115169185656187037) really the sort of person you want here? And how exactly am I supposed to know that when I get no feedback whatsoever, and none of the people violating the ToS get removed?

@Ember

Is this really the sort of person you want here?

Did he violate the ToS on codeberg?
What is so bad about his mastodon post that he deserves banning here?

@Ember > Is this really the sort of person you want here? Did he violate the ToS on codeberg? What is so bad about his mastodon post that he deserves banning here?
Author
Copy link

The racism?? The ableist slur?? The misogyny??


since this is locked as "Too heated" (lol) i can't properly respond.

But that does not have any particular relevance to us here on Codeberg.

yes it does, because that racist, ableist, and misogynistic person has an account here. you are allowing awful people to be here as long as they keep their awfulness offsite. again, i'll repeat, that's exactly how you create a nazi bar

it's truly silly to say "how serious we are about not allowing fascism on our platform" while literally allowing fascists and harassers on your platform.

The racism?? The ableist slur?? The misogyny?? --- since this is locked as "Too heated" (_lol_) i can't properly respond. > But that does not have any particular relevance to us _here_ on Codeberg. yes it does, because that racist, ableist, and misogynistic person has an account _here_. you are allowing awful people to be _here_ as long as they keep their awfulness offsite. again, i'll repeat, **that's exactly how you create a nazi bar** it's truly silly to say "how serious we are about not allowing fascism on our platform" while _literally_ allowing fascists and harassers on your platform.

ToS on Codeberg

* Terms of Use, not Terms of Service. There's a difference here and precision is necessary for sensitive matters like this.

P.S. Haven't seen the full report.

> ToS on Codeberg `*` Terms of Use, not Terms of Service. There's a difference here and precision is necessary for sensitive matters like this. P.S. Haven't seen the full report.
Owner
Copy link

The operative word in @ashimokawa's comment is here. Personally, I understand the decision of the Mastodon instance to remove the post. But that does not have any particular relevance to us here on Codeberg.

Let’s be real. We are a hosting platform for open source developers. If we were to ban everyone who is ever an arsehole off-site, we would have nearly no users. The ‘FOSShole’ is a stereotype with an unfortunate element of truth. (I say this with sufficient self-knowledge.)

If the user were posting this content on our platform, or even encouraging people on another platform to use our platform for this kind of harassment, that would be another question. We would certainly take action.

In this case there are also specific difficulties besides it being off-site: as @ashimokawa mentioned, the problematic content in question had been removed from Mastodon by the time of your report. We have no immediate and obvious guarantee that the screenshot is not fake. (This may seem unlikely in this case, but fake screenshots of users supposedly doing ToS-violating things are already hugely problematic for moderation. This constitutes both a means of harassing users by having them banned for things they have not done; and an attack vector which actually enables fascists to use one of their favourite tactics against their perceived enemies, if we did have a policy of assuming all screenshots of un-verifiable off-site content were real.)

Please see, for example, our statement from February this year on how serious we are about not allowing fascism on our platform.

The operative word in @ashimokawa's comment is *here*. Personally, I understand the decision of the Mastodon instance to remove the post. But that does not have any particular relevance to us *here* on Codeberg. Let’s be real. We are a hosting platform for open source developers. If we were to ban everyone who is ever an arsehole off-site, we would have nearly no users. The ‘FOSShole’ is a stereotype with an unfortunate element of truth. (I say this with sufficient self-knowledge.) If the user were posting this content on our platform, or even encouraging people on another platform to use our platform for this kind of harassment, that would be another question. We would certainly take action. In this case there are also specific difficulties besides it being off-site: as @ashimokawa mentioned, the problematic content in question had been removed from Mastodon by the time of your report. We have no immediate and obvious guarantee that the screenshot is not fake. (This may seem unlikely in this case, but fake screenshots of users supposedly doing ToS-violating things are already hugely problematic for moderation. This constitutes both a means of harassing users by having them banned for things they have not done; and an attack vector which actually enables fascists to use one of their favourite tactics against their perceived enemies, if we did have a policy of assuming all screenshots of un-verifiable off-site content were real.) Please see, for example, our [statement from February this year](https://blog.codeberg.org/we-stay-strong-against-hate-and-hatred.html) on how serious we are about not allowing fascism on our platform.
dpk locked as Too heated and limited conversation to collaborators 2025年10月10日 13:30:26 +02:00
This discussion has been locked. Commenting is limited to contributors.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2162
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?