Not really relevant, but I’ve got a “rule of thumb” for all security-related issues;
“If it doesn’t nuke my PC, then I’m good. If it does, then I’m still good since backups and logs exist, and if it was related to the latest seucirty issue? Then I make a quick patch and/or update. Then back to 1.”
There was somebody on the Linux reddit with a self hostable ebook app just a week or so. It looked slick but wasn’t really that useful for me. Might be worth a look.
I feel that I’m usually more upset that apps choose electron and I have performance issue because they didn’t spend time writing a proper lightweight desktop application. I feel like Calibre is actually one of those apps.
I could see portability across devices being useful but is the Calibre interface really going to be conducive for that?
All the other services I have running are on a server in my closet, which I access with a web browser from other devices. Calibre needing to run on my workstation is a big shift in that workflow. Especially because all the rest of my media is sitting on that server.
Also, UX of open source desktop apps is… lacking. They don’t look good, and they don’t feel good to use. But that might be because I’m picky and spoiled by decades of using a Mac.
I definitely don’t want more Electron apps. About the only things I want to run locally is a browser, a text editor, and a terminal.
That’s fair but I think one of the most critical features of Calibre for me is interfacing with my e-reader over USB to download/upload my epubs. I don’t know how that would work from a Browser app.
You can use Podman too, if that would be a problem.
Look at StirlingPDF if you want an example how to run OR are interested in a great web-UI PDF editor based off various open sourc tools, in a single interface
It’s unnecessarily annoying to set up, as the other user pointed out. But it can be set up by itself using hub.docker.com/r/linuxserver/calibre-web docker, and used standalone. The only trick is needing an empty database.
Can you explain bit more please. I have calibre-web running, downloaded empty database, added some books in the same folder as database, but nothing is showing up in calibre-web gui. Did I miss something?
I have done something similar following this post - loads of others have created similar scripted installers for Arch for their specific use cases and this guide takes it one step further with custom arch meta packages that hold deps and system wide config.
You can also do similar things with tools like ansible or saltstack or similar tools. Though these all take the approach of define your configs and system to automate the setting up of a system approach rather than the backup or clone an existing system. So are more effort initially but are able to keep multiple system in sync with system configs with far less effort then trying to create a backup/restore system for organically created configs.
that wouldn’t work (I think) because my laptop has vastly different hardware
Should not matter, you can install all the packages all your system need - such as both nvidia, amd and intel graphics drivers and the kernel will only load the ones for the hardware you have booted with. Or if you really need different configs or packages for different systems the various approaches have ways to do that.
Most done with the latter. But the nice thing is once you have done it once it is much easier to keep things up to date and in sync from then on words. You can also peace meal it - setup one application at a time and migrate things one by one over to it.
painstakingly manually code every unique facet
That makes it sound a lot worst then it actually it. It is only a bit more effort then setting something up for the first time manually. And pays its self back many times over when you next need to reinstall or install a new system. Assuming you keep up with making changes to the code and not directly to your system each time.
This is basically the reason why I wanted to ask early. Two problems.
Already kinda late… And, idk how to configurate Firefox addons from the terminal. Even if I did, there’re a bunch of other apps too. I’d need to do so much research.
The easiest step into this world is KDE. It has a store for users to share global themes, color themes, even sddm animations.
You can use kwin rules to send certain apps to certain desktops, start shaded, all sorts of fun stuff.
And then you can throw a tiling manager on top of that. If you want to use the control panel, you can install bismuth. If you’re comfortable editing text files, awesome or i3 (but I have yet to go that far).
If you really want to go for it, hyperland looks incredible, but it is a lot of up front work.
The survey was absolute hell on mobile until I actually read the part where it says you can just double click. Made it so much easier. I personally chose the more intricate designs as my favorite and less intricate and more simplified designs as my least favorite. Detailed and intricate designs or nothing for me.
So glad they’re moving forward on the non destructive front! Non destructive editing such a useful feature. I will always prefer to be able to non-destructively edit things I’m working on to easily be able to change things if necessary or to be able to see how I did something in the future!
I used to be super excited about Wayland but it’s been 15 years, now I’m too old to care.
My favorite distro still runs on xorg and it runs so well that I don’t remember why we needed Wayland in the first place. (I am not saying that there is none)
Tearing videos and games have been fixed on xorg when Wayland was supposed to be the only solution.
I am sure Wayland will eventually make X completely obsolete and will be a much needed modernisation of the Linux desktop stack.
But I can’t help but notice that it is not there yet, is old enough to carry it’s own significant technical debt and might never bring the simplification and streamlining that it once promised.
It is a tiling Wayland compositor that is only a couple of megs in size. On Oasis Linux, I launched into Velox, opened a terminal, and checked the memory usage. It was under 30 MB of RAM. That is for the whole system!
That experience made me think differently about Wayland.
There was only one Xorg. For me, the evidence that it was big and complicated is best expressed by the fact that, over decades, the number of projects that competed to provide X had dwindled to one. There was loads of unhappiness with it and yet, there were no forks. Why?
Now Wayland. There are new Wayland compositors all the time now. I just saw one yesterday—Louvre. The basis for Velox above is SWC. There is Wayfire. There is Weston. There is of course wlroots. And both KDE and GNOME have made their own. I think somebody even wrote one for Haiku! For me, this is evidence in itself that making a Wayland compositor is easier than implementing X.
It also means that all these Wayland compositors can compete with each other and drive each other. It means that I, as the end user, can pick a super stripped down version when that is what I want and an all-singing, all-dancing version when that is what I want instead. In some situations I will be happy with, and thankful for, Velox and in other situations I will want GNOME.
It is taking a long time and the journey has not been smooth. That said, I am becoming quite confident that we are in a much better place. For normal uses, Wayland is in a good place now. The level of innovation is very high. Dev can start to shift from the basics to the extras. I fully expect that we are heading into an exciting time on the Linux desktop.
X has a singular fully functional implementation into which you can slot a wide variety of components. Because everything is a component that slots into the singular X implementation forking has both a low benefit and a high cost.
Wayland is just a protocol everyone must implement with a semi useless reference implementation that nobody would ever use. Nobody forks Wayland they just implement it as they must the X approach isn’t available.
It’s apples to oranges. A meaningless comparison. Its more just churn than innovation on the part of desktops.
That said, everything you said about the Xorg server could be said about wlroots. Nobody has to “implement Wayland because they must” anymore. The X approach is available in Wayland as you can build your window manager on top of wlroots and many do.
Seems fairly apples to apples to me.
Or you can choose a competing compositor library as there are now quite a few available. I think XFCE is looking at using Wayfire. Or you can control more of the stack directly and write your own as GNOME and KDE are doing.
Not only do you not have to implement Wayland to make a window manager, because compositor libraries are available, but people are writing Wayland compositors even though they do not have to. Louvre is a compositor recently released that seems expressly designed to make writing new window managers super easy.
As for innovation, there seems to be lots in Wayland. Valve just added HDR. GTK is looking at using dmabuf. There are already Wayland window managers that are not ports from X. There seems to be innovation at every level.
Building on top of wlroots is still a different scope of problem than writing a window manager for X. Pretending its the same thing doesn’t change the fundamentally different architecture even if it certainly makes it easier.
Out of all the libraries isn’t recent KDE the only fucking one that supports proper scaling of xwayland windows without turning it into a blurry mess? KDE which nice as it is lacks most of the nice tiling features of i3wm or the per monitor workspaces? Let me rip out and throw away a highly functional Nvidia GPU and come on down!
Don’t worry in another fucking 10 years all problems will be solved in the meanwhile I’ll just be fucking using non-beta software. Pardon me if I’m a little annoyed. Wayland has been the future for a while now.
Yeah, I don’t see a reason to use Wayland unless it’s a drop-in replacement for X.
I don’t have any issues with X. I’m glad it works and I don’t even know it’s there.
It doesn’t make sense for me to adopt something newer that works worse when I have something that works without issue right now.
I bet when Wayland reaches the maturity, adoption, and stability of X, people are going to be moving to the next broken thing that will be functional in 15+ years.
linux
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.