Sounds like social media for a specialised case. Thanks for your explanation.

I never never cared about my own or other people’s music listening history. And I never talked to someone who does. So I never needed a word for the thing, I guess.

Scrob…what?

wikti

Verb scrobble (third-person singular simple present scrobbles, present participle scrobbling, simple past and past participle scrobbled) (Internet slang) To publish one’s media consumption habits to the Internet via software, in order to track when and how often certain items are played.

Noun scrobble (plural scrobbles) A datum or the aggregate data collected by this means.

It really depends on the use case. 😏

Witchcraft.

Who doesn’t. I’m sure he also consumed bread. (But I fail to see the connection with the case. )

:) the hardware is still more capable than a brick:
Plug in favourite installation media stick, push reset button (if there is one), reinstall.

Can an OS be bricked?:

A brick (or bricked device) is a mobile device, game console, router, computer or other electronic device that is no longer functional due to corrupted firmware, a hardware problem, or other damage.[1] The term analogizes the device to a brick’s modern technological usefulness.[2]

Edit: you may click the tiny down arrow if you think it can’t. ;)

Yolocopter ;)

Flying taxis

One aspect is how interesting you are as a target. What would a possible attacker gain by getting access to your services or hosts?

The danger to get hacked is there but you are not Microsoft, amazon or PayPal. Expect login attempts and port scans from actors who map out the internets. But I doubt someone would spend much effort to break into your hosts if you do not make it easy (like scripted automatic exploits and known passwords login attempts easy) .

DDOS protection isn’t something a tiny self hosted instance would need (at least in my experience).

Firewall your hosts, maybe use a reverse proxy and only expose the necessary services. Use secure passwords (different for each service), add fail2ban or the like if you’re paranoid. Maybe look into MFA. Use a DMZ (yes, VLANs could be involved here). Keep your software updated so that exploits don’t work. Have backups if something breaks or gets broken.

In my experience the biggest danger to my services is my laziness. It takes steady low level effort to keep the instances updated and running. (Yes there are automated update mechanisms - unattended upgrades i.e. -, but also downwards compatibility breaking changes in the software which will require manual interactions by me.)