The one trick is to make sure your file naming & organization is good. They have good documentation on it. Everything's pretty much automatic then, almost zero further work. The naming conventions aren't too bad, and the resulting file tree would be a reasonable way to organize your files regardless.
Yeah in my case it mostly just encouraged me to clean up some nonsense I’d been meaning to anyway.
I think some folks who have strong opinions about things like organizing their files under folders by director or something find it grating, but it did nothing but help my structure.
Agreed. I honestly chose Jellyfin over plex because I preferred the branding, not sure what I’m missing. I really enjoy Jellyfin, and thy seemingly have support for most devices in some way.
My GF has it set up on her iPad, phone, computer. App is on our TV and has no issues. We have Netflix at home. She’s non technical and hasn’t had any trouble once I gave her a login.
The only hiccup was when she tried to watch during one of her lectures. I had to explain that Jellyfin is only at home ;) (for now)
> The only hiccup was when she tried to watch during one of her lectures. I had to explain that Jellyfin is only at home ;) (for now)
Tailscale got me outside-the-home Jellyfin with a grand total of maybe 30 minutes of effort, including signing up, getting my server connected, and getting it on my MacBook, AppleTV, and phone. I'd never used it before.
I gave Jellyfin up and went back to upnp/dlna after the Android and iOS clients would keep losing sync, or wouldn't show me some season of a show, or would pick a white background on white text for a show.
The pain just kept adding up. It was quite nice most of the time. But every single time I reached for my phone, I was wondering how badly it was going to go. Quitting Jellyfin seemed like an excellent choice.
Upnp/dlna is much cruder; very direct raw BubbleUPnP client. But it works so well for me. Their transcoding server also is quite good and I can run it on any machine I want, isn't coupled to anything, can switch between them easily.
Bubbleupnp is also great because it lets me turn tablets into cast screens. I love that so much. Good general protocols rock; having media server, media renderer, then separate control points was a great model, good job UPnP.
Heh, I just spent 15 minutes debugging a Jellyfin bug where my WebOS client thought that the startup wizard had not been completed yet (I tried restarting it several times, but the thing that did the trick was enabling debug logging and _then_ it started working properly--probably a coincidence). Jellyfin is the best in class, but the bar is in hell. It can't be run in any kind of a high availability configuration, so if your only instance goes down or has any kind of issue, you have to jump on and fix it immediately or you can't use it. When something goes wrong, some of the logs show up in stderr, but most are just written as plain files to a directory. It's free software, so you get what you pay for, but it's pretty buggy.
My suggestions to new users are: Start small, just create notes for whatever you want to (actually) remember and create impromptu TODO lists. Ignore the whole Knowledge Database / second brain thing. Learn the obsidian keyboard shortcuts really well. You can build a structure in your notes later when you actually see what's good and what needs automation.
I think the main cause (that's actually quite anti-capitalist) is that banks and people at power have the ability to create money out of nothing, to lend the money into existence, while devaluing everyone else.
It was very interesting to me where I finally understood how banks (and the overall system) create money.
As a bank you start with 0 money, you lend 100 to some person that you "deposit" into their account at your bank. So now on your books you have 100 in liabilities (the money that the person has in your account) and 100 in assets (the money the person owes you). So accounting is balanced. You did not need money to start with, as a bank you just "lend it into existence".
The comparison here is to something like TCP/IP. TCP/IP never goes down. TCP/IP is a protocol, the servers may go down and cause disruption, but the protocol doesn't really have the ability to "go down".
Nostr is also a protocol. The communication on top of Nostr is pretty resilient compared to other solutions though, so that's the main highlight here.
If tens of servers go down, then some people may start noticing a bit of inconvenience. If hundreds of servers go down, then some people may need to coordinate out of bound on what relays to use, but it still generally speaking works ok.
That's because TCP/IP is a protocol, not a (centralized or decentralized) server. A protocol cannot go down. It can trigger failures, it can be abused, but it cannot go down.
It's like saying "English never burns". Sure, you can't burn English but you can burn specific books, newspapers and so on.
"Our AIs"?
The AI models belong to giant corporations (Google, Microsoft) or are receiving millions of dollars serving giant corporations. How are they yours?
A better solution is passing laws on wage transparency. For most jobs, the company has a range in mind. Make them post that range in the job offer itself. Short of robust labor unions bargaining for better wages, transparency in the job posting is the next best thing.
reply