Cool project! I’ll check it out.
Regarding userscripting, from the F.A.Q.:
Why use an external automation tool (Playwright) instead of a browser extension?
While Beachpatrol allows to control the browser from both the OS and from a browser extension, our priority was the OS. Therefore, something like Playwright was the natural choice.
Furthermore, while controlling the browser from an extensions is possible, Manifest v3 removed the ability to execute third-party strings of code. Popular automation extensions like Greasemonkey and Tampermonkey could also be affected by Manifest v3. The alternative is to embed the code into the extension, but that would requires re-bundling the extensions after every change. Other tricks do exist to make this approach work, and there is some hope for future Manifest v3 solutions, but this path is certainly tricky.
It is more likely that Selenium and related tools will continue to work in the foreseeable future given the business demand for traditional browser testing.
Will do, bossman
It should be pretty soon. I’ve got it working already, but I need to test it more and figure out how Firefox profiles work with Playwright.
If you want you can just clone it and replace “chromium” with “firefox”. It should just work, and it shouldn’t take too long to figure out the rest.
“Currently only Chromium is supported. Other Chromium-based browsers and Firefox support to be added soon.”
Hey, I really appreciate that. I’m glad you find it useful.
I got you, boss man. Enjoy the raw speed
Setting it up in .inputrc allows more flexibility and configuration. Plus, it’s shared by any other app that uses Readline for the prompt.
The link is on the body of this post.
learnbyexample has very nice blogposts (or rather books) on GNU and sysadmin topics, samwho.dev has great visualisations on compsci concepts
Right? I wonder why this approach isn’t more common.
How do you do this with vim, btw? I’ve looked into it before but haven’t found a fully satisfying answer yet.
You must have a different version of rm then I do:
$ rm -ir f
Actually I do
$ rm -Ir f
That’s fair.
I don’t really want to be confirming every file in a recursive rm or cp or mv either
Ah but rm
will only make you confirm if there are more than 3 files to be removed. And cp
and mv
only if there’s risk of overwriting. And it’s only one confirm per command, not per file.
shouldn’t be a problem because scripts are run non-interactively and my .bashrc
wouldn’t be read, right?
That’s a good point. If I need something like a bash script I tend to stick to bash features as much as possible.
just trying to get a good mental model of when it’s reasonable to use tools like awk instead of simpler unix tools. also further confirming that sed is almost never the best tool except for substitutions.
Unlike a password manager that just logs you in, Beachpatrol can run any automation task, like checking your email, downloading files, or filling out forms. You have to create Playwright scripts for these tasks and run them from a shell command. There is an example script already in the commands folder, which you can run with the command
beackmsg smoke-test
. The sky is the limit, basically.