SinTan1729

Well, patool exists.

I hear it every time, but most of my phones barely survive a full day's use. (I've used flagships from pretty much every brand. The only ones that have adequate battery life are brands like Oppo and Vivo, but I don't like them for different reasons.) If they weren't obsessed about making phones as slim as possible, it should be possible to put in even more battery life, so that people like me (and I'm probably not a minority, I hear people complain about this a lot) could have 30% battery left at the end of a normal day, and could be confident about using their phone more on more demanding days (e.g. need to shoot videos, or long video calls).

I haven't met a single person in the last 5 years who wanted a slimmer phone. Phones are already slim enough. We just want longer battery life.

All my servers run AlmaLinux. Install docker, openzfs etc. as needed. AlmaLinux offers a very solid starting point.

Laser printers in general are much better. Hell, my parents have an HP laser printer, and even that works pretty well even after 7 years. (Although it's used maybe 3-4 times a year.)

Also, IIRC there were some concerns with some new policy that Brother introduced. But I couldn't find anything after a quick search, so maybe I'm hallucinating?

শুনে ভালো লাগলো যে এটা কারো চোখে পড়েছে। নয়তো সবাইকে বোঝাতে হয় কি নাম, কেন নাম। আসলে বাঙালী প্রোগ্রামার খুব বেশি চিনি না।

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.

It's just a way to advertise, I think. I've found myself putting more trust in projects written in Rust or Go, than say, JavaScript.

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.

I don't understand much about OIDC either. But I'll keep it in mind. Thanks.

Unnecessary to me, I guess.

Thank you for the kind words.

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.