Viable electric cars, light bulbs connected to wifi, Raspberry Pi, robots that run like cheetahs, quad copters, quantum computers...
But saying "I'm sure there might be a few but..." indicates your disposition will be critical of an objective response. You're probably going to argue that IoT light bulbs are just lightbulbs + wifi. But Edison didn't invent copper wire or glass, and nobody questions whether the lightbulb was an invention.
It's the same argument that no thoughts are unique, they are just derivative of prior thoughts. But the conclusion is hasty and incomplete. It's easy to deconstruct ideas (and inventions), a posteriori, into a collection of parts that existed prior. But the combination of those parts is what constitutes uniqueness.
"Just because I know how to write PHP doesn't mean I understand these vulnerabilities at all."
Ouch.
You need to know a lot more than PHP to make your toaster talk to your dishwasher. And I'm pretty certain it's not the Maytag Man who's going to make it happen.
The concern over securing mesh networks is real, but the argument in the article is terrible.
Ever hear of someone missing a meeting because it was scheduled for 2:00EST and they thought it was 2:00PST? Ever see an email from an employer, or hear the news reminding you to change your clock this weekend? It's not a programming problem, programmers are just more keenly aware of it.
And it's not really a "problem" at all. Just an idiosyncrasy. Like imperial units.
It's rare that you have transatlantic meetings, but you fly abroad so often that you can't keep track of when the shops open? (your phone could compensate for that). Do you also flip the fuck out when you fly to Australia and it's goddamn Summer in January?
It's only confusing because it's different from what you've been doing your entire life. The solution (hypothetically, as this will never happen in our lifetime) is a different paradigm. You could say, "I'll get that to you by COB Wednesday", and it's understood by custom that "Wednesday" means "the workday that began on Wednesday". But more likely is that you'd say, "it'll be on your desk by 06:00 on the fourth." Speech patterns would adjust.
If you want to propose a solution to the problem, why not have everyone adopt UTC? Every programmer who has ever dealt with time deltas will give you a big hug.
Yep, that's what I meant by "accessible" too. But with Hamachi, there's a central service for client authentication. With freelan, peers authenticate directly via signed crts.
It's similar in that it's peer-to-peer, but doesn't require an auth/directory server to establish connections. If any known peer is accessible, the two can authenticate directly.
With freelan, once the client has established a connection with any other known and accessible freelan client, a direct client-client connection can be made to anyone on the network, even if they are behind a NAT/firewall. I believe it's through a combination of tun/tap, UDP-punching, and proxying, but don't know for certain.
OpenVPN establishes a site-to-site or point-to-site VPN, but routing to the client still goes through the gateway server.
Freelan still requires a known "supernode" to broker the initial connection, but after that, they can either communicate directly or through peers.
I'd be very interested to check it out if it lands on GitHub. I don't think I'd be much of a contributor up front, I'm still getting my head around all the acronyms tossed around VPN networking, but I have a hobby project for which I've been researching how to build something like this.
The kickstarter video mentions using audio io to reduce cost. Using USB would require a microcontroller and the usb interface. The microphone jack is used for scanning, so as long as your device has 16 bit audio out, I'm assuming you could print just fine.
And yes, I am going to get one just so I can see how Pink Floyd compares to Daft Punk when printed.
I'll get excited about stickers and a store when there's an API to back up the years of content I'm generating in Path. I'll even use the store to pay for access to the API.
Sent a support request over the weekend asking directly, hope they've just been too busy with the release to respond.
For anyone who plans to set this up on a site that gets moderate traffic, here's an example Raven config that helps weed out exceptions caused by 3rd party scripts and browser extensions:
I initially set up Raven without this ignore list, and we drowned in exceptions caused by shoddy browser plugins and userscripts. On the flipside, sifting through those logs did help to explain a few unreproducible support tickets.
Hearing a few convert stories over the past few months, I'm getting the impression that Google is evolving at a steady pace and is now at par with the revolution that iOS created when it first debuted. Seems like Android is going to continue to improve while iOS gets stuck in a rut.
I've been considering a switch to Android for my next upgrade, which I never thought would happen. The Android platform has reached a point where it's at least as compelling as iOS, though probably more for technically minded users. I've got increasing nerd envy over some features in Android that iOS will probably never see, or if it does it won't be for quite a while.
Has anyone here regretted making the jump from iOS to Android?