ta223
Re:Google stores voice searches
on Thursday June 02, 2016 @10:35AM (#11822740)
> * 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.
Re:96 MacBook Pro’s in one server rack
on Wednesday July 29, 2015 @09:58AM (#9968633)
That would be "'96 MacBook Pros..." or I guess, since it was written by a Mac user, "’96 MacBook Pros..."
Re:Why The 'Reasons to Ban Handheld Devices Article" is Wrong, Stupid
on Thursday March 13, 2014 @12:05PM (#7392696)
To clarify: The quality of the comment I quoted is indicative of the quality of TFA.
Re:Why The 'Reasons to Ban Handheld Devices Article" is Wrong, Stupid
on Thursday March 13, 2014 @10:39AM (#7392049)
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.
Re:How to Start an Anonymous Blog
on Tuesday January 28, 2014 @02:01PM (#7138971)
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
Re:Rally Against Mass Surveillance Livestream [video]
on Saturday October 26, 2013 @02:38PM (#6618613)
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 own crummy web server, and link to YouTube, ideally with a notice to the effect of "Clicking this link will share your information with YouTube..."
Re:Rally Against Mass Surveillance Livestream [video]
on Saturday October 26, 2013 @02:25PM (#6618534)
Amen brother, amen!
Re:Rally Against Mass Surveillance Livestream [video]
on Saturday October 26, 2013 @02:19PM (#6618500)
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 https://rally.stopwatching.us/ |grep -c facebook.com
>>> 1
curl https://rally.stopwatching.us/ |grep -c youtube.com
>>> 0
curl https://rally.stopwatching.us/ |grep -c youtube-nocookie.com
>>> 1
hey, at least someone /thought/ about it
curl https://rally.stopwatching.us/ |grep -c typekit.net
>>> 1
curl https://rally.stopwatching.us/ |grep -c twitter.com
>>> 5
curl https://rally.stopwatching.us/ |grep -c cloudflare.com
>>> 3
The list goes on...EDIT: I should note that these could be harmless <a...> links, but most aren't, and I'm too lazy to update the regexes and rerun. You get the point though.
Re:The Search Engine that Vows Not to Track You [video]
on Wednesday July 10, 2013 @10:17PM (#6024108)
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, just use Chrome and/or set your name servers to 8.8.8.8 and 8.8.4.4.
Re:Make DuckDuckGo your Chrome default search engine
on Friday June 14, 2013 @11:33AM (#5880462)
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. Face it.