Looks very much like KDE Plasma. Not sure which distro, though.

Just wanted to throw Kate into the mix of suggestions…

Well… https://lemmy.ml/post/30395990

There are some passively cooled (i.e. no spinning fan) SFF Desktops (HP, DELL, etc.) or you could get a Raspberry Pi 5 and stick it into a Geekworm case. Power consumption with these devices should hover around 5W, maybe slightly higher under load. The Desktops most probably support WoL. The Raspberry Pi doesn’t.

There’s also The Dude - although it’s a Windows-only application. But the visualisation is great.

I’m running SpotWeb to browse spots. It’s kind of a curated list of NZBs. So, most things you can find a spot for, are still actually available to download.

It was heavily used by the Dutch to distribute movies with baked-in (“ingebakken”) Dutch subtitles for older media players.

If you like to checkin manually to places, there’s PrivateSquare which will query places around you from Foursquare (so, 4sq will still see whereabout you are), but store the actual checkin in a local database.

If you want some automated tracking, I’m mostly happy with OwnTracks which logs to my DaWarIch instance. (I’ve previously used Traccar and php-owntracks-recorder.)

While I don’t see any battery usage from OwnTracks, my only gripe is that it can’t increase the amount of points logged when it detects movement because of Apple iOS limitations.

(For iOS, there’s also Geory which will log into a local database and CAN increase the logging by spawning a Live Activity. It gives me the most accurate logs so far. But they have to be exported manually to be stored elsewhere and the author wants to keep the app simple and doesn’t want to implement logging to external systems.)

I let CrowdSec determine that. I’m seeing /13, /12 and even /10 in my decisions list. All seem to be Amazon AWS ranges.

In the Traefik static configuration (usually traefik.yml), add this to load the CrowdSec plugin:

experimental:
  plugins:
    crowdsec-bouncer-traefik-plugin:
      moduleName: "github.com/maxlerebourg/crowdsec-bouncer-traefik-plugin"
      version: "v1.4.2"

(The name for the plugin is defined here as crowdsec-bouncer-traefik-plugin.)

Then, in your dynamic configuration, add this (I’ve used a separate file dynamic_conf/050-plugin-crowdsec-bouncer.yml):

http:
  middlewares:
    crowdsec-bouncer:
      plugin:
        crowdsec-bouncer-traefik-plugin:
          CrowdsecLapiKey: "...YOUR CROWDSEC LAPI KEY HERE..."
          Enabled: true

(The name for this new middleware defined here is crowdsec-bouncer. It uses the crowdsec-bouncer-traefik-plugin defined in the previous step. Make sure these names match.)

You can get the LAPI key by registering a new bouncer in CrowdSec.

And, finally, make sure all incoming traffic routes through the bouncer plugin. You can do this individually, or in general via the static config:

entryPoints:

  websecure:
    address: :443
    http:
      middlewares:
        - crowdsec-bouncer@file
        - secure-headers@file

The middlewares are processed top to bottom.

Any change to the static configuration requires a restart of Traefik to become active.

I’ve recently enabled banning whole subnets if more than 3 malicious actors from that subnet are on the blocklist. This is great for all those DigitalOcean droplets and other cheap hosters used by those people…

I had fail2ban running for several years before switching to CrowdSec late last year. They both work in a similar fashion and watch your logfiles for break in attempts. With the small difference that CrowdSec also lets you use blocklists from the “crowd” to block malicious actors before they even get to try their luck on your machine(s).

I’m using CrowdSec with Traefik and nftables. But there are some bouncer plugins for nginx and OpnSense, too.

I just followed their example configurations for Docker, Docker Compose and then started tinkering with the config until everything worked as desired.

The Bitwarden clients cache your data locally. So even if your Vaultwarden goes down, you’ll still be able to access your passwords. Just not sync new ones or make changes.

I’d throw in option 3: use a KeePass2 database, sync it using whatever sync tool you like (SyncThing, iCloud, NextCloud, WebDAV, …) and use compatible apps (KeepassXC, Strongbox, etc.)

If you’ve got a slow-ish SD card and a game that compresses very well, then this might be the case. But with a modern card from e.g. SanDisk or Samsung with U3 and A2 certifications, this probably won’t do that much.

And BTRFS with compression and deduplication are great to save space.

I’m not sure I’d go as far as replacing the file system. There’s a plethora of tools to do deduplication on ext4 as well. Albeit manually (or via cronjob).

Also, btrfs seems to be slower for random reads than ext4. At least that was the case back in 2019.

While a non-profit sounds very honourable, I personally think Gitea has the more future-proof model. In fact, Gitea Actions was something they got commissioned for and were allowed to open source it as well.

This is basically how I think about it. (Not my comment.)

But we’ll see…

And Gitea has Gitea Actions. The big difference - and also the sole reason ForgeJo was forked - is that Gitea has a business behind it that allows them to sell support hours to other businesses. And then use the money to progress Gitea. Similar to how Zabbix and others do it. But the community decided that this is a bad thing and moved to ForgeJo.

how so?

I’d like to get educated as well, please. So far, ForgeJo doesn’t seem to have any specific advantage over Gitea. (And the name couldn’t be worse…)

If you spin up a Lemmy instance and subscribe to a community, all new posts and comments inside that community will be mirrored to your instance. As I’m subscribed to around 100 different communities, that was a LOT of traffic without me doing anything. That’s why I’ve given up on self-hosting Lemmy just for myself and went back to using lemmy.ml.

However, I do self-host a GoToSocial server just for myself. It’s probably not necessary as mastodon.social isn’t going anywhere anytime soon, but if you’re on a smaller instance, it might be worth it. Also, you get to show off your own domain name. And, while other instances may block yours, your content stays online as long as YOU want it to. There’s no way for an external moderator to delete posts on your own server.

People can find you via Boosts from others or by searching for your @username@domain.com.

Maintaining my GoToSocial so far consisted of simply getting WatchTower to update the Docker container. Migration of data to a new version happens automatically. (Well, there was one accident where some pre-release version got released under the latest tag and I had to use the development branch for a few days … but that was an accident from the GtS-team and shouldn’t happen again.)

I’ve just set WatchTower to one-shot runs and whenever I have some time to fix eventual issues, I start the WatchTower container, it’ll pull any updates and stop again. No need to mess with my compose files (all set to latest) and no need for pull requests or similar.