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

[Regulations nonsense] How does Codeberg handling EU DSA user number reporting, if at all? #2040

Closed
opened 2025年07月21日 22:24:38 +02:00 by ell1e · 3 comments

Comment

There's this unwieldy thing the EU made, the Digital Services Act. I'm not a lawyer, this isn't legal advice, and everything I say could be wrong. However, it seems like Codeberg would be an online platform under the DSA, but the DSA seems to basically exclude online platforms that aren't big companies from most obligations, based on revenue. But the one thing remaining to do apparently would be tracking monthly active users to somehow prove that it's not one of the extra regulated very big platforms.

  1. Providers of online platforms or of online search engines shall communicate to the Digital Services Coordinator of establishment and the Commission, upon their request and without undue delay, the information referred to in paragraph 2, updated to the moment of such request.
    [Source]

Now for anybody hosting e.g. forgejo locally for themselves who reads t his, I guess they're wondering the same: if the EU wants this from random small code hosters, does forgejo track this number, and how?

Because apparently, this number is meant to include unregistered users. But I imagine if some install scripts somewhere depend on something on Codeberg and starts hammering it with git clone or wget automatically, that can lead to a ton of requests. Should they just be grouped by IP? By IP and user agent? Is Codeberg handling this somehow already, and how?

Or does Codeberg have some sort of knowledge that these numbers don't actually need to be collected by random small gitea or forgejo instances?

### Comment There's this unwieldy thing the EU made, the Digital Services Act. I'm not a lawyer, this isn't legal advice, and everything I say could be wrong. However, it *seems* like Codeberg would be an online platform under the DSA, but the DSA seems to basically exclude online [platforms that aren't big companies](https://www.eu-digital-services-act.com/Digital_Services_Act_Article_19.html) from most obligations, based on revenue. But the one thing remaining to do apparently would be tracking monthly active users to somehow prove that it's not one of the extra regulated very big platforms. > 3. Providers of online platforms or of online search engines shall communicate to the Digital Services Coordinator of establishment and the Commission, upon their request and without undue delay, the information referred to in paragraph 2, updated to the moment of such request. [[Source]](https://www.eu-digital-services-act.com/Digital_Services_Act_Article_24.html) Now for anybody hosting e.g. forgejo locally for themselves who reads t his, I guess they're wondering the same: if the EU wants this from random small code hosters, does forgejo track this number, and how? Because apparently, this number is meant to include unregistered users. But I imagine if some install scripts somewhere depend on something on Codeberg and starts hammering it with git clone or wget automatically, that can lead to a ton of requests. Should they just be grouped by IP? By IP and user agent? Is Codeberg handling this somehow already, and how? Or does Codeberg have some sort of knowledge that these numbers don't actually need to be collected by random small gitea or forgejo instances?

@ell1e wrote in #2040 (comment):

Now for anybody hosting e.g. forgejo locally for themselves who reads t his, I guess they're wondering the same: if the EU wants this from random small code hosters, does forgejo track this number, and how?

This is better discussed in https://codeberg.org/forgejo/discussions.

@ell1e wrote in #2040 (comment):

Or does Codeberg have some sort of knowledge that these numbers don't actually need to be collected by random small gitea or forgejo instances?

I am not really sure what kind of knowledge you would expect here, but this would imply some legal guidance/advice which Codeberg does not have.

@ell1e wrote in #2040 (comment):

Because apparently, this number is meant to include unregistered users. But I imagine if some install scripts somewhere depend on something on Codeberg and starts hammering it with git clone or wget automatically, that can lead to a ton of requests. Should they just be grouped by IP? By IP and user agent? Is Codeberg handling this somehow already, and how?

Sorry, but this is asking how to comply with regulations and Codeberg cannot answer that for you. As far as I am aware Codeberg has not been requested to report such numbers, so there's no answer to that.

@ell1e wrote in https://codeberg.org/Codeberg/Community/issues/2040#issue-1958794: > Now for anybody hosting e.g. forgejo locally for themselves who reads t his, I guess they're wondering the same: if the EU wants this from random small code hosters, does forgejo track this number, and how? This is better discussed in https://codeberg.org/forgejo/discussions. @ell1e wrote in https://codeberg.org/Codeberg/Community/issues/2040#issue-1958794: > Or does Codeberg have some sort of knowledge that these numbers don't actually need to be collected by random small gitea or forgejo instances? I am not really sure what kind of knowledge you would expect here, but this would imply some legal guidance/advice which Codeberg does not have. @ell1e wrote in https://codeberg.org/Codeberg/Community/issues/2040#issue-1958794: > Because apparently, this number is meant to include unregistered users. But I imagine if some install scripts somewhere depend on something on Codeberg and starts hammering it with git clone or wget automatically, that can lead to a ton of requests. Should they just be grouped by IP? By IP and user agent? Is Codeberg handling this somehow already, and how? Sorry, but this is asking how to comply with regulations and Codeberg cannot answer that for you. As far as I am aware Codeberg has not been requested to report such numbers, so there's no answer to that.
Author
Copy link

I was simply curious if Codeberg handles this already and how, apparently it doesn't.

For what it's worth, if this applies to Codeberg (which I obviously don't know), it seems like the expectation might potentially be that these numbers are tracked even if they haven't been requested yet. Not that I would know, clearly I'm not a lawyer.

I was simply curious if Codeberg handles this already and how, apparently it doesn't. For what it's worth, **if** this applies to Codeberg (which I obviously don't know), it seems like the expectation might potentially be that these numbers are tracked even if they haven't been requested yet. Not that I would know, clearly I'm not a lawyer.
Author
Copy link

I made a forgejo issue here now: forgejo/forgejo#8668 I'll close this one here. But feel free to reopen if somebody at Codeberg has something to say on this, it would be interesting to hear given Codeberg is larger than random hobbyist forgejo or gitea instances.

I made a forgejo issue here now: https://codeberg.org/forgejo/forgejo/issues/8668 I'll close this one here. But feel free to reopen if somebody at Codeberg has something to say on this, it would be interesting to hear given Codeberg is larger than random hobbyist forgejo or gitea instances.
Sign in to join this conversation.
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
2 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#2040
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?