Statistically sure but then it’s on the algorithm to recommend stuff that interests you more. Reposting things is just spoofing the recommendation algorithm and making things more likely to bubble up to you which is always going to cut both ways. Some people want duplication, others don’t.
Not to be that guy but no one expects someone to stumble on earlier posts and thus not repost them. But you can quite easily search for them before reposting the exact same thing. One requires luck the other requires care. It’s similar to not asking for support with an issue that’s already been discussed in a separate users question.
I’ve never had this issue but I run basically everything through docker and presumably it bundles this by default.
I would recommend just using caddy. It removes the complicated part of ssl management. For a local network it’ll setup a local self signed certificate authority and you can just install those certificates to any devices on your LAN that you want to have access. For a public setup it’ll use letsencrypt. You will still need to setup dns if you want wildcard routing.
Ddns-updater and porkbun.
I funnily had the same use case. Two different jellyfin servers for complete separation. Both routing through gluetun. The reason this doesn’t work is because the network mode setting you have basically makes all three containers operate in the same network. Meaning if one binds a port the others can no longer bind the same port. Their different hosts but all sharing one network and port range. To expose the ports you can move that ports setting from C1/C2 to the gluetun service definition. This’ll still work because when C1 binds to 1234 it’ll be reachable through the gluetun service.
Note: as mentioned if C1 and C2 cannot use the same port if you also want to have service gluetun set. More likely than not you start C1, it binds to the port, start C2, it tries and fails to bind to the port and crashes. I fixed this by making one of my jellyfin containers use a separate port. If you can’t configure the ports of your services then there’s no real recourse FWIU.
This is absurd. Are you being serious? I’m aware how sanctions are setup in the US because I’m compelled to complete hr training on them every 8 months even though I have no interaction with anyone that would overlap with sanctions requirements. That doesn’t make it any less absurd. It’s also not on me to somehow categorically disprove the link between Linux contributions and military work, the onus there is and as it always should be is on the entity demanding you do something in response to it. But OK, let’s say all the work on Linux coming from anyone who happens to live in or have a Russian nationality somehow goes back to the war effort. Ban work on Russian firmware or Linux compatibility with Russian hardware. Don’t ban Russian people unilaterally and with force using flimsy hypothetical justifications and reductive arguments. I go back to ww1 and the role of scientists in war. They should abstain. Developers should abstains. We don’t belong to the countries we live in, our work should exist for all mankind and to the betterment of society as a whole. If the US wants a trade embargo, or a corporate berlin wall I’m all for it. This is not that.
Edit: Also, not really relevent, but I would be absolutely amazed if the Russian government is somehow on the bleeding edge of linux development and actively deploying head branch builds of linux with the latest available firmware. Most of the US government still runs on windows out of sheer apathy. If they are using these contributions in drones their almost certainly backporting to a stable linux release and that means this kinda ban if it follows you’re reason isn’t going to have an impact until a few releases down the line and that’s easily bypassable by just not upgrading linux. Russian already presumably sanctioned to older hardware (excluding self manufactured) so that isn’t even a hard choice.
I still maintain this is a pretty weak argument. And it does nothing to address the question of what do these devs contribute to instead because it’s not likely their suddenly gonna become jobless and dependent on the state. These are highly skilled and motivated developers just based on what ive heard about getting contributions into the mainline kernel. I just hope they don’t get recruited to write drone targetting systems because we’ve decided to ban them from contributing to a project everyone benefits from.
I don’t really see how that relates. These are open source contributors to Linux, a global os everyone has access to. Their contributions would benefit everyone. If their employed by a Russian company paying them to contribute to Linux then the economic aspect might make sense but I see that as a pretty weak argument. Now those devs are more likely to be poached to work in industries that more directly contribute to the war. This is like ww1 and German scientists who were supposed to be impartial getting recruited into the war machine to create poison gas. We shouldn’t be encouraging that or making it easier.
Man, despite loving Foss this whole debacle is so disillusioning for anyone that ever wanted to pivot to working on it full time. You don’t have to agree with people wanting to try new things, but the bare minimum is not to spew vitriol to keep them quiet or claim you’ll break their stuff and that’s their problem because they aren’t doing things the same way as you but still depend on a shared ecosystem. All we have to do is be bloody polite to each other and build cool sh*t, why is that so hard. All the best to the Linux rust rewrite for these folks, but to me it just feels like both projects are losing here. Linux losing the passion and drive for adopting more modern stuff and all the folks with that drive opting to restart from scratch because too many people refuse to get along.
I have the utmost respect and appreciation for mullvad but I don’t need a vpn without port forwarding so I cancelled my sub. They are still objectively the vest vpn, this is the only sticking point.
What security holes? I think the bigger problem here is relying on a media platform to also maintain security protocols. Use authelia or plug some other well maintained and hardened security mechanism on top of jellyfin. Then put it in front of everything else like the arrs, etc. Its weird to me to just setup jellyfin, make it Internet facing, and believing everything is just gonna be safe and secure with no issue. Frankly id prefer if all these services came without security. Its a royal pain to bypass it for localhost or proxying with something like authelia.