BookOrbit is doing pretty well for me so far with comics. Seems to have manga options about reverse reading direction.
Even better for books too. Can do koreader opds and email books as well. (I have a kobo so I havenât tried the kindle-orientated email, but I assume itâs ez pz)
Very good metadata ingestion. And the book/comic libraries arenât in different siloâd worlds like they are with Calibre and its derivatives.
Iâm pretty pleased so far, have found some niggles but nothing bad. And the good stuff plenty outweighs anything else. Itâs all ready to go, I switched libraries quickly. And it ate up my old library with its different (not as good) naming style and realigned it automatically, which was nice.
I have seent that in my searches [ https://github.com/naleo/audiobookshelf.koplugin ], but I decided to go for something that has it natively since sometimes the plugins get björked by updates (from my experience with gnome and its plugins)
But I will say, Audiobookshelf is superior for its purpose: audiobooks and podcasts. If I wanted that first Iâd slap the plugin on to be happy with books/comics and kobos, but I wanted book/comics first so I chose a diff path - abs ainât bad!
Iâve got BookOrbit and Audiobookshelf both going. They both can be hosted securely (locked down compose file with read-only, non-root user, etc.) and use Postgres as their DBs, both key features.
I added in BookOrbit to try since it has kobo sync and koreader sync that Audiobookshelf lacks.
I moved books from Audiobookshelf to get BookOrbit going and there was a learning curve to get the UI to do it optimally for me, but I eventually got it to work for me. BookOrbit has the ability to write metadata to the files themselves, which most things lack. Very nice for portability.
Thereâs a folder BookOrbit imports from and you can set it to populate metadata automatically - seems strongly built for an automated library system.
Both have been very stable. Iâd say BookOrbit is the better one - and it supports audiobooks too. Audiobookshelf handles multiple libraries (like books and comics) in a clunky way (have to switch between them like theyâre completely different siloâd libraries - much like how Calibre handles them). BookOrbit has them separated but easy to see they exist and you can mix and match them in a collection or something. Better way to handle it.
I use the desktop application Calibre to convert books as needed, but BookOrbit will automatically generate kobo epubs from epubs when syncing so I need not worry about kepub prep.
Lastly, I chose BookOrbit to try over others because Grimmory needs a ton of RAM, Kavita had features behind a paywall, some other one is comic-focused, and the Calibre web iterations give off the vibe of a lot of tapes the inside to make them work; I had big doubts Calibre Web Auto would be able to be run non-root and read-only. Chose Audiobookshelf originally because of the Calibre mess and other options didnât exist or were much less established.
Edit: lore drop: BookOrbit is a feature copy of Booklore but written not in Java (I think JS), and Grimmory is a community fork of Booklore after its creator fell into AI psychosis.
So extra background, I was put off by proxmoxâs weird steps to get ISOâs onto the system via USB so I was like âI am not touching the backup stuffâ and just rolled my own (I treat the VMs/containers on my proxmox server like individual servers and back them up accordingly and do not back up the underlying proxmox instance itself).
I see proxmox has a similar pruning setting to Restic, and it exports the files like incus. So Iâd say yes, proxmox is one-stop-shop for backup while with incus you have to put its container export options and restic together and put that in a cron job.
Still hard to say what Iâd definitively tell a newbie to go with. I found (and still find) the proxmox ui daunting and difficult while the incus UI makes much more sense to me and is easier (has an ISO pulling system built in for instance. But as youâve pointed out - proxmox gives you an easy way to have robust backups that takes much more effort on the incus side.
As backups are paramount, proxmox for a total newbie. If someone is familiar with scripting, then incus - because it needs scripted backups to be as robust as proxmoxâ backups. @barnaclebill@lemmy.dbzer0.com this conclusion should help you choose proxmox (most likely)!
A bit down from the snapshots section is the export section, what I do is I export to a place then back it up with Restic. I do not compress on export and instead do it myself with the ârsyncable flag added to zstd. (Flag applies to gzip too) With the rsyncable flag incremental backups work on the zip file so itâs space efficient despite being compressed. I donât worry about collating individual zip files, instead I rely on Resticâs built-in versioning to get a specific version of the VM/container if I needed it.
Also a few of my containers I linked the real file system (big ole data drive) into the container and just snapshot the big ole data drive/send said snapshot using the BTRFS/ZFS methods cause that seemed easier, those containers are easy enough to stand up on a whim and then just need said data hooked up.
I also restic the sent snapshot since snapshots are write-static and restic can read from it at its leisure. Restic is the final backup orchestrator for all of my data. One restic call == one ârestic snapshotâ so I call it monolithically with one call covering several data sources.
This describes the jist, itâs all about snapshots! Incus loves BTRFS/ZFS.
Thereâs no true need for stop everything as far as I can tell.
Stop everything is applicable for databases for any backup system (snapshot avoids backing up a database mid write (guaranteed failure) but the snapshot could be during a live database multi-step operation and while intact is left in a cursed state). For databases I make sure to stop and backup (SQLite losers) or backup live (Godsâ chosen Postgres) specially so no very niche database failures occur even though it was done with instant/write-safe snapshots!!
Recovery plan is restore snapshot and if 0.1% chance of database bad bc was mid big multiple step operation then I have the .gz to restore from.
There is a larger community. I have proxmox and incus on two devices and for the basics (LXC container/VM) Incus is way more straight forward. Ditchin proxmox next reinstall on the other device (that proxmox install is the OS version). If youâre doing regular stuff itâs easy enough even with the reduced community! Theyâve covered the basics well.
But again, proxmox community is larger. I started with it for that reason too.
Since youâre not using proxmox as an OS install, why not check out Incus? It accomplishes the same goals as proxmox but is easier to use (for me at least). Make sure you install incusâ web ui, makes it ez pz. Incus does the VMs and containers just like proxmox but isnât focused on clustering 1st but rather machine 1st. It does do clustering, but the default UI is set for your machine to start so it makes more sense to me. The forums are very useful and questions get answered quickly, and thereâs an Ubuntu-only fork called LXD which expands the available pool of answers. (For now, almost all commands are the same between Incus and LXD). I run the incus stable release from the Zabbly package repo, I think the long term release doesnât have the web ui yet (I could be wrong). Never have had a problem. When Debian 13 hits Iâll switch to whatever is included there and should be set.
I use incus for VMs and LXC containers. I also have Docker on the Debian system. Many types of containers for every purpose!
I installed incus on a Debian system that I encrypted with LUKS. It unlocks after reboots with a USB drive, basically I use it like a yubikey but you could leave it in so the system always reboots no problem. Thereâs also a network unlock too but I didnât try to figure that out. Without USB drive or network, youâll have to enter the encryption key on every reboot.
Have your friend try inflammation-reducing drugs like metformin. Metformin specifically, maybe thereâs others, Iâm sadly not a doctor. Metformin is a magic drug thatâs not just for diabetius.
It wonât be immediate, but maybe it could help your friend recover. Idk if cranking yourself will break through when itâs a blocking mechanism causing the problem.
Indeed I did not, weâre at a stalemate because you and I do not believe what the other is saying! So we canât move anywhere since itâs two walls. Buuuut Tim Apple got my back for once, just saw this now!: https://lemmy.blahaj.zone/post/27197259
Iâll leave it at that, as thanks to that white paper I win! Yay internet points!
Itâs wild, weâre just completely talking past each other at this point! I donât think Iâve ever gotten to a point where Iâm like âitâs blueâ and someoneâs like âitâs goldâ so clearly. And like I know enough to know what Iâm talking about and that Iâm not wrong (unis are not getting tons of grants to see âif AI can thinkâ, no one but fart sniffing AI bros would fund that (see OPâs requested source is from an AI company about their own model), research funding goes towards making useful things not if ChatGPT is really going through it like the rest of us), but you are very confident in yourself as well. Your mention of information theory leads me to believe youâve got a degree in the computer science field. The basis of machine learning is not in computer science but in stats (math). So I wonât change my understanding based on your claims since I donât think you deeply know the basis just the application. The focus on using the âright wordsâ as a gotchya bolsters that vibe. I know you wonât change your thoughts based on my input, so weâre at the age-old internet stalemate! Anyway, just wanted you to know why I decided not to entertain what youâve been saying - Iâm sure Iâm in the same boat from your perspective ;)
You can, but the stuff thatâs really useful (very competent code completion) needs gigantic context lengths that even rich peeps with $2k GPUs canât do. And thatâs ignoring the training power and hardware costs to get the models.
Techbros chasing VC funding are pushing LLMs to the physical limit of what humanity can provide power and hardware-wise. Way less hype and letting them come to market organically in 5/10 years would give the LLMs a lot more power efficiency at the current context and depth limits. But that ainât this timeline, we just got VC money looking to buy nuclear plants and fascists trying to subdue the US for the techbro oligarchs womp womp
No, theyâre right. The âresearchâ is biased by the company that sells the product and wants to hype it. Many layers donât make think or reason, but theyâre glad to put them in quotes that they hope peeps will forget were there.
So close, LLMs work via matrix multiplication, which is well understood by many meat bags and matrix math canât think. If a meat bag canât do matrix math, thatâs ok, because the meat bag doesnât work via matrix multiplication. lol imagine forgetting how to do matrix multiplication and disappearing into a singularity or something
I was channeling the Interstellar docking computer (âimproper contactâ in such a sassy voice) ;)
There is a distinction between data and an action you perform on data (matrix maths, codec algorithm, etc.). Itâs literally completely different.
An audio codec (not a pipeline) is just actually doing math - just like the workings of an LLM. Thereâs plenty of work to be done after the audio codec decodes the m4a to get to tunes in your ears. Same for an LLM, sandwiching those matrix multiplications that make the magic happen are layers that crunch the prompts and assemble the tokens you see it spit out.
LLMs canât think, thatâs just the fact of how they work. The problem is that AI companies are happy to describe them in terms that make you think they can think to sell their product! I literally cannot be wrong that LLMs cannot think or reason, thereâs no room for debate, itâs settled long ago. AI companies will string the LLMs together and let them chew for a while to try make themselves catch when theyâre dropping bullshit. Itâs still not thinking and reasoning though. They can be useful tools, but LLMs are just tools not sentient or verging on sentient
Improper comparison; an audio file isnât the basic action on data, it is the data; the audio codec is the basic action on the data
âAn LLM model isnât really an LLM because itâs just a series of numbersâ
But the action of turning the series of numbers into something of value (audio codec for an audio file, matrix math for an LLM) are actions that can be analyzed
And clearly matrix multiplication cannot reason any better than an audio codec algorithm. Itâs matrix math, itâs cool we love matrix math. Really big matrix math is really cool and makes real sounding stuff. But itâs just matrix math, thatâs how we know it canât think
Itâs literally tokens. Doesnât matter if it completes the next word or next phrase, still completing the next most likely token đđ canât think canât reason can witchâs brew facsimile of something done before
Indeed that was me in the other thread on book managers, so to be fair people arenât raving about it - only I am haha!
BookOrbit is doing pretty well for me so far with comics. Seems to have manga options about reverse reading direction.
Even better for books too. Can do koreader opds and email books as well. (I have a kobo so I havenât tried the kindle-orientated email, but I assume itâs ez pz)
Very good metadata ingestion. And the book/comic libraries arenât in different siloâd worlds like they are with Calibre and its derivatives.
Iâm pretty pleased so far, have found some niggles but nothing bad. And the good stuff plenty outweighs anything else. Itâs all ready to go, I switched libraries quickly. And it ate up my old library with its different (not as good) naming style and realigned it automatically, which was nice.
I have seent that in my searches [ https://github.com/naleo/audiobookshelf.koplugin ], but I decided to go for something that has it natively since sometimes the plugins get björked by updates (from my experience with gnome and its plugins)
But I will say, Audiobookshelf is superior for its purpose: audiobooks and podcasts. If I wanted that first Iâd slap the plugin on to be happy with books/comics and kobos, but I wanted book/comics first so I chose a diff path - abs ainât bad!
Iâve got BookOrbit and Audiobookshelf both going. They both can be hosted securely (locked down compose file with read-only, non-root user, etc.) and use Postgres as their DBs, both key features.
I added in BookOrbit to try since it has kobo sync and koreader sync that Audiobookshelf lacks.
I moved books from Audiobookshelf to get BookOrbit going and there was a learning curve to get the UI to do it optimally for me, but I eventually got it to work for me. BookOrbit has the ability to write metadata to the files themselves, which most things lack. Very nice for portability.
Thereâs a folder BookOrbit imports from and you can set it to populate metadata automatically - seems strongly built for an automated library system.
Both have been very stable. Iâd say BookOrbit is the better one - and it supports audiobooks too. Audiobookshelf handles multiple libraries (like books and comics) in a clunky way (have to switch between them like theyâre completely different siloâd libraries - much like how Calibre handles them). BookOrbit has them separated but easy to see they exist and you can mix and match them in a collection or something. Better way to handle it.
I use the desktop application Calibre to convert books as needed, but BookOrbit will automatically generate kobo epubs from epubs when syncing so I need not worry about kepub prep.
Lastly, I chose BookOrbit to try over others because Grimmory needs a ton of RAM, Kavita had features behind a paywall, some other one is comic-focused, and the Calibre web iterations give off the vibe of a lot of tapes the inside to make them work; I had big doubts Calibre Web Auto would be able to be run non-root and read-only. Chose Audiobookshelf originally because of the Calibre mess and other options didnât exist or were much less established.
Edit: lore drop: BookOrbit is a feature copy of Booklore but written not in Java (I think JS), and Grimmory is a community fork of Booklore after its creator fell into AI psychosis.
So extra background, I was put off by proxmoxâs weird steps to get ISOâs onto the system via USB so I was like âI am not touching the backup stuffâ and just rolled my own (I treat the VMs/containers on my proxmox server like individual servers and back them up accordingly and do not back up the underlying proxmox instance itself).
I see proxmox has a similar pruning setting to Restic, and it exports the files like incus. So Iâd say yes, proxmox is one-stop-shop for backup while with incus you have to put its container export options and restic together and put that in a cron job.
Still hard to say what Iâd definitively tell a newbie to go with. I found (and still find) the proxmox ui daunting and difficult while the incus UI makes much more sense to me and is easier (has an ISO pulling system built in for instance. But as youâve pointed out - proxmox gives you an easy way to have robust backups that takes much more effort on the incus side.
As backups are paramount, proxmox for a total newbie. If someone is familiar with scripting, then incus - because it needs scripted backups to be as robust as proxmoxâ backups. @barnaclebill@lemmy.dbzer0.com this conclusion should help you choose proxmox (most likely)!
https://linuxcontainers.org/incus/docs/main/howto/instances_backup/#instances-backup-export
A bit down from the snapshots section is the export section, what I do is I export to a place then back it up with Restic. I do not compress on export and instead do it myself with the ârsyncable flag added to zstd. (Flag applies to gzip too) With the rsyncable flag incremental backups work on the zip file so itâs space efficient despite being compressed. I donât worry about collating individual zip files, instead I rely on Resticâs built-in versioning to get a specific version of the VM/container if I needed it.
Also a few of my containers I linked the real file system (big ole data drive) into the container and just snapshot the big ole data drive/send said snapshot using the BTRFS/ZFS methods cause that seemed easier, those containers are easy enough to stand up on a whim and then just need said data hooked up.
I also restic the sent snapshot since snapshots are write-static and restic can read from it at its leisure. Restic is the final backup orchestrator for all of my data. One restic call == one ârestic snapshotâ so I call it monolithically with one call covering several data sources.
Hope that helps!
https://linuxcontainers.org/incus/docs/main/howto/instances_backup/#instances-snapshots
This describes the jist, itâs all about snapshots! Incus loves BTRFS/ZFS.
Thereâs no true need for stop everything as far as I can tell.
Stop everything is applicable for databases for any backup system (snapshot avoids backing up a database mid write (guaranteed failure) but the snapshot could be during a live database multi-step operation and while intact is left in a cursed state). For databases I make sure to stop and backup (SQLite losers) or backup live (Godsâ chosen Postgres) specially so no very niche database failures occur even though it was done with instant/write-safe snapshots!!
Recovery plan is restore snapshot and if 0.1% chance of database bad bc was mid big multiple step operation then I have the .gz to restore from.
There is a larger community. I have proxmox and incus on two devices and for the basics (LXC container/VM) Incus is way more straight forward. Ditchin proxmox next reinstall on the other device (that proxmox install is the OS version). If youâre doing regular stuff itâs easy enough even with the reduced community! Theyâve covered the basics well.
But again, proxmox community is larger. I started with it for that reason too.
Since youâre not using proxmox as an OS install, why not check out Incus? It accomplishes the same goals as proxmox but is easier to use (for me at least). Make sure you install incusâ web ui, makes it ez pz. Incus does the VMs and containers just like proxmox but isnât focused on clustering 1st but rather machine 1st. It does do clustering, but the default UI is set for your machine to start so it makes more sense to me. The forums are very useful and questions get answered quickly, and thereâs an Ubuntu-only fork called LXD which expands the available pool of answers. (For now, almost all commands are the same between Incus and LXD). I run the incus stable release from the Zabbly package repo, I think the long term release doesnât have the web ui yet (I could be wrong). Never have had a problem. When Debian 13 hits Iâll switch to whatever is included there and should be set.
https://linuxcontainers.org/incus/docs/main/installing/#installing-from-package
I use incus for VMs and LXC containers. I also have Docker on the Debian system. Many types of containers for every purpose!
I installed incus on a Debian system that I encrypted with LUKS. It unlocks after reboots with a USB drive, basically I use it like a yubikey but you could leave it in so the system always reboots no problem. Thereâs also a network unlock too but I didnât try to figure that out. Without USB drive or network, youâll have to enter the encryption key on every reboot.
Now this is feral hacking hell yeah
Not a doctor, but based on research Iâve seent brain fog (in likely many cases) seems to be due to inflammation. https://www.autoimmuneinstitute.org/covid_timeline/brain-fog-likely-caused-by-brain-inflammation-its-not-just-all-in-their-head/
Have your friend try inflammation-reducing drugs like metformin. Metformin specifically, maybe thereâs others, Iâm sadly not a doctor. Metformin is a magic drug thatâs not just for diabetius.
It wonât be immediate, but maybe it could help your friend recover. Idk if cranking yourself will break through when itâs a blocking mechanism causing the problem.
Indeed I did not, weâre at a stalemate because you and I do not believe what the other is saying! So we canât move anywhere since itâs two walls. Buuuut Tim Apple got my back for once, just saw this now!: https://lemmy.blahaj.zone/post/27197259
Iâll leave it at that, as thanks to that white paper I win! Yay internet points!
Itâs wild, weâre just completely talking past each other at this point! I donât think Iâve ever gotten to a point where Iâm like âitâs blueâ and someoneâs like âitâs goldâ so clearly. And like I know enough to know what Iâm talking about and that Iâm not wrong (unis are not getting tons of grants to see âif AI can thinkâ, no one but fart sniffing AI bros would fund that (see OPâs requested source is from an AI company about their own model), research funding goes towards making useful things not if ChatGPT is really going through it like the rest of us), but you are very confident in yourself as well. Your mention of information theory leads me to believe youâve got a degree in the computer science field. The basis of machine learning is not in computer science but in stats (math). So I wonât change my understanding based on your claims since I donât think you deeply know the basis just the application. The focus on using the âright wordsâ as a gotchya bolsters that vibe. I know you wonât change your thoughts based on my input, so weâre at the age-old internet stalemate! Anyway, just wanted you to know why I decided not to entertain what youâve been saying - Iâm sure Iâm in the same boat from your perspective ;)
You can, but the stuff thatâs really useful (very competent code completion) needs gigantic context lengths that even rich peeps with $2k GPUs canât do. And thatâs ignoring the training power and hardware costs to get the models.
Techbros chasing VC funding are pushing LLMs to the physical limit of what humanity can provide power and hardware-wise. Way less hype and letting them come to market organically in 5/10 years would give the LLMs a lot more power efficiency at the current context and depth limits. But that ainât this timeline, we just got VC money looking to buy nuclear plants and fascists trying to subdue the US for the techbro oligarchs womp womp
No, theyâre right. The âresearchâ is biased by the company that sells the product and wants to hype it. Many layers donât make think or reason, but theyâre glad to put them in quotes that they hope peeps will forget were there.
So close, LLMs work via matrix multiplication, which is well understood by many meat bags and matrix math canât think. If a meat bag canât do matrix math, thatâs ok, because the meat bag doesnât work via matrix multiplication. lol imagine forgetting how to do matrix multiplication and disappearing into a singularity or something
They do not, and I, a simple skin-bag of chemicals (mostly water tho) do say
I was channeling the Interstellar docking computer (âimproper contactâ in such a sassy voice) ;)
There is a distinction between data and an action you perform on data (matrix maths, codec algorithm, etc.). Itâs literally completely different.
An audio codec (not a pipeline) is just actually doing math - just like the workings of an LLM. Thereâs plenty of work to be done after the audio codec decodes the m4a to get to tunes in your ears. Same for an LLM, sandwiching those matrix multiplications that make the magic happen are layers that crunch the prompts and assemble the tokens you see it spit out.
LLMs canât think, thatâs just the fact of how they work. The problem is that AI companies are happy to describe them in terms that make you think they can think to sell their product! I literally cannot be wrong that LLMs cannot think or reason, thereâs no room for debate, itâs settled long ago. AI companies will string the LLMs together and let them chew for a while to try make themselves catch when theyâre dropping bullshit. Itâs still not thinking and reasoning though. They can be useful tools, but LLMs are just tools not sentient or verging on sentient
Improper comparison; an audio file isnât the basic action on data, it is the data; the audio codec is the basic action on the data
âAn LLM model isnât really an LLM because itâs just a series of numbersâ
But the action of turning the series of numbers into something of value (audio codec for an audio file, matrix math for an LLM) are actions that can be analyzed
And clearly matrix multiplication cannot reason any better than an audio codec algorithm. Itâs matrix math, itâs cool we love matrix math. Really big matrix math is really cool and makes real sounding stuff. But itâs just matrix math, thatâs how we know it canât think
Itâs literally tokens. Doesnât matter if it completes the next word or next phrase, still completing the next most likely token đđ canât think canât reason can witchâs brew facsimile of something done before