Alright, I've thought about this some more and I think I want to repost in future to make it really obvious the value to developers. Here's my current todo list

Alright, I've thought about this some more and I think I want to repost in future to make it really obvious the value to developers. Here's my current todo list: - [ ] solve the meta bug - [ ] ensure Flash works but disable secure doc viewer (with a note 'available in Pro') - [ ] use docker single file scale server with simple AUTH - [ ] create a "code <-> result" demo where people can see how to use an iframe to embed this. - [ ] set options (like max-tabs, display Chrome UI, etc, allow sound, allow devtools, allow flash, allow chat, allow cobrowsing, allow sound) via environment variable - [ ] basic co-browsing indicator of other users (circle highlights on pointer) - [ ] make demos live for only 5 minutes (docker stop / kill) - [ ] show an "API integration" where you can "fully script" the browser using puppeteer etc - [ ] new static landing page. repost "X-FRAME" - [ ] make it also work via a custom element (x-frame sandbox="co-browsing") etc - [ ] show API for "record of interactions" - [ ] show API for "record of screenshots" - [ ] also custom VF options like: stop frames, start frames, resize, new tab, close tab, open devtools. - [ ] marketing copy: "x-frame - unrestricted embedding; a super iframe; embed any web content with a super iframe; scriptable remote browser isolation; drop-in full featured web-proxy right in your web client" - [ ] expose the puppeteer API right on the x-frame itself or in the JavaScript, so like from the client you can call: "selectorGet" or whatever the fuck and you get a result. Nice! - [ ] enable option to kill browser when a client has disconnected (no websocket, for more than 60 seconds). this is all about pitching developers to ensure they like it. - include minor section on caveats but be really specific like: "when you use the built-in remote devtools front-end (screenshot) right now it only works on Chrome reliably, and Firefox to some extent, while Safari has multiple bugs which make many DevTools features unusable...but cross browser devtools front end is actively being worked on and the Chrome team support its eventual inclusion in a future version of chrome." - also -- pricing: I think "pay per session" is a good idea. Or "Pay per total booked time." is a good idea. - how about i also reach out to people who have reached out to me before about this and tell them about the HN post: B**, D**, S**, R**, A**, N**, M***, etc