venia_sil

"The shareholders will now decide your fate"

"Your cat has been delivered" – USPSPSPSPSPSPSPSPSPS

Starting up wikis is so easy nowadays that there's no excuse. I maintain a few Dokuwiki-based ones, it's my preferred engine for simple wiki stuff, but Mediawiki (the same one that powers Wikipedia) is not bad either and not really too difficult, just a bit more demanding storage-wise. Heck, you can currently fire-and-forget DW-based wikis on SDF's "one payment" access tier, even! Probably on Neocities too, haven't checked.

Sounds (heh) good in theory, but so far it hasn't been able to pick any radio in my country (Ar) or nearby. Inspector says any attempt to load a radio ends in a HTTP 403 error.

Thanks for your work! I honestly don't say this enough.

Protip:

Just don't have a live Windows partition.

To be fair (and this is something I don't recall being established with or dealt with in the video) you need to at least trust that the backend is there. Currently if "lol CIA AWS" servers are not working, you don't have an option (Advanced Settings or whatever) in Signal to choose another provider, such as say a self-hosted community server.

One would think that Firefox would have a command somewhere to re-export the currently installed extensions. Useful for migrations, replications etc.

I use SQLite to power up lots of stuff I'm working on. It's lightweight, fast, simple and well-documented for small projects — like a Postgres but very local. Saves me from having to deal with containers "just to store data", let alone for moving stuff to other machine where I would also need the permissions to configure and run containers in the first place; whereas all you need to pass SQLite databases along is scp / rsync.

Reason enough to <del>use something else if possible</del> read the docs.

Firefox ESR is basically the LTS of Firefox. Over a portion of the normal ("stable") Firefox's release cycle, ESR will get security fixes and backports, but nothing that changes interface or expected UX behaviours. It's basically there for keeping an environment that is consistent and predictable over a reasonably long term (~1 y) which is why it's the Firefox version that gets shipped with eg.: Debian.

In general, ESR is the default version I install for anything clients-wise that for some reason requires that we don't intervene client machines too much (including maintenance). It's fire-and-forget once you have the usual extensions rolling like uBlock Origin.

Memory wise it's also quite reasonable in its usage and I've found it's far more responsive to customization of in-RAM memory usage patterns than stable, nightly or develiper Firefox, who tend to ignore or misinterpret my requests such as "only use up to 16 MB of cache in RAM".

One part where maybe ESR is too conservative is the HTML / CSS lexer. Because it's intended to stay stable over very long periods it gets stuck with stuff like still not accepting CSS :has(), and it seems the next ESR won't support it either, whereas Nightly does already. Also, because behaviours are retained as long as possible, bug UI breaking changes such as the migration off Australis or the incorporation of the Extensions Button are a more jarring clash in ESR than in normal Firefox, because you get all those workflow-changing changes in one BIG update.

. It's not like they can buy the Fediverse.

They don't need to. They only need to buy the admins. And we know that some admins have annouced they are for sale.