lionleaf

Fun to see this on HN! :D

Apologies for the quick reboot of the servers. I learned from last time this happened and resized the digitalocean droplet.

I really like the way Norway has done it. A couple of years back they introduced a law that to make non-competes enforceable the company would have to pay you a full salary for the duration that you're blocked out of other work. Non-competes has function, but it's far too cheap for the company and far too expensive for the employee. Now the employer has to consider whether it's a position it's worth to protect or not, rather than just put it in the default contract

Well, duh, of course it is. Monitoring writes to memory would be pretty interesting

Yeah, that's good to know. Anyone have some insight on the implementation of the Google Home mute button?

I recently got a Google Home, and I've been thinking about how to potentially build a "is-the-microphone-actually-recording?" device. A basic one should be possible just by watching the power draw, but that would probably trigger if it decides to download a firmware update or whatever too. I expect this has been done before?

Using the <iframe> "sandbox" property. At least stops things like alert('hey') and a full-page redirect

That's something I've been thinking about. Webworkers don't have direct access to the Canvas though, but it seems like you can work around that by passing image data. Killing infinite loops would be great

Changed to sfz :)

Makes me quite nervous too. So far each dweet is run in a sandboxed iframe loaded from a separate subdomain.

There are definitely things you can do, and I'm aware of some annoying ones. I'll just manually delete them at this point. Any security conscious person would view it with noscript and just read the javascript ;)

Oh, that's cool! I like the integration with twitter

Brilliant dweet! Part of the challenge is the manual minification. A larger textarea might be worth it especially as you can use linebreaks instead of ; for better readability