

Yeah, but I could also use a shortener. It’s more ergonomic, easier to use, edit etc. Different tools exist for a reason.


Yeah, but I could also use a shortener. It’s more ergonomic, easier to use, edit etc. Different tools exist for a reason.


While I agree on principle, we’re not always using big-name websites. The argument falls short for some-local-blog.com, there’s no security improvement on clicking that link as opposed to shortener.tld/blog-link. I’d say we should trust the source of the link instead of the link itself. Link shortening can be useful if you want long links to look nice when sharing, or simply for personal use so that you don’t need to remember long links to access an internal resource. Or just for personal websites. I can link my CV at https://domain.tld/cv instead of the full PDF file path, for example.


I was already using Vaultwarden for the server, just switched to Keyguard on Android and Desktop. Works perfectly.
There seems to be an open PR for a browser extension as well. Hope that’s merged soon.


Even though I avoid everything Microslop and Adobe like the plague, I think it’s a good thing overall. There are many who would like to use Linux, but can’t due to their work needing Office 365 or Adobe Creative Suite. If someone manages to make the latter work in Linux somehow, a large number of people will be enticed to switch to Linux.


Thanks. Filtering does not cover expiry, but it does cover shortlinks, longlinks, and notes. Making expiry work will make the filtering inefficient for little benefit, since the expiry times are stored as UNIX timestamps in the database.


For most “normal” setups, no. Networks, environment variables, volumes, permissions etc. map pretty much one-to-one.
If you’re using compose, you can even keep your setup mostly unchanged and use podman compose. Although, I would recommend learning a bit about quadlets and using them instead. There’s a tool called podlet that can help you translate your docker commands to quadlets, although it’s not complete and does miss some features. The annoying thing can be some QoL tooling that exists for docker compose that doesn’t for quadlets e.g. automatic restart for changed quadlet files. I wrote some scripts for most of these situations. I will probably release them at some point after I make sure that they don’t rely on any specific properties of my setup. But you can easily write them for yourself if you know some shell scripting.
For docker run commands, you can mostly get away with changing it to podman run.


Yes, my sister uses Gnome, and I’m basically her IT support. I just don’t see any reason for switching. It’s too limiting for me.
I also used it for a month or two on my own machine before I switched back.


I’ve been using KDE for about a decade now. It’s polished, and works well. Plus, it’s also highly customizable, so I’ve never had a reason to switch.


The question has been answered. But since you seem to be new to containers, I’ll just give you a recommendation. Just use podman. It can do pretty much everything that docker is used for, but it’s rootless by default.


Silksong is easily the best game I’ve played in the last few years. If you haven’t played it, I’d highly recommend. It’ll be worth every penny.


neovim
It just feels right. It took me some time to get used to the vim motions. But man, does it make moving around any project so fast and natural. I went in for the customizability. And that’s obviously there. But the sheer speed it gives me is uncanny. My past self with VS Code could never.
I’d also suggest taking some time to write your own config from scratch once you get the hang of it; it’ll be worth it.


Idk, I feel like it’s blown out of proportions a bit. It’s always supposed to be unsupported, and users are supposed to look at the PKGBUILD files. I know most people don’t, but I don’t think that’s AUR’s fault.


I love the rolling release model, and the AUR. (I even maintain some packages on AUR.) I have installed and used pure Arch in the past, if only for the rite of passage.
But nowadays I mostly use EndeavourOS. It’s basically Arch once it’s installed, but has a nice and fast installer, with great defaults. Also, the community is awesome. I rarely need any help anymore, but I still like hanging out in their forums helping others, and generally chatting about non-Linux stuff.


Fair enough. I’m not a professional programmer, so I guess I won’t understand your frustration with long term maintenance of Go code. I do agree that it can be unnecessarily verbose. Writing something as simple as an http server takes a long time. Also, the dependency management sucks. It can’t seem to decide if it wants to be declarative or not.
I do like that it’s dead simple though, and that the standard library has most of the basic stuff. I’ve mostly replaced the need for Python with Go, for small CLI apps. Nowadays, I only use Python when I have to use some specific library, mostly for mathematical computing.


Yes. IIRC, the flavor that I used was MSWLogo.


I don’t think there’s an std-way of doing it, but the Rust ecosystem has this thing where people usually settle around one library. In this case, it is tokio. Afaik, most async stuff is done using tokio. What little async I’ve used, it’s been using tokio or some library like actix-web that uses tokio under the hood.
Also, side note, I never understood the idea of why golang is ugly. I think it’s fine, except for maybe the repeated if err != nil guards. Those are ugly. I wish it used additive types for error handling.




I’ve always preferred the functional approach to programming, so OOP never really intrigued me. That’s one of the reasons why I never liked C++ or Java, but instantly fell in love with Rust. It lets me do a lot of functional style programming, while still being somewhat practical. (I’m looking at you, Haskell.)
OIDC was requested quite a few times. I finally understood the point when I started using it for my selfhosted apps lol. It can be very convenient.