<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>markosaric</author><text>We&amp;#x27;re hoping to start a conversation with browsers such as Brave and Firefox and blocklist maintainers about this.&lt;p&gt;One way to incentivize even more sites to move from GA et al would be to create some kind of privacy criteria and whitelist those analytics that fulfill it (open source, minimal data, no personal data, no cookies&amp;#x2F;persistent identifiers, no cross-site&amp;#x2F;device tracking, no connection to adtech etc).&lt;p&gt;Site owners want analytics. We offer self-hosted service but most sites don&amp;#x27;t want to deal with managing analytics server as it is not an easy job. So by blocking every analytics tool (good or bad) the incentive for site owners is more on trying to avoid being blocked rather than on moving to something more privacy-friendly.&lt;p&gt;(I&amp;#x27;m the Plausible co-founder)</text><parent_chain><item><author>eric4smith</author><text>I would posit that almost any remotely hosted analytics system (privacy oriented or not) is eventually a target for privacy centric browsers. If not now, then in the future.&lt;p&gt;I mean, let&amp;#x27;s be honest - the days are fast coming when anything that looks like remotely hosted javascript is going to be blocked, no matter how benign it is.&lt;p&gt;So could it be that the future is home grown analytics subsystems that reside in your own stack?&lt;p&gt;That way people who need &lt;i&gt;deeper&lt;/i&gt; types of tracking can do it, while those that need shallow analytics can do it too.&lt;p&gt;It certainly seems to be heading in that direction.</text></item></parent_chain></comment><story><title>Simple and privacy-friendly alternative to Google Analytic</title><url>https://github.com/plausible/analytics</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>capableweb</author><text>&amp;gt; I mean, let&amp;#x27;s be honest - the days are fast coming when anything that looks like remotely hosted javascript is going to be blocked, no matter how benign it is.&lt;p&gt;I&amp;#x27;m sorry but what? Remotely hosted JS seems to always be growing in popularity, at least in the SaaS business and related area. Can I ask what industry you&amp;#x27;re in where you see more and more people blocking _all_ JS, not just analytics&amp;#x2F;tracking? (The HN bubble doesn&amp;#x27;t count as a &amp;quot;industry&amp;quot;)&lt;p&gt;I have a really hard time as seeing your statement as &amp;quot;the truth&amp;quot;. People today seem even more likely to accept arbitrary JS running in their browser, than how it used to be.</text><parent_chain><item><author>eric4smith</author><text>I would posit that almost any remotely hosted analytics system (privacy oriented or not) is eventually a target for privacy centric browsers. If not now, then in the future.&lt;p&gt;I mean, let&amp;#x27;s be honest - the days are fast coming when anything that looks like remotely hosted javascript is going to be blocked, no matter how benign it is.&lt;p&gt;So could it be that the future is home grown analytics subsystems that reside in your own stack?&lt;p&gt;That way people who need &lt;i&gt;deeper&lt;/i&gt; types of tracking can do it, while those that need shallow analytics can do it too.&lt;p&gt;It certainly seems to be heading in that direction.</text></item></parent_chain></comment><story><title>Simple and privacy-friendly alternative to Google Analytic</title><url>https://github.com/plausible/analytics</url></story>