dominiwe

I actually did absolutely need it recently when I golfed together a shell script that is simultaneously a valid YAML file [0]. Sometimes having no-op tokens is nice!

[0]: https://domi.work/blog/posts/compose_polyglot/

In reaction to recent AUR supply chain attacks, I am working on two small tools to try to help address the issue for myself.

First, `aurgate`, a small AUR helper which is more barebones than alternatives but provides a "full diff" workflow. The idea is to make upgrades feel like a "full diff review" and also support graphical tools like meld or the vs code diff viewer.

Second, `flatgate`. This tool is inspired by LittleSnitch and Flatseal. Here the idea is to "default deny" all permissions of newly installed flatpaks and allow/whitelist per invocation (where possible) or on first use.

Relevant, a golfed systemd polyglot file that is simultaneously an executable script: https://domi.work/blog/posts/compose_polyglot/

Yes, I have too much time sometimes... and I agree, I don't like the syntax.

I recently had a desire to enable PiP and video controls in teams.

I was able to contribute it to this project which was a genuinely good and smooth process.

If you start the app with '--videoMenu' new menu options to enable/control this appear.

Wow, I completely forgot about that image! Thank you for reminding me (it is now gone).

It was an experiment a while back and it was inline in order to keep it all in one file. Actually that made me realize, my site is dynamic: Because I edit this one html file live on the server to make changes, whoever loads my website repeatedly while I'm doing that is going to see changes live.

I did the same: https://domi.work/

And it's also ugly :)