mirror of
https://github.com/imputnet/cobalt.git
synced 2026-05-22 22:39:42 -05:00
[GH-ISSUE #1136] Cobalt continues connecting to the Plausible instance after analytics are disabled #6606
Reference in New Issue
Block a user
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?
Originally created by @celenityy on GitHub (Feb 28, 2025).
Original GitHub issue: https://github.com/imputnet/cobalt/issues/1136
bug description
Despite enabling
don't contribute to analyticsundersettings->privacy,cobalt.toolscontinues connecting tohttps://a.imput.net/js/script.js. This functionality should be entirely disabled once analytics are disabled - users have no way to verify you're dropping it on the server side (which is what I suspect is happening here).reproduction steps
cobalt.tools, enabledon't contribute to analyticsundersettings->privacy.https://a.imput.net/js/script.js- (I confirmed with uBlock Origin).screenshots
No response
links
platform information
Phoenix (Firefox) 135.0.1
additional context
I love Cobalt, and I'd really like to include
a.imput.neton my BadBlock Ethical Whitelist, as you otherwise perfectly meet the criteria, but this issue is unfortunately preventing me from doing so.I'd also like to ask: Would you consider disabling these analytics automatically if Global Privacy Control is enabled?
@wukko commented on GitHub (Feb 28, 2025):
hey! the script should stop making requests completely once it sees
plausible_ignorein local storage, can you check if it’s present in your case? i’ll look into this soon cuz this obviously shouldn’t happen@wukko commented on GitHub (Feb 28, 2025):
it’s also supposed to log “ignoring event” in console: https://plausible.io/docs/excluding-localstorage
@wukko commented on GitHub (Feb 28, 2025):
just figured out what you meant in the issue, the js script doesn't do any analytics by being loaded, it sends a separate fetch request to /api/event which is indeed not sent when
plausible_ignoreis present:however, i could make it not load the script at all, though i don't see how it's beneficial
@wukko commented on GitHub (Feb 28, 2025):
cobalt's plausible analytics are already private, it doesn't track anyone, just aggregated number of traffic, so i don't think it's really applicable here?
@celenityy commented on GitHub (Mar 2, 2025):
Thanks for the quick response and clarification!
I think it'd be best not to load the script at all. If anything, it'd give users more peace of mind and not mislead them into thinking Cobalt is still sending analytics after disabling them in settings (even though it isn't). Also probably a good idea to not make unnecessary connections/load unnecessary scripts for bandwidth/resource consumption (I doubt this is making a meaningful impact there to be clear, but I think it's still a good rule of thumb). It'd also help reduce the load/unnecessary blocking for those using content blockers that block
a.imput.net.That's completely understandable. To be clear, I don't have any doubt that Cobalt is not tracking users - and I believe you've gone above and beyond in protecting the privacy of users. I think my main reason for suggesting this was to allow users a way to easily opt out of analytics persistently without needing to save cookies, and I feel like you'd still get quality analytics (as the majority of browsers don't enable GPC by default). But this isn't a big deal as long as analytics are disabled when the
plausible_ignorecookie is present (since users can use ex. uBlock Origin to automatically set this cookie).