aroch

44 ms·

331.
by aroch 12y ago
You're being disingenuous, Apple buying AuthenTec prevented the N6 from having a fingerprint reader but not for the reasons you're implying (ie. patents). It prevented the wished design for the reader (touch instead of swipe) on t
332.
by aroch 12y ago
Both, but only because the US-made Sriracha sauce is imported by the ton.
333.
by aroch 12y ago
They're pretty comparable, I like archbang a little better in terms of their defaults but that's only if I'm being picky.
334.
by aroch 12y ago
I do, I run it on my MBP (two SSDs, one running OSX one with ARchbang). I've run it now for quite a while and like it. I used to run vanilla Arch, and as is bound to happen with any Arch based distro there are the occasional breaking c
335.
by aroch 12y ago
Archbang is still under active development, thankfully
336.
by aroch 12y ago
The cynic in me wonders if this is blog post was written solely to serve as positive PR for Verizon in the face of their horrible transit/peering infrastructure management (ie. letting links run hot so they can charge transit providers
337.
by aroch 12y ago
Out of curiosity, presumably your mother knew she had defective mitochondria so why did she elect to have children?
338.
by aroch 12y ago
Honestly I'd like to see something in the vein of TACK [1] over the other various key pinning methods. [1] http://tack.io/
339.
by aroch 12y ago
Seems they just recently passed Mozilla's/Google's CA root inclusion process: https://bugzilla.mozilla.org/show_bug.cgi?id=851435 Edit: Hmm, looks like the free certs will never pass strict OCSP checks. As br
340.
by aroch 12y ago
From my understanding of the WebRTC spec, as long as your TURN/STUN server is trusted (which it is, the CA and relay are both run by Mozilla) it doesn't matter if the network is untrustworthy. WebRTC by itsself is not MITM resista
341.
by aroch 12y ago
https://blog.mozilla.org/blog/2014/10/16/mozilla-and-telefon... Presumably offering routing servers and transit. Plus Telefonica bought TokBox[1], whose tech powers the backend [1] https://tok
342.
by aroch 12y ago
>Who is buying this stock?! Speculators that bought and sold to make a profit today. I bought a few hundred shares, sold about half of them (guaranteeing a profit even if the other half crashes to 0) and am holding the other half as eith
343.
by aroch 12y ago
I'm male and have a Pinterest acccount -- it is used solely when I plan on spending time baking with my girlfriend or my mother.
344.
by aroch 12y ago
The FAQ really doesn't answer the question, there's a lot of hand-wavy nonsense in it.
345.
by aroch 12y ago
JuiceSSH (probably the most popular Android SSH client) supports mosh fully.
346.
by aroch 12y ago
So..uhh...Where are the files stored? Is it a rebuilt of Syncthing? Are they stored on other users computers? Are they stored in the 'cloud'? Are they using OVH's public cloud? Or are they using OVH's hubiC ($1/TB)
347.
by aroch 12y ago
Play Store support can't do anything about software bugs, at most they'll offer to let you return the device.
348.
by aroch 12y ago
The only other option is the Google Product Support forums[1], which are mostly "staffed" by non-googler community moderators that offer no real support. Googlers who are on the forums do their best to ignore actual problem posts.
349.
by aroch 12y ago
The Lollipop release looks to be an EOL update with little to no love from Google. They haven't done a great QA job on it either since they broke core functionality (Dailer/voice calls, Wifi, location provider polling broken).
350.
by aroch 12y ago
Google is "Nexus customer support", they just don't particularly care about doing that job. Google drops support for their own developer phones faster than Samsung and HTC do. E: To address the initial downvoters: why don&#
351.
by aroch 12y ago
Mosh doesn't really impact real latency, just perceived latency by buffering the screen (and ironically, is slower on good connections than regular ssh).
352.
by aroch 12y ago
This was a ShowHN a few weeks ago: https://news.ycombinator.com/item?id=8743374
353.
by aroch 12y ago
Even if not the CPU cost, I don't think small-town, USA IT wants to deal with incompatibilities between clients when SSL is enforced (ie. no SNI on pre-GB Android phones/winXP, only some [weak] ciphers available in IE etc) not nec
354.
by aroch 12y ago
Google[1] and Amazon[2] also charge 30%... [1] https://support.google.com/googleplay/android-developer/answ... >You receive 70% of the payment [2] http://gameservices.s3-website-us-east-1.am
355.
Nvidia Tegra X1 Preview and Architecture Analysis(anandtech.com)
2 points by aroch 12y ago|0 comments
356.
by aroch 12y ago
You've misinterpreted me. The AOSP bug tracker is exactly the right place to file bug reports for Google sold devices . Google takes on the responsibility of supporting those devices, hardware and all.
357.
by aroch 12y ago
If memory serves there were a number of issues with XHTML2, chief among them being it didn't serve the original intent of XHTML very well. HTTP/2 has good meaning but some of the deign choices were made because Google wanted th
358.
by aroch 12y ago
Or a great choice if you want to shoehorn your wished spec into reality?
359.
by aroch 12y ago
The N4 was explicitly Google branded hardware with Google providing the hardware support (Google handled RMAs, component replacement, etc). It is Google's responsibility to support phones they sell as Google supported devices. It is no
360.
by aroch 12y ago
It isn't a double standard. What's is hypocritical about giving users a choice (an informed one at that)?

More ›