if you don't mind sharing, why is the domain blacklisted for you?
I'm only speculating though, as this is a pretty common mistake
Just as one might block "googleads.g.doubleclick.net" to avoid google tracking, it is very reasonable to blacklist sentry to avoid various companies tracking you.
Treating products like Sentry the same as advertising and analytics companies can only be harmful for our industry.
> Do we provide any of those capabilities? No.
Yes you do. When I view a bug in Sentry it tells me how many users have hit the particular bug and which users they are. I can even search by user and see what bugs they've hit.
Even if you only send an event when a bug happens it’s still handy to send some metadata along.
https://docs.sentry.io/product/cli/send-event/
Other places discuss sending "info"-level log events:
https://docs.sentry.io/platforms/python/guides/logging/
These things aren't necessarily bad, but they're 100% the building blocks for various forms of badness, and I can fully understand track-free users just saying no to all of it.
In any case, the solution for Sentry-the-company is just to have a separate domain for receiving events, so getting that blocked doesn't block your corporate landing page.
A way to opt out of personal data collection that is provided by Sentry to end-users would put Sentry back on track. Until then, I'll be running my own solution.
Edit: A cross-domain cookie could work for this
I'm a very satisfied user of Sentry, but I use it for an internal project. I also use LogRocket which is far more intrusive. For public projects, I would use Sentry but certainly understand that many people would block it. I would never use LogRocket without informing users though.
Normalizing collecting information about users and their behavior without getting informed consent in advance is harmful to our industry.
When you access a website you access resources on a remote server, this means that is almost impossible to not leave any trace of you visiting that website (access logs, ISP logs, DNS logs, etc).
I do think there should be explicit consent for a locally installed software to send logs or analytics to an external server, but I don't think explicit consent must be given when the user is the one accessing the server.
Also, there is a big difference between technical logs (app crashes, 404 pages, resources that fail to load) and storing user-specific information or actions (exact location, products purchased, items viewed) most importantly when this information is used for marketing purposes, not for improving the user experience (by making the website faster/easier to use/more secure, etc.).
Often times much more is being collected than than what would be required for performance monitoring, it's not at all clear where this data ends up ("why does Bob from marketing have an account on our Sentry?" is literally something I overheard), and opt-outs are rare.