Shadertoy might fit that category? Runs in the browser, are all fragment shaders and without a size limit afaik, but they tend to be small-ish

https://www.shadertoy.com/

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

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

looks hardwired: https://medium.com/@justlv/google-home-mini-teardown-compari...

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?

Of course it's listening, at all times. Otherwise it would not be able to react to the trigger phrase. What is interesting is whether it sends this data anywhere, and that is probably impossible to ascertain, since it could store it for a while and tunnel it out with innocent looking traffic.

It would be interesting if it could be determined if it stores the passively obtained data at all. If one could monitor writes to memory while in passive state it might give a clue.

Since apparently it can be rooted without affecting the listening process, it should be possible to monitor writes in pure software.

Of course, it may detect the monitoring and avoid writing in those cases /tinfoil

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

The dweets are stopped but not unloaded as you scroll away. You're entirely right though, needs some proper unloading.

Edit: Link to the issue https://github.com/lionleaf/dwitter/issues/66

That is really cool! They are using a realistic 3D model of the persons face and eye-tracking in the VR headset to make a good guess at their facial expression, effectively reconstructing the face that's hidden by the headset.

Not something you can easily do as a consumer yet, but for high quality mixed reality production this seems like a great boon.

For an explanation of mixed reality videos are made I recommend this: https://www.youtube.com/watch?v=8T7ux3DXP_w

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 ;)

While you're deleting stuff, I noticed someone on the new page has posted pornographic images. Alas, I'm not terribly surprised since this is the internet after all, but I'll +1 a feature to report dweets as being inappropriate.

A system to automatically hide dweets (for later manual review) after receiving a certain number of reports would likely solve the problem in the short term.

While you're manually deleting things... there are currently way too many that are just exact reposts of the default swaying black bars. Probably accidents rather than people being deliberately lame, but low-hanging fruit for any kind of automatic cleanup.

Why not make their javascript run in WebWorkers and provide a DOM-like interface for all the things? That way you can kill infinite loops etc.

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

how do you sandbox the iframe/code?

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

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

Sorry about your lost dweet :( Accidental infinite loops while editing can be a pain. A "reload" button isn't a bad idea, or a "recover dweet draft" functionality.

I managed to finish one! https://www.dwitter.net/d/714

More suggestions:

- in-browser minification tool

- character counter would count using this output

- larger textarea

That way, I can compose without relying on vim + yui-compressor.

Awesome little site.

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

Aye, then I cheated. :0 I'll try doing it manually next time.

Why not auto-save to local storage? That's something that's easily added.