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

Codeberg pages statistics #1207

Closed
opened 2023年09月11日 00:19:56 +02:00 by schrmh · 5 comments

It would be nice to have a few statistics about a codeberg pages page.
E.g. visitor count.
The reason is that I don't want to include third party services (I don't want to have to add a consent banner) but I'm still interested in some meta data.

(Maybe a bit similar to #307 but repo traffic does not equal codeberg pages page traffic.)

It would be nice to have a few statistics about a codeberg pages page. E.g. visitor count. The reason is that I don't want to include third party services (I don't want to have to add a consent banner) but I'm still interested in some meta data. (Maybe a bit similar to #307 but repo traffic does not equal codeberg pages page traffic.)
Author
Copy link

Additional argument for Codeberg providing this based on backend data:
https://github.com/easylist/easylist/issues/17826
Answers there show that client-side statistics scripts running will very likely be blocked by easylist in general (no matter if from a third party or directly from the visited site) and I can understand that view very well.

Additional argument for Codeberg providing this based on backend data: https://github.com/easylist/easylist/issues/17826 Answers there show that client-side statistics scripts running will very likely be blocked by easylist in general (no matter if from a third party or directly from the visited site) and I can understand that view very well.
Owner
Copy link

If Codeberg collected statistics for every page, it would be opt-in and a global option. The data would exist, no matter if the author actually needed it. If people add trackers to their pages, it is at least an explicit choice of the author that they want to track their users.

Also, tracking requires server resources (although probably not much, it is better not to do this IMHO), and last but not least requires an implementation.

I'm personally against implementing this in Codeberg Pages.

If Codeberg collected statistics for every page, it would be opt-in and a global option. The data would exist, no matter if the author actually needed it. If people add trackers to their pages, it is at least an explicit choice of the author that they want to track their users. Also, tracking requires server resources (although probably not much, it is better not to do this IMHO), and last but not least requires an implementation. I'm personally against implementing this in Codeberg Pages.

The pages server is intended to run stateless, we only store the certificates for the custom domains to reduce load on the CA

The pages server is intended to run stateless, we only store the certificates for the custom domains to reduce load on the CA

I don't really think this alineates with Codeberg's values of user's privacy, even being a visitor on some page hosted with Codeberg pages.

I don't really think this alineates with Codeberg's values of user's privacy, even being a visitor on some page hosted with Codeberg pages.
Author
Copy link

Yeah,
besides the implementation effort and the additional needed resources, there is a strong privacy argument to not store and grant access to backend data (or an abstraction of it) at all (e.g. experiences with census and data rentetion). If there wasn't the other issue I linked to in which download statistics are mentioned in a comment by a Member, I would have never opened this issue here.
I "only" wanted to have some kind of indicator of how active one Pages site is but I think I will just continue as I did which is doing things rather slow, which is the healthiest way of doing things anyways instead of pushing myself on something interpreted as demand.

Thanks that you kept this open; I will close this now.

Yeah, besides the implementation effort and the additional needed resources, there is a strong privacy argument to not store and grant access to backend data (or an abstraction of it) at all (e.g. experiences with census and data rentetion). If there wasn't the other issue I linked to in which download statistics are mentioned in a comment by a Member, I would have never opened this issue here. I "only" wanted to have some kind of indicator of how active one Pages site is but I think I will just continue as I did which is doing things rather slow, which is the healthiest way of doing things anyways instead of pushing myself on something interpreted as demand. Thanks that you kept this open; I will close this now.
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
4 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#1207
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?