If you have trouble because the clients do not support native oauth, you can try to use a auth dameon like https://github.com/ltratt/pizauth

I enjoyed the article anyway. Thanks for sharing.

To make a callout on ! Is ridiculous since it’s literally meant to overwrite the compilers descicion. Ignoring compiler warnings is known to be a bad idea, I mean otherwise there would be no warning at all, right? This is why zero warning policies exist.

Once we get to the point where we think the programmer has no responsibilities at all, we are lost anyways.

Gitea supports Debian and other formats. https://docs.gitea.com/usage/packages/debian

I personally work for more than 20 years as dev and really hate to see myself as senior. I think I am more of a Veteran. I only have more practice and survived more projects. What I am trying to say is, give yourself time. Nobody starts out and knows everything. And even if you have experience, there is always a bigger fish. Simply because the topics are too complex to know them all.

Nice site. I would like to see badges for the tools which quickly indicate certain features. In my case I’m particularly interested in tools which have vi key bindings.

Oh my god! This struck right into my soul! Very good read and something which deserves your attention.

Edit: I misread the statement. Thanks for pointing this out to all the repliers! My fault.

The first point of the answer is misleading. Tor is indeed designed with anonymity in mind. The leaks occur in different layers, like the for e.g. chosen BitTorrent client.

https://blog.torproject.org/bittorrent-over-tor-isnt-good-idea/