ta223

4 ms·

1.
by ta223 10y ago
> * Sending all microphone input to a remote server would be really bad for battery life and data usage. Not if you transcribe it first, and upload compressed text.
2.
by ta223 11y ago
That would be "'96 MacBook Pros..." or I guess, since it was written by a Mac user, "’96 MacBook Pros..."
3.
by ta223 13y ago
To clarify: The quality of the comment I quoted is indicative of the quality of TFA.
4.
by ta223 13y ago
This comment pretty much sums it up: I, too, have not read the original article and have no urge to. This article is brilliant and just my cup of smart- ass-take-that kind of writing.
5.
by ta223 13y ago
Here's how I'd trace him: 1) get access to the request logs of third-party includes on his page 2) look for requests made just before the page is published publicly
6.
by ta223 13y ago
Quite the opposite. The video -- because it's huge compared to JS, CSS, etc. -- /does/ make sense to host on YouTube. The /player/ does not belong embedded in the page though. Take a screenshot, host that on your ow
7.
by ta223 13y ago
Amen brother, amen!
8.
by ta223 13y ago
Let's see who's watching us on stopwatching.us: dig MX stopwatching.us | grep -c google.com >>> 6 curl https://rally.stopwatching.us/ |grep -c 'google.*\.com' >>> 6 curl htt
9.
by ta223 13y ago
Don't worry, you can use DDG and still be tracked by Goolge! With content of some sort loaded from Google's servers on around 80% of all sites, this mostly happens without you doing anything. But if you're really concerned, j
10.
by ta223 13y ago
Agreed. I just searched "PRISM" on DDG, and 8 out of top 10 results had some element loaded from a Google server (GA, fonts, jquery, search box, embedded youtube, etc.) Are you using Google's DNS server? Google owns the web.