![](https://fedia.io/media/02/84/028416d3618528eb4fbfdb6af5f155506472e83b31a5668f363b3032d74b8c6e.png)
![](https://lemmy.dbzer0.com/pictrs/image/a18b0c69-23c9-4b2a-b8e0-3aca0172390d.png)
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.
I’m a worldbuilding consultant and fanfiction writer for the Pokémon fandom, also work with computers ‘n’ stuff. Linux user (but not Arch, btw).
I have a Mastodon btw as @VeniaSilente .
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.
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.
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.