monteslu

AI agents want your API keys. Don't give them your API keys.

I built agentgate - a proxy that lets AI read my GitHub, calendar, Bluesky, etc. But any writes get queued for me to approve first. I review them over coffee.

Made an open source MCP (model context protocol) server to let an AI coding agent like Claude Code see its canvas output and also send errors and debugging for quickly iterating on a codebase. Video here: https://www.youtube.com/watch?v=z2on3KelaH4

It's open source :) https://github.com/monteslu/pagenodes

The source for pagenodes is here: https://github.com/monteslu/pagenodes and you can look at src/editor/nodeDefs/core/espeak.js as an example.

Also MDN has some pretty good documentation on the WebSpeech API https://developer.mozilla.org/en-US/docs/Web/API/Web_Speech_...

The goals are similar. PageNodes does its best to leverage newer browser capabilites. WebRTC, WebUSB, SeviceWorker, offline support, etc.

That's a good question. Our storage is in local indexeddb. And the site is https, so no one should see your flow if you don't share it. That said there's nothing stopping you from reaching out to another secure service or plugin before making requests.

Pure MQTT is done over TCP which browsers don't support without an extension. I'm trying to keep this purely web based as long as I can :)

Some MQTT servers tunnel messages via websockets, sever-sent-events, and REST calls which are supported by pagenodes.

Of course this was more of a fun example of something you can do with the Page Nodes platform than an actual echo replacement. And a way of getting started connecting services.

Definitely move on to some dedicated hardware if you're serious about this sort of thing.

Need to be able to profile frames/second for HTML5 gaming. The frames part of the timeline tab in Chrome is extremely useful.

We did it : https://twitter.com/iceddev/status/265599421469818881

You're correct. But no reason google couldn't add a ChromeWebView lib as part of the install of the new browser for PhoneGap to wrap.

The Chrome beta on ICS is great, but it's only accessible to <4% of all android devices. ICS has been out for months, and the providers are completely dragging their feet on it.

Chrome Beta needs to be backported to at least 2.3

If you're calling i18n and a11y "plugins", you're missing the point. These types of considerations are taken thoughout the framework in a consistent manner.