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

help-circle
  • Yeah, I don’t think you understand Calibre at all, because you are somehow annoyed by it. I get it. But there’s no e-reader on the market that supports Calibre. Quite the contrary, there’s a titanic effort from the Calibre team (it’s been several people since 2009) to reverse engineer support with every single e-reader and tablet in the market that should not be minimized. You’re also painting a picture as if somehow Calibre is the Windows of e-book and everyone hates it but is forced to use it, when in reality that is not at all the case. Yes, it has quirks and people have constructive criticisms, but calling a guy’s name “rough” is not positive criticism. Overall, most people appreciate and like Calibre for what it has achieved and enabled for readers all around the world.

    Again, it’s fine if you don’t like it, don’t understand it, and don’t want to understand it. But that doesn’t excuse insulting a person who actively is making your petty life a bit easier and free from corporate control. It takes a very weird person to feel like commenting negatively on someone’s name is somehow appropriate, it’s bully attitude. If that is all the criticism you can bring to a discussion of software, save it for yourself and stop replying. You’re all over this thread complaining, completely unprovoked like a little wuss. No one is forcing you to use Calibre, it just so happen that no one has done anything better, as you yourself admitted in another comment.


  • Good, so if you know what needs to be fixed it should be easy for you to make a new alternative, with modern web UX, self-hosting in mind and NO quirks whatsoever.

    Really, it’s so easy to insult those who are making solutions when you have never contributed at all. There’s constructive criticisms, but calling people who are fronting free labor for your benefit as nerd aliens is not it.


  • Calibre is so old that it’s use case and architecture precedes the current popularity of self-hosting. It is as old as the premiere of the very first e-ink reader in 2006. It’s not obtuse or weird, it was just the way things were done 20 years ago. The problem is that adapting it to work as a self hosted app or even multi user sync requires rewritting all of its backend from scratch with fundamentally different principles and use cases in mind. And guess what? Everyone is way too lazy to face that massive undertaking. Thus the hobbled together solutions.

    Fortunately, one way backup to a NAS works perfectly fine to keep libraries secure. It’s not this way out of caprice, and the Dev is definitely not an nerd alien.

    There have been attempts to create modernized replacements for calibre. But they all fall through because, Calibre already does 99% of what they want to achieve. That one percent is covered by addons and shoddy workarounds? Yes. But that’s an effort to reward analysis any Dev is faced with. Calibre does much more than what the average user need, and they keep adding features. Because they’re not catering to one particular user but a community of a complex mix of users. Developing software is hard, rebuilding 20 years of features is daunting.



  • There’s three types of NVIDIA failures on Linux:

    A- The niche thing that doesn’t work for the group of people who use it.

    B- The specific card model that doesn’t work.

    C- The distro that for some reason is a nightmare to install the drivers.

    Each motive individually is not a lot of people, but all together it is way much more than AMD. Hence the difference.

    Also, if you have a type A failure card, there’s a probability that maybe it will be fixed eventually. But for type B, you’re out of luck. There’s a non-zero chance that your card will never work.

    Type C is entirely up to user error and distro effort. But it won’t help with type A and B. If NVIDIA of fails you, whether you can install the drivers on your distro or not, is irrelevant.


  • If anyone is thinking about having a rooster, though, make sure to also have chickens for it to court and mate with. Because roosters without chickens get crazy and start singing at all sort of inappropriate hours. Not fun waking up at 3 Am to a rooster having a psychotic breakdown because it doesn’t have any social interaction. Or random screams at midnight that don’t let you fall sleep because the poor thing is lonely. Be aware.










  • I also tried tailscale in a docker container as a subnet handler and realized I was out of my depth. Net engineering is abstract and hard. There’s a reason there are pros making bank just doing that for big corps.

    Followed a way simpler setup. Now tailscale runs on the server bare metal and podman handles the routing automatically. I just use the magicDNS address given by tailscale and everything just works as intended. All my services are available, and apps run no issue, no matter where I am as long as I’m connected to tailscale. I will make the setup more complex as I learn more and acquire the need for more features. But so far this has met all my expectations.





  • I was mostly joking, of course. I appreciate the use case. It’s just that 99% of people are spinning new machines once every decade. Having a reproducible setup is something of interest for a very narrow band of system managers.

    I truly believe that for those who are spinning new hardware every day and need an ideal setup every time, a system image is far more practical. With much more robust tooling available. I’ve read other replies and for them all, I notice that using Universal Blue to package and deploy a system image would take a tiny fraction of the time it takes just learning Nix basic syntax. It’s so niche it seems almost not worth any of the effort to learn.