Edit: Disregard my original reply, updated today and now it works again lol!

It launches for me (and I am in a plasma-wayland session FWIW), and it loads the thumbnails for all videos with no problem. When I click a video as if to play it, it appears to load up the main page for that video complete with play button, but nothing at all happens when I click the play button. Along the way are various api errors from youtube, but I think some of those came in even when things were working for me.

Basically I can get this far for any video:

Thank you! I actually tried setting the invidious options yesterday before making that post, thinking I might need to use that instead of localapi. But as you have predicted, no dice.

Edit - works fine after updating today lol!

Freetube on desktop Linux hasn’t worked for me for a long time - but that doesn’t seem to be the case for most people. Any tips regarding settings? I’d say it’s been at least 3 or 4 months since I could reliably use it.

I have servers on Digital Ocean and Linode and also one in my basement, and have had no problem. I do have all services behind NPM (not to suggest it’s a panacea) and use HTTPS/SSH for everything. (not to suggest HTTPS/SSH are either) My use case could be different than yours - my immediate family are my only consumers - but have been running the same services in those locations for a few years now without issue.

Just tried it - so simple, so good. Thanks for posting about this!

Anyone else remember when MS bought github and a LOT of folks were saying this is where we’d see that they have changed and won’t fuck things up this time because Nadella is so much cooler than Balmer? Pepperidge Farm remembers.

I spent just a few minutes with it and I like it a lot. I swear it’s more responsive than actual trello! :D

Feels like what happened to Emby to me.

(hugs Jellyfin)

[2024-03-23T09:29:01-0400] [ALPM] removed floorp-bin-debug (11.10.5-1)

[2024-03-23T09:29:01-0400] [ALPM] removed floorp-bin (11.11.1-1)

It’s a completely different way to manage and build an OS that no one else is really doing. I find team ‘I use arch btw’ to be extremely annoying but at the end of the day, the arch tooling for building a Linux ypunlike to use means that people are naturally going to want to tell you they built something they find enjoyable to use. That’s not really something a lot of people say about most OSs.

I wanted to try to find a way to say this in reply to some of the other comments, but I wasn’t sure I could communicate it effectively without just sounding like I was living up to the meme. You did a better job than I would have. :)

I have a roughly 13 year old install that I’ve moved through the transition to /usr/ and from sysv to systemd.

Whew! I’m aware of both those transitions, and was an arch user during one of them, but that’s super impressive. My oldest install is from 2020, endeavouros on a headless media server in my basement. Not even close!

No worries. For me, the the fun of installing wore off after a couple times, so I have stuck with derivatives in recent years, but I get it. :)

Preach. (Though I haven’t used pure Arch in a long time.)

Rolling distros have been all I’ve run for at least the past 6 or 7 years, and I essentially never do a fresh install anymore unless I get new hardware. It’s a lovely, low maintenance place to be, and I’ve always got fresh versions of all the software I use.

You might want to have a look at endeavouros if you consider coming back. It does a lot of the heavy lifting for you. I’ve got arch, manjaro, antergos in my background as far as arch-based distros I’ve tried over the years, and have not had major problems with any of them, but endeavouros is an easy install with some conservative defaults. I had only a couple things to add on afterward to get it just how I wanted, you have a fair bit of control at install time, and once installed it’s just like maintaining an arch system.

Any time! :)

If the script was supposed to wait 30 secs and then unblock the ports, running with nohup would have allowed the ports to be unblocked 30 secs later. Instead, the script terminated when the SSH session died, and never executed the countdown nor unblock.