Did they comment on why it was deleted? I didn’t see anything in the article. I recall the consensus was that they made so many mistakes the only way to fix it was deletion of the repo.

I also saw in one of the comments of the Arstechnica article that the one who pushed for open-source wanted to clean up the code before publishing. Management said no, the entire team got fired/left, and suddenly the code got published with all that commercial stuff left in. Sounds about right.

I figured OSalt would have been near the top of the recommendations. I didn’t realize how unpopular it was I guess. It’s a little more selective in it’s recommendations (and perhaps a tad dated).

You might also look at gallery-dl

Any of them compatible with Winamp plugins? Because that’s my reason for sticking to the past.

It’s been too many years since I’ve dabbled in code licensing so I’m a bit in the dark as to what this implies, but if this results in a Linux fork that’s capable of running Winamp plugins…

Two of the best call centers I’ve ever worked with would be Google Fiber and Intel. Both of which are probably terrible now.

(2015) Google Fiber actually had people who understood networking, understood my personal setup, and understood what tests I had already performed to diagnose that my issue with their equipment. No faffing about with a script, I gave them my test results and got an appointment for a replacement line in like, 15 minutes, and an immediate credit on the account.

(2009) Back when Intel made rock-solid vanilla motherboards I did a dumb and accidentally disabled legacy USB on my board, which meant that I couldn’t press F2/DEL to get back into BIOS. I called Intel, gave them the troubleshooting steps I already ran (including jumper BIOS reset), and the call center forwarded me to the engineer who designed the motherboard. He whipped up and sent a bootable CD-ROM image to update the BIOS back to default and then updated all future revisions to avoid my issue.

I wish every call center was that good.

I’ve noticed more and more are just hanging up on you now.

I just wish it had a better name. Anything You just makes my brain feel like it hiccup’d trying to reread the sentence parsing it a second time as a name.

What? I didn’t have to subscribe to anything. Are you not choosing Open-Meteo?

I guess I’ll keep this in the back of my mind, but I already migrated over to QuickWeather when Geometric Weather went unsupported. It stinks that I can’t swipe between locations anymore, but the built-in radar and higher information density outweigh switching back for me.

I don’t see any source on the article, and I don’t see anything in the changelog. All the image dates are still March 15th, so how is this change being pushed?

Yeah, it’s an install that’s getting long in the tooth. I’ve been hunting for a RPi4 for two years now, as USB3.0 would allow some basic LVM RAID5. I finally got one a week ago and have been waiting for RPiOS Bookworm to come out before making the painful transition… then RPi5 gets announced. Just my luck. haha

I guess that depends on how much storage you have to spare. In Jellyfin you can designate different formats by appending the label after the name, as long as both files are in the same parent directory. For example I’m subscribed to a movie maker on Patreon, and he allows his movies to be downloaded at their native resolution in an mp4 with h264 encoding. Not ideal for running on an old CRT with a Roku1 attached, haha. So I scale them and put the resolution as the label, then I use the drop-down inside the app to choose the appropriate version. It’s worth the storage penalty for me. Other stuff like GamesDoneQuick archives I downloaded are not multi-format since I don’t feel like keeping weeks worth of streaming media in redundant files. So those are left in webm with VP9.

├── Skull Forest (2012)

│   ├── folder.jpg

│   ├── Skull Forest (2012) - 480p.mp4

│   └── Skull Forest (2012) - 1080p.mp4

Yeah it’s weird that they don’t have plans for that price point. I mean, given inflation the starting price should be closer to $50 USD, so I’m guessing they’re going to continue production of RPi4 to keep that entry level low.

I use a Raspberry Pi 3B as a Jellyfin server, and people are correct… it’s not very suited to the task. Transcoding must be turned off in the settings as the the little Pi has no hardware decoding currently available, so I re-encode all my stuff to h264/aac before upload. Last I heard there were attempts to get some hardware decoding enabled, but I see very little progress. rpi-ffmpeg

I currently have 8 SSDs attached (which is probably too many), and I get about 12MBps throughput on USB 2.0. I have two powered USB hubs attached so that the SSDs don’t undervolt the RPi, which is really easy to do. As people already mentioned, part of my speed issue is the ethernet being on the same internal hub as the USB ports. I recall that WiFi is not tied like ethernet so you may increase throughput by connecting to your network via 802.11. These rules change when you get an RPi4 though.

The media itself takes some time to scan in, and if you’re booting from an SD card you’ll want to mount all jellyfin directories on dedicated LVs to avoid tearing up your SD card. Also doesn’t hurt to enable log2ram to reduce SD card wear, though you’ll need to modify your system journal to flush more frequently so you don’t fill it to 100% accidentally. log2ram

But yeah, after all that stuff it works more or less like I’d expect. The interface can take a second or two to load thumbnails, but I can watch 1080p content without buffering from inside the network… though content will always be exactly what you upload with no changes to resolution, encoding, or container. If you want different resolutions or encodings you have to upload multiple copies in the same folder (with specific naming) so they show up as options in the Jellyfin client. I even got some VLC installs to play the media by enabling DLNA.