I've been building a lockitron clone using a raspberry pi. The key functionality selling point for me was being able to lock/unlock the door base on proximity like lockitron's "sense" feature.
Turns out this is much more difficult than it sounds because bluetooth le rssi is pretty unreliable. I've figured how to get it working for my particular case but I would be curious how lockitron configures it to work consistently for a wider range of locations and devices.
On a separate note, the servo can be attached to the door without duct tape or modifying the door if you have a door like [1]. I simply bought a piece of rubber tubing that fits over the knob and then configured a smaller piece of rubber to fit the servo arm to the lock piece on the knob. This design is also nice in that if the device malfunctions a key can override it.
This. I often tutor beginners wanting to learn to code and environment setup is by far the biggest hurdle. Frankly, think about the last time you started learning a new language, it's usually the biggest hurdle for experienced programmers as well.
The next biggest hurdle for beginners is usually grasping basic design patterns or the request response pattern of client server interaction. This is usually difficult because a lot of the nomenclature isn't there yet. But that is nothing in comparison to the struggle it is to walk someone through basic environment setup for RoR even node.
When I've tutored for web development and CS I've surprisingly been able to change the same as my freelance rates. This might suggest that I don't charge enough for freelancing, but I charge above my hourly rate at work and live comfortably in the bay area.
Guys there is an easy way around your problem. if your results are as good as you say they are then its just a matter of tweaking your ux. offload the result delivery to email and pubsub the actual search. If you have thought of this I would be interested in hearing why it doesn't work. If not then please at least include it as an option.
There is plenty of third party javascript that is not at all predatory. Pretty much all analytics services, Olark and other similar customer outreach services, A/B testing suites. There is far more of a push to create new more secure avenues for third party js (namely cors and websockets) to exist than there are efforts to eliminate it.
I'm curious how this change will effect services like optimizely that rely on third party cookies to prevent tests being run on the same users multiple times.
Take a minute look at that and tell me what the keys stand for. When you figure it out you'll realize why this is the worst piece of code you've ever seen.
