miken123

What I cannot find anywhere: how does this compare to Firefox' tracking protection feature? That would already block third-party requests to Facebook on other sites, wouldn't it?

> There's no need for a charging light because it's USB-C, so you know whether it's plugged in or not

I can't count the number of times my Mac wasn't charging because the USB-C cable was detached only half a millimeter.

I can also confirm the super buggy touch bar (missing buttons, non-responsive buttons) and many graphic glitches (esp. in combination with Flux). Still hoping an OS X update will fix this.

At least Google has a post-mortem, at AWS everything would still show up green with some random note about 'increased error rates'.

Dyn states their problems were fixed at 17 UTC, but me and most other people in the Netherlands have been seeing issues for the whole evening. Something about their story does not add up...

License is BSD 3-clause.

Yeah, until you do an upgrade:

"The upgrade process for some previous releases recommended the use of aptitude for the upgrade. This tool is not recommended for upgrades from wheezy to jessie."

See https://www.debian.org/releases/stable/amd64/release-notes/c...

Yes it did, but they removed that option, at least in the Mac OS X version of Spotify.

[edit] Apparently it has been added again in 1.0.5.x, but I'm not getting that update yet...

Nice technical read, but to be honest, the moment I find another app that does what I need I will gladly leave Spotify behind. Apart from the general slugginess of the app, the number of features that have been removed over the last couple of months is staggering. Just some examples, in case someone from Spotify in a position to fix this is reading this:

* Searching in playlists was removed

* Searching in local files was removed (and the local file support has always been crap anyway, please work together with Last.fm to properly match files)

* Creating a new playlist in a folder was removed (you now have to create and move the playlist)

* Sorting playlist folders was removed.

* The option to turn off your 'volume normalisation' was removed. Because your algorithm is really broken and severely compresses the music, removing any dynamic range, this is the biggest showstopper for me. Check your forums, tens if not hundreds of people already left because of this.

* Apps were removed (tbh, I can live with this)

Oh, another one, please give us an option to turn off 'Spotify Connect'. It prevents my Android phone from entering deep sleep, and thus it is a battery drain. You don't need to fix the battery drainage, just give me an option to turn the feature off.

You need to automate it if you have more than 1 site. If you have just one site, you can just check the expiry date and put that in your calendar. No need to check it on a monthly basis, no clue why the author of the post would suggest that.

The backup feature is on by default, scheduled to backup at 4:00 daily. I can't find an option to turn it off.

How can storage be more important than being reachable?

Please be aware that some internet users only have native IPv6 connectivity, and that IPv4 addresses are becoming increasingly scarce, especially if you are setting up thousands if not millions of virtual machines, like DO.

I saw the .htaccess, but that still doesn't link the request of index.php to the request of index.php?tracker.

I just tested it by changing my IP while staying in the same browser session. After an IP change the page only displays '1' for the number of visits, exactly as you would expect when reading the code (since the E-Tag for the image is kept (and the image request updates the counter), but the index.php uses your IP+UA combo to determine the session). This code is flawed and doesn't do a thing.

As it turns out, he simply uses your IP and User Agent string. See https://github.com/lucb1e/cookielesscookies/blob/master/inde...

No E-Tag tracking is taking place, since the E-Tag is never send to the server for the index.php request (only for the image request). In theory he could update the session after your IP changed, but he does not seem to do that (the image requests hold on to the old E-Tag).

So, basically, to me it seems like the whole point/post is invalid. Please correct me if I'm wrong.