ignore the haters. this is cool. (and i've been vibe coding with claude code and termux for months. it's good stuff.)
i would highly recommend you add guidance on automated data backups, though. my pixel phone went "black screen of death" on me and one of my projects is trapped in there until i can replace the screen.
i'm vibe coding vibium, a test automation tool in the spirit of playwright and selenium. (was #1 on hn last week for a little bit with a lively discussion.)
google fell victim to one of the classic blunders. the most famous of which is inventing the transformer behind gpt but not productizing it first. but only slightly less well-known is this: letting puppeteer go without a plan.
there's generally only 3 ways to make money in browser automation:
1) test automation (my specialty)
2) data scraping / crawling
3) business/robotic process automation (e.g. back-office data entry, processing invoices, etc.)
when it comes to handling login sessions, cookies, etc. test automation is the easiest. (you create disposable test logins and use them in each test. it's mostly a solved problem.)
handling logins is a way gnarlier problem in data scraping and business process automation. i'm focused on test automation in v1. (i'm hoping experts in data scraping and process automation can help me improve vibium in this regard.)
Thank you for helping me understand this. I'm trying to use various tools to automate downloading my energy usage from my provider. They seem to be going to great lengths to try and prevent this. It sucks because I want to conserve and reconcile usage.
entergy.com ... I'm hoping your tool or playwright will help me get it into home assistant.
i try to say this often, but it never feels like enough: yes, i started the project, but it's a relay race. i ran the first few laps, but the project has been going for 21 years now. there's dozens (hundreds?) of people to thank at this point for the success and impact that the selenium project has achieved.
reply