Earlier quoted context omitted.
There are other ways to promote a business outside of search engines. The point is you can't say you have "ditched Google" while still being part of their systems that collect user data.
Should they block Google's public DNS servers from resolving their domain, too? Good grief.
We ditched Google Analytics
131–140 of 273 posts
Re: We ditched Google Analytics
#132Earlier quoted context omitted.
Unsurprisingly, Wikipedia has a list: https://en.wikipedia.org/wiki/List_of_web_analytics_software
Who makes these lists?!
Probably the vendors of the software concerned. Perhaps it started out as a list of three with a major bias towards a particular product. And then the competitors responded, moderators did their things and eventually an accurate list was evolved.
Re: We ditched Google Analytics
#133Not strictly on topic so I apologise if this is unwanted but I thought I'd share my experience with SpiderOak in case anyone here was thinking of purchasing one of their plans. In February SpiderOak dropped its pricing to $12/month for 1TB of data. Having several hundred gigabytes of photos to backup I took advantage and bought a year long subscription ($129). I had access to a symmetric gigabit fibre connection so I…
Re: We ditched Google Analytics
#134Earlier quoted context omitted.
Did you read my comment? You will have no GA cookie from any of my sites, I am not recording client identifying things or capabilities. It is a server-side push of GA and avoids all client-side interactions. It is merely, "A page has been viewed, this one: /foo/bar?bash". There's nothing in there that is tracking you. I'm not even embracing the session management aspect. I get to use the tool that is best-in-class, i…
Without any "client identifying things" how would GA be able to chain several page hits into a session then? That is, do basic visits vs. hits split. If you are in fact anonymizing everything about a client as you claim you do, then it won't be able to. Unless, of course, you are feeding GA some opaque client ID that you then internally map to and from actual clients that hit your server. However something tells me t…
I do not care to track users/sessions, page views are enough for me. I am tracking content and content views... and I get this big tool that is awesome at slicing data and presenting trend information... for free.
Re: We ditched Google Analytics
#135Earlier quoted context omitted.
Aren't there self-hosted analytics anyway? Piwik[1] comes to mind first, but I'm sure there are many. 1. https://piwik.org/
See https://news.ycombinator.com/item?id=10697045 Piwik is still using (unsalted) MD5 for passwords in 2015, and probably will still be using unsalted MD5 in 2016.
I can't believe unsalted MD5 is "by design" (https://github.com/piwik/piwik/issues/8753).
Re: We ditched Google Analytics
#136Not strictly on topic so I apologise if this is unwanted but I thought I'd share my experience with SpiderOak in case anyone here was thinking of purchasing one of their plans. In February SpiderOak dropped its pricing to $12/month for 1TB of data. Having several hundred gigabytes of photos to backup I took advantage and bought a year long subscription ($129). I had access to a symmetric gigabit fibre connection so I…
Many of these types of services seem to intentionally cap upload speeds to reduce their potential storage liability (since they're likely over-selling storage to be able to offer 1 TB for $12 with the level of redundancy, staffing costs, etc, needed). I wonder if that is happening in this specific case? Although if it were the case the vendor should still be honest about it. Just saying they limit uploads to 2 Mbps i…
Re: We ditched Google Analytics
#137Earlier quoted context omitted.
There's a $555 bounty if you can demonstrate a security vulnerability in Piwik because of that.
I'm not interesting in further dehumanizing myself with participation in a bug bounty program. I'll write an exploit for it (the general case, not just Piwik in particular) and drop it on OSS Sec some day, but here's a theoretical attack: 1. Guess a username somehow. Maybe "admin"? Whatever, we're interested in the security of the hash function. Let's assume we have the username for our target. 2. Calculate a bunch o…
Re: We ditched Google Analytics
#138I'm doing my part. I'm moving to DuckDuckGo for searching more and more. It's a process. Google does have better results. For work I still rely on Google, for private stuff I use https://duckduckgo.com/ And for the sake of ducks, I'm eating less meat as well. No more chicken - too much antibiotics, and as little meat as possible, only when it's worth it, so great taste and good quality.
Here in Europe 'ping -c 5' gives an average of about 10ms for google.com and 30ms for duckduckgo.com. Since search is such a fundamental part of browsing, this is very noticeable.
Re: We ditched Google Analytics
#139Earlier quoted context omitted.
Many of these types of services seem to intentionally cap upload speeds to reduce their potential storage liability (since they're likely over-selling storage to be able to offer 1 TB for $12 with the level of redundancy, staffing costs, etc, needed). I wonder if that is happening in this specific case? Although if it were the case the vendor should still be honest about it. Just saying they limit uploads to 2 Mbps i…
> reduce their potential storage liability Its to reduce their maximum bandwidth capacity required. I don't see it as a problem, considering their price points. They're selling you storage, not "slam 1TB of your data into our storage system in a day". If you're looking for that, ship a hard drive to Iron Mountain. EDIT: Even AWS limits how fast you can upload to S3, and built an appliance for you to rent and ship bac…
That ZOMG WHAT A DEAL! of a plan is kinda worthless...
"Slam" is a bit of a loaded word, since... if they are selling 1TB of storage, shouldn't we get 1TB of storage?
That's the same crap that ISP's tried to pull with UNLIMITED INTERNET!!! (as long as you stay under 30gb per month)
Re: We ditched Google Analytics
#140Earlier quoted context omitted.
See https://news.ycombinator.com/item?id=10697045 Piwik is still using (unsalted) MD5 for passwords in 2015, and probably will still be using unsalted MD5 in 2016.
This is pretty bad. Piwik could be a high value target depending on the nature of the site it is used to analyze. I can't believe unsalted MD5 is "by design" ( https://github.com/piwik/piwik/issues/8753 ).
Considering Piwik is used by the GCHQ, I find it hilarious.