• 0 Posts
  • 100 Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle





  • Until very recently, I exclusively used the /56 prefix I get from my ISP exclusively. This is still relatively annoying in my case as this prefix changes at least daily for some reason. Clients get their IP via SLAAC.

    I’ve added ULA literally less than a week ago as I have a local reverse proxy I want to handle both local and external request, in both v6 and v4. Obviously more hosts should be accessible from local clients. But I can’t tell local clients apart except by IP, and since the prefix is unstable this would require some sort of hook to update the proxy with that new prefix (might be possible, but seems like a real hassle). So here we are.




  • Just to clarify since it barely came up: NFC can be used for a lot of things, digital payment just being one use case. You can also have “tags” that trigger some sort of automation when the phone is placed there (like on the phone holder in your car, on your desk, on your night stand). You can use it as a key to open doors or locks (bikes). You can transfer your contact information to someone by touching phones together. And so much more.

    It’s a universal way to communicate (very) short distances, with the unique property that the reading device can provide power to the item being read if needed. Not a lot of power, but no batteries needed at all for the passive side in many cases.



  • If you’re using a keepass database, Keepass2Android can natively sync with many cloud options including self hosted and generic ones, even without specific “companion” apps. That’s what I use. In my case, it’s backed by my NextCloud, but it used to be Google drive before.

    Just also sync the file on your PC, merging changes from different clients is part of the keepass database format and “just works”.

    Also VaultWarden works great if your can self host it, but I prefer keepass for a variety of features and integrations.


  • Yeah, they do need to clean up the installer a bit. It’s also not quite turnkey for a Windows dual-boot.

    Mind letting us know why or how? When I installed it almost a year ago on my desktop, I did install it as a dual boot option with no issues. Of course this doesn’t mean there aren’t issues I just didn’t run into. I’m also not new to Linux and didn’t pick a fully default install, if that makes a difference. So I could’ve probably fixed it if it did break, but it never gave me any issues.

    The only thing that I dislike, and that could probably cause issues, is that for my installation the mount point for the efi/boot partition isn’t specified in fstab using a uuid, but using the device name (which isn’t fixed and can change with hardware changes). That is a very weird (and unnecessary) decision IMHO.


  • Forgejo was soft forked from Gitea after they went commercial and changed the license (I think). If there aren’t any so far, expect pay walled features eventually.

    Forgejo turned into a hard fork after communication issues between the teams. I haven’t looked too deeply into it (as I don’t really care about the fact that it’s a hard fork now). This means while it used to be a drop-in replacement allowing you to go back and forth between the two, it’s now an active conversion, I think.