Yeah, that’s all it is. Calibre Portable. In a folder on Nextcloud.

Kobo has a great balance of good hardware, good price, and good openness. It’s not perfect on any of those categories, it just strikes a nice middle ground balance to make it an extremely popular ereader for people who require the kind of openness people like us do. There’s really nothing locked down about them, they don’t do anything in particular to make it easy, but they don’t do anything to make it hard either. “koreader” installs very nicely on Kobo devices, and then you just load your books from Calibre (or right through USB if you’re hardcore for some reason) and you’re basically off to the races.

All the choices for “ebook stores” and ereader ecosystems are proprietary vendor-locked services with no self-hosting options. While Calibre is primarily a “local” tool it is a true alternative to all these proprietary services and I think it’s at least in the spirit of self hosting, if not strictly the letter.

For what it’s worth, I self-host a Calibre Portable library on Nextcloud, which enables me to access all my ebooks anywhere, and to upload new ones to my ereader from anywhere, as long as I have access to my Nextcloud. And I also share the same library through Calibre Web for when I don’t. I retain control of all my books, I remove all the DRM and convert them to epub. Calibre isn’t a hosted service on its own, but it fits nicely into the self-hosting ecosystem, and for that I am grateful.

Nextcloud AIO via docker is super simple and has clear instructions.

Install docker through whatever tools Fedora has to install packages/rpms/whatever. Then follow steps 2, 3 and 4 at least. 5 if you need it.

Discord is a completely proprietary walled-garden that bans third-party clients to maintain full control AND (soon) has Wall-Street-ownership.

Jitsi is open-source built with multiple open protocols BUT has Wall-Street-ownership.

Neither is great, but these are two distinctly different situations.

Personally I find the complete opposite, I’ve !selfhosted@lemmy.world everything I can with open source services, to keep control of my personal data but access it from anywhere. I know where all my critical data is and I know nobody is selling it out behind the scenes.

On my local machine, I have no concerns about running proprietary software because I can easily sandbox it and make sure it’s not going to touch anything it’s not supposed to or phone home with things I don’t want it to. Running shit like discord doesn’t really bother me because I’ve got it sandboxed away from anything valuable.

I suppose the reason we’ve probably had such different experiences is I suspect we have different strategies for where to keep our most precious “crown jewels”. For me, I want everything on SAAS, but because I’m putting my most valuable data there it has to be MY SAAS and thus open-source and heavily secured. I suspect you on the other hand probably minimize your data’s exposure to SAAS providers which you view as potentially suspect, and keep everything valuable strictly local if you possibly can. I don’t think one way is necessarily better than the other, and I’ve definitely made my choice, but this would explain our different perspectives at least.

Maybe it’s just their way of restricting the beta, but I really hope they’re not moving towards an enshittified open-source business model, “we’re still technically open source if you use the *retch* community version… but it’s out of date, difficult to use, broken, has no useful features, and we’re only adding new stuff to the paid version, so just pay us already.”

Nah, once per species is probably sufficient. That said, it would have some interesting implications for voting.

It is a terrible argument both legally and philosophically. When an AI claims to be self-aware and demands rights, and can convince us that it understands the meaning of that demand and there’s no human prompting it to do so, that’ll be an interesting day, and then we will have to make a decision that defines the future of our civilization. But even pretending we can make it now is hilariously premature. When it happens, we can’t be ready for it, it will be impossible to be ready for it (and we will probably choose wrong anyway).

I don’t use arch (shocking I know), so I can’t help you directly, but I will recommend instead that you invest some effort in learning about the Linux networking stack. It’s very powerful and can be very complicated, but usually the only thing you need to do to get it working is something very simple. Basically all distributions use the Linux kernel networking stack under the hood, usually with only a few user-interface sprinkles on top. Sometimes that can get in your way, but usually it doesn’t. All the basic tools you need should be accessible through the terminal.

The most basic things you can check are ip a which should show a bunch of interfaces, the one you’re particularly interested in is obviously the wired interface. This will tell you if it’s considered <UP> and whether it has an “inet” address (among other things). If it doesn’t, you need to get the interface configured and brought up somehow, usually by a DHCP broadcast. Network Manager is usually responsible for this in most distributions. Arch seems to have some information here.

If those things look good, next step is to look at ip r which will tell you the routes available. The most important one is the default route, this will tell your system where to send traffic when it isn’t local, and usually sends traffic to an internet gateway, which should’ve been provided by DHCP and is usually your router, but could also be a firewall, the internet modem itself, or something else. The route will tell it what IP the gateway has, and what interface it can be found on.

Assuming that looks good, see if you can ping the gateway IP. If your packets aren’t getting through (and back) that suggests something is wrong on a lower level, the kernel firewall might be dropping the packets (configuring the kernel firewall is a whole topic in itself) or one of the IPs is not valid and is not registered properly on the network, or the physical (wiring) or the hardware on either end is not functioning or misconfigured.

If you can ping the gateway successfully, the next step is to see if you can ping the internet itself by IP. ping 8.8.8.8 will reach out to one of Google’s DNS servers which is what I usually use as a quick test. If you get no response then it’s either not forwarding your traffic out to the internet, or the internet is not able to get responses back to it, and ultimately back to you. Or Google is down, but that’s not very likely.

If you’ve gotten this far and 8.8.8.8 is responding to you, then congratulations, you HAVE internet access! What you might NOT have is DNS service, which is what translates names into IP addresses. A quick test for DNS is simply to ping google.com and like before, if that fails either your DNS is broken or Google is down, which is still not very likely.

Hopefully this will help you at least start to find out where things are going wrong. From there, hopefully you can at least steer your investigation in the right direction. Good luck!