Jeremy Keith's 11 year long bet against cool URLs (specifically on longbets.org) comes up next year -- and it looks like he might lose it https://longbets.org/601/

Looks like he will lose the bet.

Interestingly though, the original URL was: http://www.longbets.org/601

> A 301 redirect from www.longbets.org/601 to a different URL containing that text would also fulfill those conditions.

Yes. Good thing it's still an "HTML document". One could argue that a single page app loading content via json would not qualify.

And Wales; it seems to show data across Great Britain

might have titled it, 'who owns Great Britain?', and avoided being labeled as 'typical'

You'd have to spread in the object, right?

<Component {...{animal}} />

I know, but it's too verbose for me. BTW there is a discussion about this: https://github.com/facebook/jsx/issues/23

We already do this when we have a lot of props to pass down. "A lot" usually means enough to take the line past 100 columns.

const componentProps = {}; <Component {...componentProps} />

Yes, absolutely. Ignore what I wrote.

I believe it depends on the settings for that entry - from "auto log in", "auto fill", "fill in when selected from menu" to "require master password before filling in"

"16.8 million votes needed to win referendum" - so there would therefore be ~33.6 million votes in total.

I'd love to see a search interface for all webfonts, powered by an open database of data from across all the major webfont providers. If this interface is independent of Google fonts, then you can apply it to any set of font data.

I remember Jeremy Keith talking about this at dConstruct conference; he put a bet on Long Bets that the URI of the bet wouldn't change [0]

[0] - http://longbets.org/601/

A bit meta but can someone tell me if Warren Buffet is on course to win his bet[0]? It's set to expire next year.

[0] http://longbets.org/362/

There was an episode of Planet Money just a couple of months ago that says Buffett is indeed on track to win the bet:

http://www.npr.org/2016/03/10/469897691/armed-with-an-index-...

CAGR of the S&P500 from 1/1/2008 until the end of 2015 was 6.5%. No idea what fund of funds they used but it's probably not going to be trivial to beat that (+whatever 2016 holds) over the time span after fees.

Thanks guys! :)

I wonder what happens to long bets when the charity of the winner no longer exists by the time a bet ends.

This is defined in the rules:

2. The winnings (plus growth) are awarded with fanfare to the winner's preferred charity. The winner, if still alive, can change charities if desired (but not to multiple recipients). If the winner is no longer alive and the originally designated charity is gone or drastically changed, Long Bets may award the winnings to a charity deemed closest to the winner's original intentions.

http://longbets.org/procedure/

Thanks!

The most likely change would be for protocol to move from http to https (and for non-secure URIs to be 301 redirected/forced by HSTS) though I don't think that qualifies as a change under their rules.

Under "Detailed Terms":

> A 301 redirect from www.longbets.org/601 to a different URL containing that text would also fulfill those conditions.

I think that's being pedantic; multiple redirects really don't break the spirit of the clause.

The bet is for www.longbets.org/601, and does not include a http or https protocol. Amusingly enough www.longbets.org/601 currently redirects to longbets.org/601, though the detailed terms cover this.

The Detailed Terms section makes clear that it's for HTTP:

> …entering the characters http://www.longbets.org/601 into the address bar of a web browser or command line tool (like curl) OR using a web browser to follow a hyperlink that points to http://www.longbets.org/601 MUST …

He's actually already won. The original URL included www., the current one doesn't anymore.

> A 301 redirect from www.longbets.org/601 to a different URL containing that text would also fulfill those [winning] conditions.

The bet (and the referenced article) is about the availability of the resources at the end of those URLs - the URL itself is just a reference, or a pointer if you will to a resource.

> A 301 redirect from www.longbets.org/601 to a different URL containing that text would also fulfill those conditions.

It's unfortunate, but I have no faith in crowd-funded hardware. There's plenty of "according to" and "promises" in that article for me to want to take any claims with a very healthy pinch of salt.

Same here but I'm definitely going to be keeping an eye on it. If it does succeed and ship, and looks like it's trustworthy I might seek one out. I'm currently using a Smartthings hub and while it's a lot better than the wink i had previously i'd love one that doesn't need the cloud to do so much.

It feels like there's a little bit of comparison mismatch here - I would equate Jasmine to Mocha, as they're both test frameworks, whereas Karma is a test runner. Mocha comes with a test runner OOTB, but you can also run Mocha tests with Karma.

One of the things I like about Karma is the ability to run the test suite in a number of browsers. We run our suite in Firefox, Chrome and PhantomJS as part of the CI setup.

I wonder if it wouldn't have been possible to set up a complementary test runner which allowed your Jasmine tests to be run with jsdom? That would give you the speed increase, but without needing to port, and would have allowed you to still leverage Karma when needed.

However, a good read and the Karma bootup time is certainly a pain point I've felt!

Of course the comparison between Karma and Mocha is weird, that's why the entire Karma/Jasmine/Phantom combo and Mocha/jsdom is mentioned. There's one piece missing in the Mocha/jsdom combo actually, the assertion library, and we use `unexpected` for that purpose.

This is nice way of getting the live device data out from the router - I've made a few scripts in the past for logging into the router web interface and scraping connected device data as a "Who's in the house" display.

Pulling the DHCP functionality out into something more accessible is a great idea!

Not for me on FIOS (I have one year left on my contract UGH! but I was told NO Contract sign here I'm a Noob)

I use to have my own DNS on my server for these purposes and could get a text or email whenever my kids started pulling data on wifi (Teenagers who "can't sleep" than I pulled this trick and they were sleeping)

Fios TV must have the DNS going through their crappy router.