FreshRSS might be worth a look. Has most, if not all, of what you're looking for. The paywall ladder might require a plugin.

I’ve been paying for it for the last year or so. Whatever the mid level is. Part of the value is that I’m not reminded of what I filtered out—which is a double edged sword. But when I find myself on someone else’s device that defaults to Google or Bing, I do see the difference (again).

Presumably any CalDAV server would be sufficient. But I’m sure there are gotchas.

Have you checked out mice marketed for gaming? Particularly for MMOs, you’ll find a few 10+ button mice. I’ve been a happy user of Logitech’s line up, for what it’s worth.

I use Digital Ocean's App Platform which has free hosting for 3 static sites. CD is setup through integrations with GH/GL/BB, if I recall correctly. No particular reason why I chose this, other than I had a DO account open already for a few latent domains. It's proven to be simple enough & batteries included.

The only consistent ones for me are TrueNAS and FreshRSS. Other apps haven't lasted as long in my network.

Setup a confidential information & inventions assignment (CIIA) agreement to protect the IP created for the company, alongside the rest of the employment agreement.

Also, if your concern is judging their character, consider adding another person that you trust into the interview process. Either as a technical or behavioral round.

`xargs` is a helpful command to keep in mind. I use that surprisingly often when scripting something up.

- https://linux.die.net/man/1/xargs

Are you looking for something beyond what a host alias in your `./ssh/config` file can provide?

  $ cat ~/.ssh/config
  Host myserver
          HostName 10.10.10.10
          User ken
  $ ssh myserver

Correct, I'm looking for a tool that manages a large list of individual hostnames, I do already extensively use my ssh config to automatically apply the right credentials etc. to the hosts once I have the hostname I want.

Assuming PRs and associated feature branches are substantial[0], I'm a proponent of merging w/o squashing commits. When running `git bisect` or simply doing archaeology on a code base where the previous author(s) left the organization, I've never regretted reading granular commits--only too coarse.

[0] Largely depends on the team's workflow and the functional size of feature branches. If there are a lot of smaller commits made to develop/main/etc., then you can probably get away with squashing.