Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)D
Posts
2
Comments
165
Joined
1 yr. ago

  • Yt-dlp is the gold standard for that.

    https://github.com/yt-dlp/yt-dlp

    Tag cleanup and album art are their own beast that you’ll wanna tackle post-download, but beets is another gold standard tool that can help with that layer.

    https://beets.io/

  • Gnome. The maintainers have a hard-earned rep for contemptuous attitudes towards community and end-user feedback.

  • You shouldn’t suggest UFW at all then. There are other firewall options that can be used just fine with docker.

    It does have real potential to cause issues, e.g. if OP were to put their server in DMZ mode on their router and later copy some docker setup instructions that don’t explicitly bind to localhost.

  • This is dangerous advice because docker is well-known for undoing UFW’s iptable rules. It’s mitigated by binding to localhost, but still way too easy for people to shoot themselves in the foot by using the two together.

  • No need to cargo-cult security practices here, chief. You’re not gonna get pwned by publishing your hardware specs. If you’re planning to build some kinda webapp for yourself, that’s a different story - but you have to fuck up hard to get hacked while hosting raw HTML.

    Use an SSH key, disable password auth, make sure you’re firewalled (i.e. test with nmap), and call it a day.

  • Is there a buried lede here? What’s noteworthy about an RC of a minor version release?

  • I appreciate systemd at a high level, and use it all the time, but Nanook’s comment in this thread is dead on the money in my book:

    https://lemmy.world/post/30945123/17510444

    The CLI interfaces for PA and SysD are janky/verbose af and make it hard for beginners to do simple things as well. E.g. try wiring up a virtual device with pacmd that fuses your desktop audio and mic output into a combined source using only the man pages, or putting together a fresh service from memory without looking up any directives.

    E: even better example, compare how easy it is to set something up to run in cron vs. a systemd timer.

  • Sorry, bad phrasing on my end. I agree the community should suspicious, but I think the flawed premise in

    It seems like there isn’t much criticism of the company or their tactics, and I’m curious if any of you think that should change.

    is that there is consistent, well-founded criticism and has been this whole time. And even though the vocal folks are a minority, a lot of people feel ambivalent about the relationship rather than viewing it favorably.

  • I do think there are quite a few linux users and developers who are suspicious of Red Hat, they are a small-ish but pretty vocal minority.

    Yeah, I’m with you all the way — no shade to OP, but the question has a flawed premise. I think the majority opinion is that they’re both an asset and a liability. They’re a huge contributor to the ecosystem and have done a lot of practical good, but I also think the community will turn on a dime if the suits overstep into FAFO territory.

    (All that said, fuck Lennart Poettering. Dude couldn’t design a plan to get himself out of a paper bag.)

  • I expect Feynman’s answer, if he had a whiteboard and unlimited time, would’ve been to dive into Maxwell’s equations.

    With that in mind, his answer makes complete sense. Good luck explaining coupled PDEs to people who aren’t mathy in a few sentences without visual aid. The analogy to the gravitational force isn’t on point; there’s a lot more to be said about how magnets tie to into E&M more broadly, compared to gravity.

    Though you’re absolutely right that once you get deep enough into any topic in physics that the answer to “why?” inevitably becomes “it just be like that”.

  • 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.

  • 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 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.