Not a triad user in sight.

Just lemmings living in the moment.

While I’m sure there’s a pre-canned tool out there for you, if you have basic software experience (which you seem to), this is one of those times where it’s usually most efficient to hack together a dumb CGI script and call it a day.

This prompt should get you most of the way there, using your llm of choice:

Write a minimalist cgi script to help upload files to a server. Upon a GET request, serve a light page with a centered form that takes in a file and a submission code. Submission codes will be stored on individual lines of a plaintext file. Adding new codes to this file is out of scope - but the codes will be 8-char hex strings (do validate that submission strings are not empty!). The script should accept the submission as a POST, and save the file to an upload dir if the submission code is valid.

Vet the output, harden as needed, setup a systemd service to serve with busybox httpd, and optionally reverse-proxy. If you’ve done this sorta thing before, you can probably knock it out in a half hour.

I’m talking about the executable binary flatpak, which is the interface used to execute and manage applications distributed in the Flatpak bundle format.

https://docs.flatpak.org/en/latest/flatpak-command-reference.html#flatpak

Flatpak: a system for building, distributing, and running sandboxed desktop applications on Linux.

Flatpak application: an application installed via the flatpak command or through a graphical interface, such as GNOME Software or KDE Discover.

Runtime: also called platform, an integrated environment providing basic utilities needed for a Flatpak application to work.

Flatpak bundle: a single-file export format containing a Flatpak application or runtime.

From https://docs.flatpak.org/en/latest/introduction.html#terminology

You might be thinking of AppImages, which are more of a pure file format.

Ah - I totally missed the Nvidia-related bit! Thanks for flagging that.

That being said, based on the maintainers’ past stances, I’m pretty pessimistic on them actually implementing a fix like that. They’re very much against the general practice of poking holes in their sandbox security perimeter.

Flatpak is quite fucking far from perfect, and will always remain so due to its flawed design and UX approach.

Pretty sure the culprit here is Fedora’s packaging which adds an opaque systemd timer to run auto-updates, but the thread immediately next to this one on my homepage just happened to be a nice case-study in Flatpak fuckery: https://lemmy.world/post/30654407

Of course, the proposed changes in the article do nothing to fix this sorta problem, which happens to be the variety that end users actually care about. Flatpak is an epic noob trap since it pretends to be a plug-n-play beginner friendly tool, but causes all sorts of subtle headaches that newcomers inevitably don’t have diagnostic experience to address.

This is @Shimitar@downonthestreet.eu‘s work, not mine - but it’s pretty similar to how I’d set things up:

https://wiki.gardiol.org/doku.php?id=networking%3Assh_tunnel

This is a great suggestion!

Lest anyone miss the buried lede, this approach means that traffic is pre-encrypted as it passes through the gateway VPS - so even if your VPS gets hacked, it’s way harder to steal credentials and break into the services running on your home network.

If you’re looking for sympathy, you got it. Fuck the state.

If you’re looking for solutions, use a cheap $5/mo VPS that exists purely as your gateway host. Run everything you want on your home machines, then tunnel the traffic to your gateway and reverse-proxy it there. Your data stays in your hands, you can spin up and expose new services publicly in a matter of minutes, AND your home IP isn’t vulnerable to doxxing or DoS.

Speaking as a data engineer, you’re having trouble because git is the wrong tool for the job. You can make it work if you use git-lfs + custom hooks — but if you choose to go that route, be aware you’re making things unnecessarily hard for yourself.

If you want to make this easy, separate out your concerns:

1. Versioning: take periodic snapshots of your unconverted files with a binary-friendly diffing tool like restic or borg. Alternatively, ZFS/btrfs snapshots are an excellent way to handle this.
2. Conversion: keep your original files in their own directory. Set up a small script that searches your directory of original files recursively, passes the files to lame to encode to V0 or V2, and outputs them to a separate directory of lossy mp3 files.
3. Syncing: use rsync with the --delete flag to copy your lossy files to the server + clear out files you’ve removed locally.

Object storage is indeed a specialized filesystem in a trenchcoat.

Object storage is typically (but not always) associated with non-hierarchical key-value lookups, as opposed to the directory tree pattern most file systems use. Object storage systems are also typically (but not always) designed with sharding and distribution in mind.

This is a Jellyfin problem; not a beets problem. You can easily solve it with beets config if you’d like to, though.

The distinction between what you want vs. what you’re getting is that Jellyfin is grouping by the “Artist” tag instead of the “Album Artist” tag. I haven’t touched Jellyfin in years, but look for a builtin setting or alternative view to group by album artist - you’ll almost certainly find it.

If you want to solve it in beets, you can do that through a custom script, the FtInTitle plugin, or a combo of the inline + advancedrewrite plugins. Remember to run a re-import on the Jellyfin side after making your tweaks to the beets pipeline to make your changes show up without duplication.

You are not hosting csam on purpose. And most likely try to moderate as good as possible.

Look up what “strict liability” means in a criminal law context.

This is brilliant! You can even let the front truck pull all the others tied behind it so you need fewer working engines.

What if you added guide rails to the lane so the trucks didn’t have to steer?

There is a massive functional difference to anyone with two braincells to rub together.

The core devs can (and should) step in front of a bus (or tank) tomorrow; the core project will just fork, and LW and the other non-triad instances will do fine without them. I’ve had no issue on Lemmy blocking .ml client-side.

The only reminder of the triad’s existence is infiltrator trolls who make alts on other instances to post bad-faith arguments glazing the core devs.

You misunderstood the pinned post; it’s soliciting donations for core Lemmy development, not for the .world instance.

The core devs use donations to the project to fund their tankie .ml instance, which is why they’re getting pushback. There is zero comparable pushback among the community towards funding .world or other instances.

If you’d like to give away any free toasters with hackable embedded microcontrollers to prove your point here, I’m a willing recipient and will attempt setup of a searx instance.

You didn’t start by asking a question. You needlessly trashed a helpful suggestion from a place of ignorance, then asked a naive question defensively to mask a lack of knowledge.

That is rude and trollish behavior.

Since it seems like you don’t know much about bash at all, I promise the book will help you.

You can be someone who actually knows what they’re talking about instead of making embarrassing, snarky comments that expose your lack of education on the topic at hand.

Bash has had some nice minor features and syntax sugar added, but the fundamentals are entirely the same. All the examples in the book work just the same today as they did when it was written.

What was added in 4.X or 5.x that you can’t live without? What do you think has changed that merits inclusion?