hugs

david pogue in "how to prepare for climate change" mentions chicago and the great lakes area in general as a "climate haven", so the idea is not complete bs.

i wonder if this is the reason why those little dynamixel motors have been out of stock for months. (i use them in my robots at tapster.)

thank you!

who currently has the most regard for keeping technically interesting projects alive?

there was one glorious day years ago when every story on the hn front page was about erlang. that was fun. (anyone else remember that?)

github stars are a metric of investability.

some investors use stars (and star growth velocity) to determine which projects they invest or don't invest in. (not saying it's good or bad - just saying it's a real thing.)

i've been tempted to use an agent to help me find non-horrible seats to see the 70mm imax version of the odyssey. but that's also the kind of thing that is heavily guarded by anti-bot detectors.

thanks for the extra context. i'm friendly with devs working on the protocol, but looking for ways to get them more support.

ok, cool. looks like i should chat with the fine people at cloudflare, too.

any plans to support webdriver bidi for automation? (i'd be happy to help!)

[edit: for others reading who don't usually nerd out on browser automation protocols: webdriver bidi is the new-ish w3c cross-browser standard inspired by CDP - the main magic was the upgrade to websockets and also to standardize the capture of network-level traffic. there are still feature gaps between CDP and BiDi (in spec and implementation), but long term, i believe we should bet on web standards, not proprietary protocols controlled by one company.

(disclosure: i started the selenium and appium projects.)]

no kidding. it was the last demo in the video, but my first reaction seeing the zippers-instead-tent-poles demo was, "oh, that's going to be huge." weight and "how well does it handle wind?" are concerns, but i could totally see "100% zipper" tents on the market by the end of the year.

since the rise of agentic coding tools, it feels like we're in a new "eternal september" of people discovering ui end-to-end test automation.

not many people talk about mapquest anymore.

have you tried vibium's cli + agent skill?

some serious people use vibium instead. (full-disclosure: "some serious people" is me.)

that is the MCP vs CLI debate.

i wish more people knew or cared about web standards vs proprietary protocols. the webdriver bidi protocol took the good parts of cdp and made it a w3c standard, but no one knows about it. some of the people who do know about it, find one thing they don't like and give up. let's not keep giving megacorporations outsized influence and control over the web and the tools we use with it. let's celebrate standards and make them awesome.

most people just click the "internet" button and use whatever was already pre-installed.

they probably meant desktop. i do browser test automation (selenium, vibium), and the lack of google chrome on arm64 trips up new users frequently. the workaround is to just use chromium, but that's a confusing extra step for some if it's not automated and hidden for you.

on that note, it would have been nice if they also clarified if this means they'll be shipping an official "chrome for testing" for arm64 linux, too.

hi, i'm jason huggins (selenium, appium, now vibium). browser automation and testing have been my jam for a long time. for most of that time, it would be fair to say browser automation was an often forgotten and overlooked corner of the tech landscape. with vibe/agentic coding, things have changed.

the folks at kernel reached out a few weeks ago about adding support for vibium and webdriver bidi on their service. it's now live on kernel.sh's crazy-fast-browsers-as-a-service.

ama!

openclaw is the napster of itunes.

people who have been around long enough know that we're currently in the wild west of networked agentic systems. it's an exciting time to build and explore. (just like napster and early digital music.) eventually some big company will come along and pave the cow paths and make everything safe and secure. but the people who will actually deliver that are likely playing with openclaw (and openclaw-like systems) now.

possibly also a boon for automated testing tools and infra designed for ai-driven coding.

not mozilla-related, but there's also the ladybird project if you're looking for sustainable alternatives: https://ladybird.org/

vibium clicker, too. https://github.com/VibiumDev/vibium/blob/main/CONTRIBUTING.m...

"browser automation for ai agents" is a popular idea these days.

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.

claude code 100%

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

short-term mediation is always always always run it in a virtual machine with as minimal credentials as possible.

thanks!

it's named vibium for a reason.