A. K. A. Which song do you hate the most?

Requirements:

• Domain registration (duh)
• Privacy.
• DNS included.
• Preferably based in the EU, but it's not a hard requirement

And are there any you would support if you had just that little bit of extra disposable income?

Back story: https://kyivindependent.com/cia-deputy-directors-son-killed-while-fighting-for-russia-in-ukraine-investigation-claims/

This picture is alleged to be the last picture of him alive.

Link: !kittenspaceagency@sh.itjust.works

I'm considering hosting one, and I'm just curious how much effort I should invest in doing it "properly" for everyone to use as opposed to just dicking around on my own for testing purposes.

In short, sell me on ufw.

I learned recently that yfw is basically replacing iptables "everywhere", and as I'm getting old and crusty, this means that I have to learn something new when I'd much rather practice yelling at kids to get off my lawn.

To me, iptables is fine, and I like its flexibility. I've been using it ever since it de facto replaced ipchains, so ease of use isn'treally a factor in this equation.

So my more pointed question is: Can I just stick to iptables, or am I missing out on something that can only be done with ufw?

Are there any canonical references to how fast these two are, for comparison?

Is there an available screen recorder for Linux that can continuously record everything, but only keep the last, for example, 10 minutes in a buffer, and anything older will be discarded?

Sometimes something interesting happens in whatever I'm doing, but replicating it after starting a recorder is hard. I also don't want to deal with terabytes of video backlog.

Ideally, when something share-worthy has happened, I'd push a button or a magic key combo, and the buffer will be saved to a file.

SOLVED:
ReplaySorcery as suggested by @trigg@lemmy.world does the job perfectly and just runs unobtrusively in the background after boot.

I have a system that involves a rather large and complex oracle database, and while the system as a whole is easy enough (for me) to understand, the database feels more like a black box of mysterious powers that I need some assistance wrapping my head around.

Are there any analytical tools to help with this? Ideally, I'd like a tool that would connect to the database and make a diagram over which tables connect to which other tables, as well as naming any stored procedures relevant to each. If such a tool exists, that'd be grand, but any other tools that can help breaking down this rube goldberg machine into something more digestible would be great.

And yes, it is much overdue for a postgresql successor. Getting the current contraption mapped out is the first step in building its replacement.

EDIT: Oh, and this database also interacts a lot with orasched, as well as external processes. A lot of things that should have been a cron job is now a procedure stored in the scheduler. A lot of things that should have been an external script/program is a stored procedure. And most offensive of all: many things that should have been in a config file is part of an SQL table. Whoever built this contraption must've been paid to write SQL and nothing else.