I think it's the masquerade that's causing problems for me. I have to keep it enabled since I'm running a tailscale exit node. But maybe I can selectively disable it here.
It's like everything else, you need to actually do it to get better at it. The more you want and try to get better, the harder it'll feel. The best way is to just enjoy doing it. But it's easier said than done.
For me personally, since it's not my job, I don't feel any pressure programming, and it's kind of a stress reliever. I'm not very good at it anyway, but the improvements I've made were due to the fact that I didn't feel any pressure in learning new things, and was able to do things at my own preferred pace. As an example, for the last few days I've been learning about the internal working of SQLite. It's pretty complex, but I don't feel like I need to know and remember everything, so it's easier for me to actually get through it. (Btw, if anyone reading this has experience working with SQLite, let me know, I'd like to discuss some stuff. It's about optimizing some queries, so you don't need to know about the SQLite codebase, just a rough idea of how it works, and some experience with Rusqlite. Fwiw, happy to add you as a contributor in my project if any performance improvements come out of it.)
But it's a different story when it comes to learning stuff for my actual work. Even though the rewards are bigger, the process feels much worse. (Hating on Deligne-Serre representations right now. :( They're beautiful objects, but the pressure to learn is just too much.)
So, if you're like me, try not to take it too seriously, and it'll be easier to learn.
Forgejo and Codeberg are great (I use both), but only for backups, at least unless you're already well known. For small developers, GitHub is pretty much the only platform that might let others discover your project.
I'm happy that you like it. Any kind of analytics or logging is decidedly against my stated policy for this project, so I won't be adding it. But I understand that some might need it, and in that case, one should look at more comprehensive solutions like YOURLS.
Hmm, so that might be out of scope here. But I can try to do some kind of 2FA, shouldn't be much of an issue, really. It's just that I never thought a link shortener needed 2FA protection since the links will be publicly shared anyway.
Won't lie, the main reason that I stuck to a vanilla frontend approach is because I didn't know what else to do. I've never been a frontend dev, and never wish to be one. So I looked at an older project, and started by trying to replicate it. In hindsight, it was probably a good decision. The backend is more intentional though, and I do try to keep things simple and clean.
I'm already aware of a few small UI oddities. There were quite a few changes in the frontend, so I kind of expect these. Please let me know if you see anything weird. You can comment here, or open a bug report. I expect to do a patch release by tomorrow.
Well, it's statically typed, and it's memory safe. (There can be some race conditions during concurrent execution, but that's not relevant for simple scripts.)
It's perfect for daily interactive use, but terrible for scripting. I write almost all my scripts in bash, the only exceptions being convenience scripts for fish itself.
I think it's the masquerade that's causing problems for me. I have to keep it enabled since I'm running a
tailscaleexit node. But maybe I can selectively disable it here.