There’s no backend server to do the transcoding in this case. Kodi can access raw NFS/SMB file shares the same as accessing local storage, so it’s just reading the file over the network, the same as if you were playing it in VLC on your PC.
Agreed. I’m willing to allow that adults should have the right to refuse vaccination, as stupid a decision as that may be, but very much in the same way that adults have the right to starve themselves. You do not have the right to starve your children, and vaccination should be seen in the same way (it should also never come at a direct personal cost; vaccines solve public health problems, they should be paid from the public purse).
I write technical documentation and training materials as part of my job, and the state of most open source documentation makes me want to stab people with an ice pick.
Mine too. A friend of mine set up a myth box in a shared house at uni, and I was enthralled by the entire concept of just building your own tech to do cool shit.
Yes, you will need a tuner card or USB tuner. The go to apps are mythtv and Kodi. I’d start with Kodi and see if that does the job for you. If you check the Kodi wiki you’ll find resources on what specific tuner cards work best.
Self hosted DVRs are definitely a dying breed, but there’s stuff out there if you’re willing to dig.
For Jellyfin integration, once you have the files you should be able to dump them out to a folder where Jellyfin can scan them.
I bought a “lifetime premium” for something like $30 USD I think
Same
But use Airsonic instead, it’s a fork that’s free in both the beer and speech sense.
There’s also Navidrome, which is a unique backend, but works with existing Subsonic clients. Check out both, see which one you like better.
If someone has the resources to simulate a universe, they probably have the resources to stimulate an arbitrarily large number of universes. This also assumes that any civilisation within the stimulated universe reaches the level of technological advancement required to make a universe level simulation. We’re talking, probably, whole networks of Matrioska Brains, that sort of thing.
Being a terminal purist is wonderful for those of us who live our lives deep in the caverns of Linux, but in actual production use you very often find situations where less technical users have to interact with the systems that we build.
For my work, I need a way for low level tech support and technicians to go in and restart a container from time to time, and these people curl up in a ball and scream if you show them a command prompt. Having a UI removes a lot of friction.
To be fair, Dockge is very, very new. I imagine features like that will turn up soon enough.
Technically true, but if you actually try to interact with those compose files directly then shit gets really fucky.
Awsome resource. You win the Internet today.
For the record, so are a lot of 3.5s. Always read up on your drives before buying.
Get to grips with Docker. OCI containers are the standard method of self hosting basically everything now, so once you’re comfortable with Docker and compose files, literally anything you could want to host is available as a drop in component for your system.
An excellent way of playing around with Docker is to install Dockge. It’s a web UI with some really helpful features. First, it can convert Docker Run commands into compose files for you (once you start to play around with this it’ll be clear why that matters), and second, its very good at pointing out where and how you’ve made errors in your compose files. But most importantly, unlike Portainer (the most popular Docker UI) it works with the Docker command line rather than trying to replace it. With Dockge you know exactly where all of your files are and if any part of your setup breaks you can repair it very easily. It also doesn’t have Portainer’s problem of flashing error messages on the screen for 0.3 seconds then whisking them away. It exposes the entire Docker terminal output so your debugging process is much, much easier.
You’ll also want to learn about reverse proxies (I reccomend Caddy for its unbelievably simple config file; an entire site is three lines). These are really important for serving multiple different services from one source.
For anything that you can’t run in Docker, VMs are an acceptable solution, and LXC containers are a better solution, but one that requires a little more work to get to grips with (fun fact, LXC has its own web UI, which is fantastic, but almost nobody seems to even know it exists). Since you’re already familiar with Linux, you may want to ignore the suggestion to use Proxmox and just set up a server with your preferred flavour and go from there. All of this can be done with any modern Linux distro, so you might as well work in an environment you’re comfortable in.
There’s a lot of misunderstanding in this thread about how captchas work.
What modern captchas examine isn’t actually your ability to solve the puzzle… It’s how you solve it. Things like mouse movements and how you type are big factors. So a bot would process for a moment, and then basically copy and paste in the answer, whereas as a human is going to type at a normal pace, often with pauses as they double check the details. Same goes for the click the tiles challenges. A bot will work through systematically, a human will bounce around, and their timings will be very different.
Hating anything that helps the planet is now the religion of the right. We’re talking about people who deliberately mod their trucks to create more harmful emissions.
Yeah, 90% of the time someone says pothole and I hear “The story didn’t spoon feed me the answer and I’m inexplicably mad about it.”
In another thread just today I was pointing out that this is the result of the Cinema Sins school of criticism taking over the average person’s relationship with media. People seem to genuinely think that how good or bad something is comes down to tallying up “plot holes” to come up with a sin score and calling it a day.
Plot holes are fine. Even legitimate plot holes are fine; if a story actually captures your attention and holds your emotional engagement, you won’t be thinking about plot holes because you’ll be too busy enjoying the story. This is Hitchcock described as Fridge Logic; problems that only occur to you hours after the movie is over and you’re staring into the refrigerator trying to decide what snack to make (yes, that’s the actual origin of the term). And he was very much of the opinion that this was absolutely fine; as long as any apparent inconsistency wasn’t so egregious as to break suspension of disbelief right there in the moment, it could be safely ignored.
When people fixate on minor plot holes it’s either because a) fundamentally the story sucks, so their mind is wandering, or b) they’ve trained themselves to constantly find or invent logic holes instead of actually trying to engage with what the storytelling is doing.
Because my basic humanity requires me to care about theirs, even if they don’t care about mine.
So is the US and Canada and the UK. Should I wish for those countries to be genocided too?
Please don’t use Portainer.
If you want a GUI, Dockge is fantastic. It plays nice with your existing setup, it does a much better job of actually helping out when you’ve screwed up your compose file, it converts run commands to compose files for you, and it gets the fuck out of the way when you decide to ignore it and use the command line anyway, because it respects your choices and understands that it’s here to help your workflow, not to direct your workflow.
Edit to add: A great partner for Dockge is Dozzle, which gives you a nice unified view for logs and performance data for your stacks.
I also want to note that both Dockge and Dozzle are primarily designed for homelab environments and home users. If we’re talking professional, large scale usage, especially docker swarms and the like, you really need to get comfortable with the CLI. If you absolutely must have a GUI in an environment like that, Portainer is your only option, but it’s still not one I can recommend.