Oh god, please give Osmand faster rendering and search.

This changes a lot with distance. I preder a medium to small one which is not to soft, as on longer rides they tend to be worse for me. There are terrible small and hard ones as well but a good one can be super nice.

I hope they also enhance their social media strategy, as their unprofessional and aggressive way of communication makes me question their trustworthiness more than I want, as I think the project is awesome.

Just imagine you invested sum X back then. Who knows if you would still hold it. Maybe you would have made 10 into 100 $ and quit or shifted some into another crypto and lost it there, maybe you would have gambled with derivates which then did not perform as well. Picking single investments is basically gambling. I know this won’t make your leftovers taste better but try not to blame yourself for decisions that were 50/50 bets at best.

I think it is not maintained any more: github.com/andOTP/andOTP

Well, every second you “miss out” on going all-in on the highest leverage possible and win. Afterwards you always know better so don’t be sad about it. Back then it was probably even more risky than it is now, so depending on your risk tolerance and investment goals it was probably right to miss it.

Volatility can be measured. There is no way to say BTC is not volatile. Historic charts also will not help predicting the future.

I tested WAFs in the past, also ones from the big players and while they might block some cheesy stuff on the application layer, as long as they are not heavily tailored towards your application, they stop bein effective against most manual stuff.
Everything lower than application layer ist not a WAF btw, so I am not sure if you mean WAF or some Firewallish stuff.

Just stick to best practices and expose only what you really need to expose. When putting third parties in front of your stuff this als has data protection implications. If using it makes you feel better okay but it should not feel you more secure if you expose vulnerable stuff.

You wrote:

there’s certainly plenty of implementations which i wouldn’t class as obscurity.

without specifying further. How am I supposed to work out what you mean? I did a guess in my last answer and you seem not to care about a discussion on the topic but instead now question me. I

I just wanted to make clear that port knocking is obscurity and maintaining and configuring your still public facing services in a secure manner is essential. There are best practices which I did not define and are applicable here.

If you whitelist your IP that of course helps but I am not sure what that has to do with port knocking. Whitelisting an IP after it knocked right, that would be obscurity. Whitelisting an IP after it authenticated through a secure connection with secure credentials? Why not just use VPN?

I am also not directly commenting on OPs question, as I try to tackle missconceptions in the comments.