Whisper is the way to go for speech to text (edit: had that backwards). Whisper.cpp is decently fast too: https://github.com/ggerganov/whisper.cpp/releases/tag/v1.7.1 Get the binaries from the link that’s on that page (god GitHub usability sucks)

I want to second Pelican for Python. Really easy to set up and get going. No need to learn a complicated templating language (it’s jinja2, which is what everything uses).

yeah, but it’ll be hard to make those Y Combinator vultures rich at that price

No, I don’t think so.

Tinc has weird limitations and Wireguard completely obsoletes it. There’s zero reasons to ever consider using Tinc when Wireguard exists.

How are the alternatives any better? Download a DEB that executes arbitrary code, signed with some .asc that’s sitting in the same webserver? Download an EXE?

Your comment is so rambley that I can’t understand whether you’re criticizing the distribution method or the packaging. Both of those are very different in terms of attack surface, if you’re talking about supply chain attacks.

I haven’t tried it personally, but Mox looks like a nice modern mailserver. It might do what you want.

Every time I look at this, the value proposition makes no sense to me. The DIY V1 and V2 only have instructions for adding a single HDMI input port (??), and the V3 and V4 are like $350 CAD, which is way more expensive than buying a used KVM on eBay. What am I missing?

I don’t want to dox myself so I’d rather not say, but it was some time ago and I’m no longer leading that project. I do still do development in the same field though!

Your post couldn’t be more true. Decades ago I was sold on MythTV, this PVR software but it only ran on Linux and you had to compile it yourself. So I gave Linux and MythTV a shot. As it turned out, both MythTV and early desktop Linux were a buggy, frustrating mess. X broke all the time. Incomprehensible, ungoogleable compile errors all the time.

I spent so much time troubleshooting MythTV and compilation problems that I ended up learning Linux inside and out and the C programming language to be able understand the compile errors. I went on to lead a major open source project and have had a long career as a programmer, using all the knowledge I gained that started with fighting MythTV.

I have no experience with portainer, but some apps have an option to disable new user registration, and that’s what I would recommend first. (I do use Keycloak myself too)

I don’t see anyone else actually telling you how to figure out if you’re being DoSed, so I’ll start:

Check your logs. Look at what process is eating your CPU in htop and then look at the logs for that process. If it’s a web application, that means the error and access logs for it. If you see a flood of requests to a single URL, or some other suspicious pattern in the log, then you can try blocking the IPs associated with them temporarily and see if it alleviates the load. Repeat until the load goes down.

If your application uses a database, check your database logs too. IIRC postgres logs queries that take longer than 5 seconds by default, which can make it easy to spot a slow query especially during a time of high load.

I don’t think DNS amplification attacks over UDP are likely to be a problem as I think most cloud providers filter traffic with forged src addresses (correct me if I’m wrong). You can also try blocking all inbound UDP traffic if you suspect a UDP flood but this will likely break DNS lookups for you temporarily. (your machine should not have any open UDP ports in any case though if you’re just running Lemmy).

If you want to go next level, you can use “perf” to generate a system-wide profile and flamegraph which will show you where you’re burning CPU cycles. This can be extremely useful for troubleshooting performance or optimizing applications. (you’ll find that even ipfilters takes CPU power, which is why most DDoS protection happens on dedicated hardware upstream)

I’m not OP but Keycloak is pretty usable for SSO. I’ve configured about 8 different web apps to be integrated with it via OAuth2.