

Audiobookshelf actually has a pretty good ebook implementation.
It’s not it’s primary focus, but if you have it for audiobooks already, it’s a no-brianer.
Linux enthusiast, family man and nerd
Audiobookshelf actually has a pretty good ebook implementation.
It’s not it’s primary focus, but if you have it for audiobooks already, it’s a no-brianer.
Roku app might have issues with self-signed certificates.
Yeah. I’ve sold a thing or two using it.
There is an instance of this in Denmark, that I have used a couple of times already. It is a nice alternative.
Hope they implement “range” soon, so you can tell how far away an item is.
It should support NVENC according to TechPowerUp. I have only ever used raspberry pi and intel hardware for jellyfin, so I don’t know how well nvidia does when going down in specs.
Yes, but it’s always the one people come back too.
They mention the other issues are either being tracked elsewhere or already solved.
At the end of the day, it’s a community project, done by primarily volunteers, who is not making any money doing this. No VC funding to hire developers to take care of these issues.
From one of the Jellyfin devs in the issue you linked, posted in April this year:
Now, let’s address this clearly once and for all. What is possible is unauthenticated streaming. Each item in a Jellyfin library has a UUID generated which is based on a checksum of the file path. So, theoretically, if someone knows your exact media paths, they could calculate the item IDs, and then use that ItemID to initiate an unauthenticated stream of the media. As far as we know this has never actually been seen in the wild. This does not affect anything else - all other configuration/management endpoints are behind user authentication. Is this suboptimal? Yes. Is this a massive red-flag security risk that actively exposes your data to the Internet? No.
At this point, this over-4-year-old issue has gotten posted to HackerNews more than enough times and gotten quite enough unhelpful peanut-gallery comments like those above… We are limiting this issue to Jellyfin collaborators only at this point. Most of the big items are already tracked elsewhere (specifically, unauth playback) or have already been fixed. And many other options are now open to us in a post-10.11 landscape now that we have a proper library database ready.
Plex recently switched the remote watch thing to be behind a paywall. If your PC/App was also on the same local network it would probably work.
Probably the easiest way. It’s plugged into a smart plug with energi monitoring.
I went: Pi 2 -> Pi 4 -> Odroid H3 -> Intel N100 box (current). All in all from about 4W idle on the pi to about 10W idle on the N100 box. So not a big power jump all in all, but my needs did get bigger since the Pi.
People don’t care and/or haven’t looked at the serverinfo page. That actually mentions the type of database in use.
So the “I don’t know” option was probably just the easiest.
No Linux client? 😞
I thought downloading and redistributing tiktok videos was against TikToks TOS?
Maybe Linkwarden can do it.
I’m not. So in theory they shouldn’t even contact me, just block me.
Yep, if they do contact me about my open relay, it’s just going down. :)
Sure, if I was great at coding I could take a stab at it, but I am not.
What if I am just running a relay outside the UK as a service to support the notr network. If this law requires the small relays/me to moderate, then they/I would just shut down instead and the notr network would be worse off for it.
Nostr relays can’t really moderate, as far as I know. They just forward messages. So I guess relays in the UK can be shut down, but then other relays from other countries just take over.
Bookmarks…?
Ah. It was started by a community member, but seems that a team member now vouches for it. CHange made 5 moths ago.
Which they do here. Once you upgrade to 10.11, your database is not 10.10 compatible anymore. So you can’t downgrade without restoring a backup.