- 2 Posts
- 104 Comments
41·12 days agoI know right? I’m constantly confused by this when I’m dealing with kubernetes networking
You haven’t addressed the case of migraine to a non geographic tld
I trust none of the I can. People are running anything on kubernetes 😆
Oh wow! And that reservation makes so much sense under these circumstances. Obviously, we could never consider the possibility of a three-letter TLD for a country or migrating a two-letter TLD to a non country specific name because reasons.
iPlayer isn’t an ‘open’ service- you have to use a supported client, even if that client is a web browser. Your options are limited to platforms that can support those clients. Personally I’ve found Roku preferable to Chromecast, firestick, full PC. I may at some point have tried to get iPlayer running with Kodi back in the day, when it was XBMC, but XBMC was pretty clunky anyway, let alone on raspberry pi.
Welcome
Depends what you want to play it on. In my house we have:
3 laptops 2 tablets 2 mobile phones (1 android, 1 iPhone) TV
Not all these devices support local storage for music and it’s a pain to sync files between them. With Jellyfin the complete library is in one location with a consistent interface. It can also be made available remotely if I choose.
Ok. I missed which sub I was in, sorry. There is a Linux desktop Jellyfin app but I haven’t used it myself. In my own case I am running Jellyfin on Linux. I use various clients, including web browser (laptop), Android and Roku (TV) and find it works really well. In the past I had tried with the ‘connect directly to the server’ route with XBMC (as Kodi was called then) and it never worked well, with similar issues those described in other comments.
Well if you want a windows pc app there’s this. There’s a list of official clients but it sounds like you already know it
Sorry but it doesn’t sound like you know what you’re talking about. Jellyfin is a server. Sure you can use a web client but there are many others too
People like this
We’re going to need to know as a minimum:
- Linux distribution and version
- Jellyfin install method and version
- what you have already tried- not sure where all those flags are coming from
I would also support the comments here recommending that you use docker. There’s only a small number of Linux distributions and versions where a distribution package installation of jellyfin is fully supported, but even then what you need to do varies across each one. All Linux distributions and versions support docker and the process is essentially the same for all of them.
Ok, aside from Android, I’ve yet to see any serious usage of SELinux in the real world and I’ve been working on cloud tech for years. Acknowledged issues such as complexity aside, it’s really just that much less relevant in a modern, single purpose environment such as Docker/kubernetes/cloud functions/etc
I feel this and some of the other comments in this thread are missing the point. It’s not about me and my followers. It’s about the news sources and topics that I search for or follow. They simply haven’t moved to Mastodon and where notable individuals that I follow have tried, it simply hasn’t worked out due to lack of interest. I’m not interested in the fediverse as a topic in itself, I’m interested in the topics and events I want to follow. Something happens and I can find and read and watch clips about it on Twitter. Not so Mastodon.
people I follow
I’ve been on Mastodon for over a year and the content simply isn’t there. Several of the people that I follow on Twitter have tried moving or duplicating to Mastodon. They’ve had a fraction of the visibility and engagement from commenters that they would get on Twitter. Invariably after a few months they have essentially given up on it as a primary medium. For me the discoverability is essentially non-existent, which I don’t think is helped by the idea of it being based around instance-local communities, which have no meaning when you’re looking at something like Twitter.
If you’re transferring Linux to Linux then I really wouldn’t recommend samba. Why not SFTP/Rsync? Compression, and error checking built in.