That’s true, but the stickers weren’t much work so I figured I’d try them out.

paperless treats it as a single ASN number row and reports the highest used.

This is OK as long as you consistently use the QR codes to assign ASNs.

If your scanner supports scanning to a network share, install Samba on your Pi and share the paperless-ngx incoming directory. My ScanSnap iX1600 supports this, but I’m not familiar with other models. I had to configure the scanner using the Windows app to add the SMB details, but once it’s configured, it works without a computer attached.

Paperless-ngx also supports email. You can set up a separate email account for it, then forward it any documents you want to keep to it.

For documents you need to keep a physical copy of, use ASNs (archive serial numbers) to correlate the physical and virtual copy. You can use QR code stickers to automatically set the ASN in paperless-ngx. I posted a nested comment with more details about this.

Consider using paperless-ai to use an LLM to tag and title your scanned documents automatically. It needs a webhook to be configured. Consider a local model if possible, and if you want to use a hosted model, review the provider’s privacy policy to ensure they do NOT train the AI on user content.

And file away your scanned papers separately,

I’d recommend using ASN (archive serial numbers) for documents you store a physical copy of, following the recommended flow

I printed ASN QR code stickers, using the smallest Avery labels I could find (Avery 5267 in the USA, L4731REV-25 in Europe) along with their free online design app.

For documents I want to keep, I stick a QR code sticker on them before scanning. Paperless-ngx automatically detects the QR code and sets the ASN. I then file it away in a folder that’s sorted by ASN. When I need to find the physical copy again, I first look in Paperless to find the ASN, then find the document in the folder (pretty quick since all documents are sorted).

You’ll need to set the following settings:

PAPERLESS_CONSUMER_ENABLE_BARCODES=true
PAPERLESS_CONSUMER_ENABLE_ASN_BARCODE=true
PAPERLESS_CONSUMER_BARCODE_SCANNER=zxing

It’s also worth checking debrid services like Real Debrid, Premiumize, TorBox, AllDebrid, etc to see if they have the torrent cached, if you have an account at any of these services. Sometimes there’s torrents with 0 or 1 seeds that are still cached, especially if it’s a movie or TV show.

If it’s cached then you could just download it at full speed from the cache then use those files to seed.

I’ve been meaning to try this. It’s backed by Louis Rossman, so I’m sure it’s great.

These days I see so much AI slop that my reaction when I see code I hand-wrote myself is “hey, that’s pretty good”.

My team’s code is great, but we use a lot of shared code written by other teams, with varying levels of quality.

Do you know exactly which SoC it uses?

It’s probably a 32-bit ARM processor. Most NAS-focused operating systems have removed support for these, if they even supported them at all. OpenMediaVault recently removed support for 32-bit ARM and only support 64-bit now: https://www.openmediavault.org/?p=4002.

Having said that, some OSes still support them. You should be able to get Debian running if it’s an ARMv7 CPU or newer. Debian did support older ones, but they’re being phased out and no longer build an installer for them.

Open source projects are particularly vulnerable here since anybody can just grab the source and throw an LLM at it to see if it can find exploits.

On the other hand, this means that they should end up more secure. Open-source projects get far, far more vulnerability testing than closed-source projects. Security holes in closed-source systems can exist for years at a time, which is how things like the Pegasus malware work (undisclosed security holes).

This is how all language package managers work, unfortunately

npm does actually support signing and provenance (tracking how the package was built), so in some ways it can be more secure than other package managers. https://docs.npmjs.com/generating-provenance-statements

If you use one of the CI/CD systems they support (currently Github Actions and Gitlab CI), it can attach a signed attestation to the package stating the commit hash that was used to build the package, along with the steps taken to build it. This is combined with trusted packaging using OpenID Connect with short-lived tokens that are only obtainable in the correct CI environment, rather than using access tokens or username and password.

It only supports some CI systems because they have to guarantee that the connection between the CI system and npm is secure.

Some of the recent issues have been attacks on the CI system, rather than npm itself. For example, a Github Action that’s only supposed to run for commits to the main branch, but unintentionally runs for some subset of pull requests too.

Of course, all this stuff is optional, and pushing to npm directly from a developer’s computer still works and is still not verifiable at all.

I think the best approach is what Flathub/Flatpak, F-Droid (Android) and Composer/Packagist (PHP) do. You provide your repository URL, and they build the code on their end. Packages are always guaranteed to be built from code in the repo.

Debian Linux is also moving towards requiring repeatable builds, meaning that a package built from source should be byte-for-byte identical to the package in the repo.

What’s performance like? I found it to be very slow the last time I tried it.

in a world where chrome becomes the defacto browser

This is already the case.

Password protect it and just let friends use it? Or have it just for yourself :D

I just posted a comment about this :D

https://romm.app/

https://romm.app/ - Self hosted game ROM manager that lets you play retro games directly in the browser (using RetroArch cores compiled to WebAssembly).

https://retroassembly.com/ is a similar project.

There’s also https://gamevau.lt/ which is like a self-hosted version of Steam, for DRM-free games (like from GOG).

Game servers? https://linuxgsm.com/. Have an Unreal Tournament 99… tournament with friends.

Companies sometimes sell their own first-party data, but not nearly as often as people think. If a company has data that other companies don’t have, a lot of the time they’ll want to keep it for themselves, since it can give them a competitive advantage over other platforms.

If Amazon knows what movies and TV shows you like, they’re going to use that data to improve ad performance on their own platforms - suggested content on Prime Video, product ads on Amazon, etc. They’re not going to give it to some other company to use.

The one major exception to that are data brokers. These are companies that only exist to sell data. These are less well known companies. They often use public data and combine it with things like supermarket loyalty data and purchase history.

For a beginner, I’d probably stick to Github initially, just because there’s so many guides and tutorials on how to use it, and their free plan is still pretty generous.

A lot of the knowledge is transferable though. If you do want to try something else, Codeberg is pretty good for open-source.

To just learn about Git, you don’t even need a host like Github or Codeberg. You can have a Git repo just on your computer, and still get a bunch of the benefits of source control - a full history of everything, separate branches and worktrees so you can have multiple incomplete changes and switch between them, etc.

Or Forgejo, which is a fork of Gitea and is what Codeberg uses. They explain their advantages over Gitea here: https://forgejo.org/compare-to-gitea/

The tl;dr is that Forgejo is maintained by a non-profit whereas Gitea is maintained by a for-profit company, and Forgejo is completely open-source whereas Gitea is open-core with some features only available in their hosted service. Forgejo also has better testing and a bigger focus on security.

Maybe I’ll give that model a go if my current one ever dies.

I got an MX Master 3 as an upgrade, but couldn’t get used to the weird scrolling behaviour (similar to this: https://www.reddit.com/r/logitech/comments/wpp1c6/logitech_mx_master_3s_scrollwheel_is_still/), so ended up returning it and reverting to the $30 one.