Kavita VS PDF.js

Browse the Issue Tracker: Visit our bug tracker @ https://github.com/Kareadita/Kavita/issues to find a list of open issues tagged specifically for the Bug Bash. You'll find a variety of tasks, from beginner-friendly to advanced.

#! /bin/bash installFolder="/opt/Kavita" # defines the folder where Kavita is installed backupFolder="/opt/KavitaBackup" # defines the backup folder for kavita kavitaUser="kavita" # defines the kavita service user kavitaGroup="kavita" # defines the kavita service group architecture="kavita-linux-x64.tar.gz" # options are: # kavita-linux-x64.tar.gz # kavita-linux-arm.tar.gz # kavita-linux-arm64.tar.gz if [ ! -d $installFolder ] then echo "KAVITA FOLDER IS MISSING!!" exit 1 fi cd /tmp if [ -r $architecture ] then echo "Kavita already present - extracting now!" tar -xzf $architecture else echo "Downloading latest Kavita from GitHub" wget https://github.com/Kareadita/Kavita/releases/latest/download/$architecture echo "extracting now!" tar -xzf $architecture fi if [ ! -d Kavita ] then echo "Something went wrong downloading or extracting" exit 1 fi echo "Stopping Kavita service" systemctl stop kavita.service if [ -d $backupFolder ] then echo "Deleting old KavitaBackup" rm -r $backupFolder fi echo "Creating new Kavita backup" cp -r $installFolder/config $backupFolder echo "Deleting Kavita" rm -r $installFolder echo "Installing new Kavita" cp -r /tmp/Kavita $installFolder echo "Deleting default config" rm -r $installFolder/config echo "Moving old config into install folder" cp -r $backupFolder $installFolder/config echo "CHOWN Kavita folder to kavita user and group" chown -R $kavitaUser:$kavitaGroup $installFolder echo "Make Kavita executable" chmod +x $installFolder/Kavita echo "Launch Kavita" systemctl start kavita.service echo "Cleaning up downloaded files" rm -r Kavita rm $architecture echo "Update process finished :)"

--2023-09-19 18:28:27-- https://github.com/Kareadita/Kavita/releases/download/v0.7.1.4/kavita-linux-arm64.tar.gz

Hey, Kavita creator here and noticed you don't have any mentions of Kavita for epub readers. Kavita is not a Calibre replacement, but has a built-in epub/pdf reader along with some series-based organization.

https://www.kavitareader.com/

The full release can be found here.

I first started building the app in the browser, using PDF.js and Download.js to take a PDF and edit it, and then download it to your computer.

pdf2json is a module that transforms PDF files from binary to JSON format, using pdf.js for its core functionality. It also incorporates support for interactive form elements, enhancing its utility in processing and interpreting PDF content.

Why not PDF.js?

I'd think opening a PDF in your browser would be at the same risk-level you associate with going to any random URL. On Firefox at least, I'm pretty sure the built-in PDF viewer is simply JS parsing and rendering the PDF anyway -- nothing with elevated permissions:

https://mozilla.github.io/pdf.js/

The PDF features are actually an extension, just one built in as Firefox's default pdf viewer.

It's called pdf.js https://github.com/mozilla/pdf.js/

You can actually use this pdf viewer in another browser like Chrome if you'd like, there's a demo URL on there.

We use Mozilla's PDF.js via the pdfjs-dist NPM module to load pages from a PDF file. The loadPdfPages function reads the PDF file and extracts its content. It returns an array where each object contains the page number and the text of that page.

The problem is that there simply wasn't a better option at the time.

Ogg Vorbis was a novelty at best, and it was the only decently widely adopted open source competitor for any of the items listed that was available at the time.

HTML5 was only just published when Chrome launched. So Flash was at that point the only option available to show a video in the browser (sure, downloading a RealPlayer file was always an option, but it was clunky, creators didn't like people being able to save stuff locally, and was also not open source). Chrome in fact arguably accelerated the process of getting web video open sourced: Google bought On2 in 2010 to get the rights to VP8 (the only decent H.264 competitor available at that point) so they could immediately open source it. The plan was in fact to remove H.264 from Chrome entirely once VP8/VP9 adoption ramped up[1], but that didn’t end up happening.

Flash was integrated into Chrome because people were going to use it anyway, and having Google distribute it at least let them both sandbox it and roll out automatic updates (a massive vector for malware at the time was ads pretending to be Flash updates, which worked because people were just that used to constant Flash security patches, most of which required a full reboot to apply; Chrome fixed both of those issues). Apple are the ones who ultimately dealt the death blow to Flash, and it was really just because Adobe could not optimize it for phone CPUs no matter what they tried (even the few Android releases of Flash that we got were practically unusable). That also further accelerated the adoption of open source HTML5 technologies.

PDF is an open source format, and has been since 2008. While I don't know if pressure from Google is what did it, that wouldn’t surprise me. Regardless, the Chrome PDF reader, PDFium, is open source[2] and Mozilla's equivalent project from 2011, PDF.js, is also open source.[3] Both of these projects replaced the distinctly closed source Adobe Reader plugin that was formerly mandatory for viewing PDFs in the browser.

Chrome is directly responsible for eliminating a lot of proprietary software from mainstream use and replacing it with high-quality open source tools. While they've caused problems in other areas of browser development that are worthy of criticism, Chrome's track record when it comes to open sourcing their tech has been very good.

[1]: https://blog.chromium.org/2011/01/html-video-codec-support-i...

[2]: https://github.com/chromium/pdfium

[3]: https://github.com/mozilla/pdf.js

Firefox Nightly is an unstable test version. You should report PDF issues to this GitHub repository.

Open this page and click on New Issue to ask the developers of the PDF viewer: mozilla/pdf.js repository. Please post a link to your question here.