bwblabs

Apps like SleepCycle that just use the accelerometer data are not as good as wristbands, especially if you're sleeping with somebody. I still have an WakeMate, but the app expired and they didn't opensource it, so it's useless :(

97M https://www.wolframalpha.com/input/?i=.025%25+of+1.6%25+of+1...

Of course 1.6% could be about everything in terms of information that is out there, excluding raw non-meta data like bit torrent, mpeg, etc. One way of 'hiding' data for the NSA would be to embed it in these raw data streams with incorrect metadata.. would definitely harder to find that.

PuTTY beta 0.63 defaults to UTF-8 encoding and 2000 lines of scrollback (rather than ISO 8859-1 and 200).

Some other projects who depend on PuTTY like FileZilla have new builds too: https://filezilla-project.org/

I guess http://earlz.net/view/2012/06/07/0026/rooting-the-nvg510-fro...

BTW Today I (Benjamin) can be found at some App World events.

Well another thing is that it's easier to setup GEO-ip stuff in a CNAME (so www) instead of the root A records, for now at least in PowerDNS (used by Wikipedia etc.). You're completely right, but if your sites ever scales to something big you're not in the best position with a no-www, in my view having a www record (and no-www redirect) has more benefits that a no-www.

A no-www domain might not be the best solution if you ever want a 'Cookie-free Domain' (static.) for images etc. which speeds up your site. If you start with a no-www domain you have to setup a different domain (no subdomain) for it: like sstatic.net for SO, ytimg.com for YT and yimg.com for Yahoo.

When the browser makes a request for a static image and sends cookies together with the request, the server doesn't have any use for those cookies. So they only create network traffic for no good reason. You should make sure static components are requested with cookie-free requests. Create a subdomain and host all your static components there.

If your domain is www.example.org, you can host your static components on static.example.org. However, if you've already set cookies on the top-level domain example.org as opposed to www.example.org, then all the requests to static.example.org will include those cookies. In this case, you can buy a whole new domain, host your static components there, and keep this domain cookie-free.

http://developer.yahoo.com/performance/rules.html#cookie_fre...

The AirBnB place for day 4-5 in Amsterdam is more than 100km (62 miles) away (1:30 hour drive). The combination with the Vayable Nightlife like a local experience in Amsterdam is hard, because if you take the public transport the last train will leave around 23:00. I guess more sub optimal combinations are chosen, nice idea but it won't work like advertised.

I really like the idea for Christmas, so I built it for them last week.

So the only added feature is that it is in 1080p WebM / HTML5 combination? (Since H264/HTML5 1080p was already available)

I ended up buying the popular phones (HTC Desire HD, Samsung Galaxy S2, etc.) just for testing, I'm on iOS myself.

But just working from (non reference) phones is dangerous too, it's so annoying to implement the volume controls with a BroadcastReceiver for the ACTION_MEDIA_BUTTON Intent (works great on Motorola's), but fails on HTC, and you should just override onKeyUp()... all (Android) phones behave differently, and not only in (screen) specs. Samsung Galaxy S (<2.2) is notorious in not following the Android specs, for example it shows the versionCode instead of versionName to the user [http://developer.android.com/guide/publishing/versioning.htm...] and if you do some (proxy) audio stream playback there is the [http://google.com/search?q=PVMFMemoryBufferReadDataStreamImp...] error with no real solutions...

The problem is, in the end, it should work on the popular devices, not the 'perfect' Android reference phones..

Well, the Android emulation is pretty good with GPS & call simulation, only limitation is Eclipse which only let you control 1 emulator (or device) at a time, but if you connect to the emulator port, you can manage quite a lot.

If you start with video (or even audio) displaying/capturing then the emulator is pretty fast useless indeed.

I missed that, now I see!

Then check that http://migrationsmap.net/#/SHN/departures is still broken.

I must agree with most people complaining here, it should work on ALL modern browsers (including IE9).

The implementation is not even great either, see this screenr I made: http://screenr.com/azAs

Looks great! The population of Saint Helena is NaN and also there is something wrong with the arrows..

BTW changing #hashcode based on the country looking at would be great too.

1) I cannot verify that, all my tests are responding with a HTTP status 200.

2) Well of course I notices it with my IE9 first, but I thought that BrowserLab was a nicer way to show the results. Can you verify my findings with a IE-browser?

BTW I don't see any BrowserLab non-IE problems with that https+ url: http://i.imgur.com/fOeqZ.png

I get the feeling that Google has a new policy to NOT support IE9/8/7, like with their Chrome experiments ( http://news.ycombinator.com/item?id=2812503 ).

Check the BrowserLab results: http://i.imgur.com/S6dQP.png

I would say that there are two options:

* They don't test their site in IE9 (nor 8/7/6) or they don't know/care.

* They are actively doing this..

And I cannot believe the first..

Some proof would be nice here. I almost thought having some proof after using Watchmouse DNS Analysis on a Godaddy DNS hosted domain: http://www.watchmouse.com/en/dnstool.php?varghost=cheapdomai... , and hit some 'No response' from multiple locations. But some Watchmouse test locations always reply with 'No response' (Amsterdam3-Netherlands; Belgrade-Serbia; Budapest-Hungary; Frankfurt-Germany; Lille-France; Madrid-Spain; Novosibirsk-Russia; San Francisco-U.S.A.; Sofia-Bulgaria).

Any other good DNS tool that queries from multiple GEO locations?

Do we actually know how many SSL certs Google uses, and for what?

From what I can see:

- Google Search & Google+ (https://encrypted.google.com/ https://plus.google.com/) are using a *.google.com from GeoTrust/Google Internet Authority

- Google Mail (https://www.google.com/accounts/) is using a www.google.com from VeriSign/Thawte

Ofcourse I'm also afraid that this is indeed a MITM attack against Iranian users.

With SSL certs that costs less than $15 you can expect that things cannot be thoroughly checked, however a Wildcard DigiNotar SSL cert is costing you € 750 a year (in a 4 year contract http://diginotar.nl/OnlinePrijsindicatie/tabid/1417/Default....), you would expect that these things would not be possible.

If they however hacked the root CA, it's even more scary, also Vasco (the mother company) makes virtually every Two-factor authentication used for Dutch Banking..

A slightly better search estimate & 10% lower:

http://google.com/search?hl=en&q=site%3Anews.ycombinator...

(search phrase with wildcard and range in it, I didn't even knew this combination was possible)