I’ve not tried that myself, but AFAIK VLC can be remote controlled in various ways, and since the API for that is open, multiple clients for it exist: https://wiki.videolan.org/Control_VLC_from_an_Android_Phone
There’s also Clementine which offers a remote-control Android app.
https://lemmy.world/post/12995686 was a recent question and most of the answers will basically be duplicates of that.
One slight addition I want to add: “Docker” is just one implementation of “OCI containers”. It’s the one that broke through initially in the hype, but you can just as easily use any other (podman being a popular one) and basically all of the benefits that people ascribe to “docker” can be applied to.
So you might (as I do) have some dislike for docker (the product) and still enjoy running containers.
I personally prefer podman, due to its rootless mode being “more default” than in docker (rootless docker works, but it’s basically an afterthought).
That being said: there’s just so many tutorials, tools and other resources that assume docker by default that starting with docker is definitely the less cumbersome approach. It’s not that podman is signficantly harder or has many big differences, but all the tutorials are basically written with docker as the first target in mind.
In my homelab the progression was docker -> rootless docker -> podman and the last step isn’t fully done yet, so I’m currently running a mix of rootless docker and podman.
Somewhere a monkey paw finger curls and you’re moved to the timeline where the world is in a nuclear winter …
You’ve got a single, old HDD attached via USB. There’s plenty of places that could be the bottleneck here, but that’s among the first I’d check. Can you actually read from that HDD significantly faster than your network transfer speed? Check that locally first. No use in optimizing anything network-related when your underlying disk IO is slow.
In the immortal words of Jake the Dog:
Dude, suckin’ at something is the first step to being sorta good at something.
We are or were all noobs once. Going away from the keyboard is often an undervalued step in the solution-finding process. Kudos!
Can confirm the statistics: I recently consolidated about a dozen old hard disks of various ages and quite a few of them had a couple of back blocks and 2 actually failed. One disk was especially noteworthy in that it was still fast, error-less and without complaints. That one was a Seagate ST3000DM001. A model so notoriously bad that it’s got its own Wikipedia entry: https://en.wikipedia.org/wiki/ST3000DM001
Other “better” HDDs were entirely unresponsive.
Statistics only really matter if you have many, many samples. Most people (even enthusiasts with a homelab) won’t be buying hundreds of HDDs in their life.
Was about to post this, this works well for me.
In my case I’m storing the DB on my Google Drive for now, but Keepass2Android supports many different systems, including “generic” things like WebDAV, so really anything should work.
While Keepass2Android is integrated with the syncing and will always check for conflicts (i.e. check for latest version before saving), the same isn’t necessarily true for the desktop client. But since I rarely edit from both devices at the same time, anything that syncs to the Desktop in a somewhat realtime fashion should work just fine.
And for the few (long ago) cases where updates were overwritten, the “previous version” feature of Google Drive was god-sent! (And KeepassX can simply merge the old overwritten version into the current one and you’ll get the correct merge).
I think the difference is at what level:
I feel OPs critique has some truth to it. I personally would rather stay with raidz by zfs, exactly because of it’s open nature (yes, they too have bugs, nothing is perfect).
I honestly have no real opinion on this (yet), as I don’t know if that would help or not.
But 90% of all policy proposals from the UK end up being terrible ideas, so I’ll just assume this is stupid.
I find that to be a tricky thought experiment.
Can you run a country in a way that peppers the general population with “all is well” propaganda thoroughly and still manages to capture all the necessary information to make properly informed decisions at some high level?
You’d need some “elite” layer of people who get to see unfiltered, honest information, but how would you even collect that information if even local, low-level government actors are subject to (and meant to believe) the propaganda?
Basically what I’m asking is: if I ignored moral concerns, is there a world where keeping the majority ignorant could actually lead to more efficiency than letting knowledge of the state of things spread?
Do you have any devices on your local network where the firmware hasn’t been updated in the last 12 month? The answer to that is surprisingly frequently yes, because “smart device” companies are laughably bad about device security. My intercom runs some ancient Linux kernel, my frigging washing machine could be connected to WiFi and the box that controls my roller shutters hasn’t gotten an update sind 2018.
Not everyone has those and one could isolate those in VLANs and use other measures, but in this day and age “my local home network is 100% secure” is far from a safe assumption.
Heck, even your router might be vulnerable…
Adding HTTPS is just another layer in your defense in depth. How many layers you are willing to put up with is up to you, but it’s definitely not overkill.
They are in fact the same image, as you can verify by comparing their digest:
$ docker pull ghcr.io/linuxserver/plex
Using default tag: latest
latest: Pulling from linuxserver/plex
Digest: sha256:476c057d677ff239d6b0b5c8e7efb2d572a705f69f9860bbe4221d5bbfdf2144
Status: Image is up to date for ghcr.io/linuxserver/plex:latest
ghcr.io/linuxserver/plex:latest
$ docker pull lscr.io/linuxserver/plex
Using default tag: latest
latest: Pulling from linuxserver/plex
Digest: sha256:476c057d677ff239d6b0b5c8e7efb2d572a705f69f9860bbe4221d5bbfdf2144
Status: Image is up to date for lscr.io/linuxserver/plex:latest
lscr.io/linuxserver/plex:latest
$
See how both images have the digest sha256:476c057d677ff239d6b0b5c8e7efb2d572a705f69f9860bbe4221d5bbfdf2144. Since the digest uniquely identifies the exact content/image, that guarantees that those images are in fact byte-for-byte identical.
I don’t follow it either, but read up a bit on it (partially from here https://pluralistic.net/2024/01/22/anything-that-cant-go-on-forever/) and the basic gist of it seems to be:
Boeing has been fucking up perpetually since shortly after merging with McDonnell-Douglas (a company that was apparently well-known in the industry for perpetual fuck-ups) in 1997, but political influence/interests/corporate capture has prevented it from actually failing the way that commercial companies that perpetually fuck up ought to.
What we see now is just another case of some of those fuck ups becoming visible again.
As others have mentioned (and also explained in quite some detail) you’re trying to bite off a lot at once. First, for Jellyfin locally you can ignore most of that.
And if you really want to learn the ins and outs of all that (and I can recommend it, it’s useful), then I suggest you start with some simple web app. Something like note taking or maybe even something trivial like a whoami service, which basically just echos some information it was sent back to you. That’s super useful because you know that it is unlikely to be broken, so you can focus on the networking/port forwarding issues. And once you’ve got that working and have a rough feeling how this all works you can go on to more complex setups that actually do something useful.
Those are usually the prefixes for interfaces which are not quite the same thing as networks. An interface is the surface that connects some device to a network. For example if your router treats its WLAN and its wired network as a single network (i.e. each thing on WLAN can see everything on wired and vice versa) then a specific device might still have a wlan1 and eth1 interface, each one reaching the respective physical network device, while being in the same network.
“One network” here really only means “something can successfully route between all the devices”.
Fun fact: that movie is in fact way less known in Austria than elsewhere. Fun fact: I once saw Michael Moore talk in Vienna and he made some “Sound of Music” joke/reference and the reaction by the audience was … crickets. No one knew what he talked about.
Honestly I don’t believe “Hitler was an Austrian” is as important for Austria to come to terms with as it is to accept/finally internalize that Austria wasn’t “the first victim”, but to a large degree welcomed the Anschluss (not 100%, obviously, but quite a big majority).
That is unfortunately pretty true. The So-called Austria victim theory, which is basically “oh, we poor Austrians were Nazi Germanys first victim!”, is obvious bullshit.
This was only really officially stated to be definitely false in the late 1980s … and there’s still plenty of people who probably would believe it or at least like to pretend that that was the case.
But as I said: at the very least we got to the place where pretty much any official/political actor has to acknowledge that it’s wrong.
Wenn ich sehe wie viel Infos dann öfters mal einfach aus chatprotokollen rauspurzeln glaub ich schon das öfters mal was gefunden wird.
Man muß nicht dumm sein um nicht perfekt in opsec zu sein. Es gibt jede Menge Wege wie man was “liegen lassen” kann, vor allem digital. Und wenn man sich damit nicht regelmäßig beschäftigt kennt man nicht alle.
Einfach aus convenience am Laptop im Chat eingelogged bleiben? Ups, jetzt ist er konfisziert …