Picard adds IDs too (well, I think it only adds musicbrainz ids, per default anyway, but those are the only ones I care about).

The lookup is automatic as well (you can review or intervene if it fails to identify the release).

It also has a plugin for replay gain (I redo that step in my script anyways) and can be configured to delete any previous tags if you re-process music that you had previously tagged with some other software (IIRC it doesn’t clean them up per default).

If you’ve not used it, I recommend giving it a try before deciding how to go on.

IDK if I’d recommend this to others, but I don’t trust unsupervised metadata lookup (I’m anal like that), so I lookup metadata with musicbrainz picard and then feed the files to beets only to keep my library organized.

My beets doesn’t do any lookup (no lookup plugins are enabled, none_rec_action: asis, fetchart configured to only look at the local filesystem).

If it’s for recruiters, put it on github. That’s the one they are most probably familiar with and you want to minimize barriers to access.

The simplest (= most basic) solution would be to assign several IPs to the machine (you can add multiple on the same network interface) and have each service listen on a specific address.

You’ll need networking basics for anything you do (there are lots of courses on youtube).

After that, you can just follow wherever you curiosity carries you :)

Err… you write markdown and hit “preview” before posting?

Also, the edit box (PC, browser) has a question mark button that will take you to https://join-lemmy.org/docs/users/02-media.html

Terrible posting etiquette

Agreed!

Though it’s very widespread, sharing a link without a word of comment is as obnoxious as those people who send you emails with no text or subject and only an attachment.

I feel less alone knowing that someone else also hates this practice.

IDK if it’s the “best” way, but generally I just let ping run for a while and check the statistics at the end

Sure thing!

(also, please do post about it when you eventually decide to switch to linux)

Setting up an OIDC provider isn’t particularly difficult, but you’ll have to run it as a publicly accessible server in order for tailscale to interact with it.

It looks like you can register at netbird.io with email and password.

In your shoes I’d setup that for now, and later look into OIDC or (probably better) into self-hosting nebula (or maybe netbird).

IDK about the current status of x86 with android, but last time I checked it wasn’t good.

Lineage might be your best bet… it supports a few androidtv boxes (most notably the nvidia shield) see https://wiki.lineageos.org/devices/

where SyncThing is overkill

I just have a dedicated shared folder between my phone and desktop and drop oneoff stuff there (it’s also easier to script this way)

For files I use syncthing (also for music/photos/notes/etc… syncing files is IMHO the way to go wherever applicable).

For sending links to my PC (eg. articles linked from podcasts’ notes) I used to rely on firefox sync, but I’m starting to distance myself from Mozilla so I am gonna experiment with wallabang.

For sending small notes to myself (stuff that I want to sort or act upon when I get to my PC), I’m using signal’s “note to self” but I’m investigating alternatives because signal doesn’t mark such messages as unread and so sometimes I forget I’ve sent some.

That’s called dogfooding, not self-hosting :)

Let me get this straight though: I’m not saying no project self-hosts their code (eg. IIRC both KDE and Gnome do), I’m just saying that the majority of FOSS projects (including those that are dedicated to self hosters) does rely on some sort of third party to host their source code.

I don’t think it’s fair to criticize a FOSS project just because they rely on a third party (even commercial ones) to publish their source code.

Yep but eksb’s comment was about selfhosting, not FOSS or ethics (same can be said for this community, although that’s less relevant than the specific comment of course)

Even that is questionable to say the least: while codeberg is the main fogejo contributor, the forgejo project and codeberg are separate entities with separate governance and funding.

I’ve blocked the bot because I find it’s more annoying that useful (I’m not complaining - just giving feedback).

That said, IMHO from that list you should remove the entries that:

• are ambiguous (eg: HA has 2 entirely different meanings in your list)
• have become words on their own (eg. DNS, HTTP, etc…): nobody cares what these expand to (think, NASA) and also knowing what these expand to doesn’t help at all (if you tell me that HTTP means “hyper-text markup protocol” will I not have to go read wikipedia anyways to understand what it is?)
• are often not used according to your definition (eg. IP is more often used to refer to an IP address rather than to the protocol) - of course you may want to amend the definitions instead

Also, you should keep the acronym expansion (“RAID” => “Redundant Array of Independent Disks”) from any comment you may want to add (“for mass storage”) and - since you are at it - provide relevant links to wikipedia articles and/or other resources.

PS: since a lot of entries in the list are not even acronyms… maybe you should consider renaming the bot to something related to “abbreviations” or “glossary”?

What self-hosted software you use is not hosted on some third party forge?