I think unix signals are a bit lacking for your use case now. I'd consider having the daemon also have a web interface that you could then have the web server message. You mention systemd also, so could also consider MQ message queuing or D-Bus. Getting these to scale across computers isn't as simple, hence my http suggestion initially. HTTP should also then be OS agnostic
Given the concern, it would be good to be explicit in the blog post. What other assets does it genuinely need? The code is open source, people are free to host instances
So with british law, the intent of the law is as important as the written texts. Listen to the debates which can and are used by judges from the commons and the lords to decide upon intent. It's not for tiny forums, but I'm also not a lawyer. Significant most likely relates to not just user count, but also other reporting from other media, it's significance of significant users, anonymity, and ability to break bigger stories. Try codifying any of that (and more!) in a law
I don't believe it would target any of the fediverse currently. No instances have significant volumes of users or target markets. This is designed to target facebooks, tik-toks, and twitters. Services that do influence populations. Essentially, making these services actually responsible for their algorithmic output and akin to publishers in the UK
Simple. Don't be a company. Companies exist to sell stuff: the fediverse doesn't. There are a few other structures in the UK alone to circumvent this potential law, which is designed to combat large social media companies. And it won't affect outside the UK either, and with brexit - will anyone else bother enforcibg?
If you don't know, ask a stupid question to yourself. Then ask it again in a more intelligent manner to a rubber duck. Then a real person. One of these three will give you an answer
TDD is the answer to the second part. Seriously, just try it. Don't do it for every task after, but do try it!
Notes, tickets, knowleadge bases, READMEs, well written code that is easy to understand, tests that are descriptive, ADRs. Nobody can remember it all, the hard part of programming is making it easy for the next change. Remember it's likely to be you, be kind to your future self
And imposter syndrome never goes away. And this is a good thing - "don't get cocky kid". It does get lesser though, and then you get more responsibilities! But really, if you aren't questioning why and what you are doing, how do you trust your past self? Embrace the imposter, realise we are all imposters to a lot of extents
That's certainly reason enough for most people. So long as there is some actual spark then what's not to love? You may well still get grandchildren and he's unlikely to be seen much. The age gap certainly fails the creepiness test, but no crimes are being commited and both are entering into it with good faith. You may well struggle for some time, but for the good of all - button that beak and smile
I think unix signals are a bit lacking for your use case now. I'd consider having the daemon also have a web interface that you could then have the web server message. You mention systemd also, so could also consider MQ message queuing or D-Bus. Getting these to scale across computers isn't as simple, hence my http suggestion initially. HTTP should also then be OS agnostic