![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
You would expose a single port to multiple vlans, and then bind multiple addresses to that single physical connected interface. Each service would then bind itself to the appropriate address, rather than “*”
You would expose a single port to multiple vlans, and then bind multiple addresses to that single physical connected interface. Each service would then bind itself to the appropriate address, rather than “*”
You should consider reversing the roles. There’s no reason your homelab cannot be the client, and have your vps be the server. Once the wireguard virtual network exists, network traffic doesn’t really care which was the client and which was the server. Saves you from opening a port to attackers on your home network.
Sorry I should have said “carbons and carbons related qol extensions”
Did you ever get carbons working properly? (As in, mobile and desktop clients of the same user both getting messages and marking as read remotely between them)
I support your position in principle, but canceled my own nitro when they did the android app redesign. It went from really snappy (respecting system animation scale settings) to completely ignoring them. It feels like molasses compared to every other phone app that operates at the system set 0.25 animation scale.
They also completely broke foldable support, and if your device changes aspect ratios inside a chat, you have to restart your client to get it to behave correctly again.
The enshittification is real and I am voting with my wallet.
Xmpp is by design, an extensible protocol. There just doesn’t seem to be any motivation to develop for it.
especially true for when manufacturers stop supporting the console you invested into, stops making replacement parts, issuing security patches, etc. Having the ability to make, repair and use copies of the games you purchase is critical to digital preservation.
There are also full-suites like rancher which will abstract away a lot of the complexity
How has nobody in this thread said check_mk yet?
It’s free, you host it yourself. It’s built off of nagios, compatible with nagios plugins, supports snmp or agent based checks. It can email, SMS, slack or discord you when something breaks, you can write your own custom checks in any language that can output to a local console… I could never imagine even looking for something else.
“The tryhard poopsock”
has xmpp figured out carbons yet between multiple clients? also are there any good mobile clients?
If one doesn’t exist, it would seem to be a fairly straightforward (if not a smidge tedious) thing to implement. Ever thought about learning web development?
That is only true when you use their “home” feature. It puts the entire thing behind oauth because it has to do so in order to restrict libraries/content to non-full users. Think about the instance where you have a thirteen-year-old kid and you want to restrict them to pg13 and under. Without forcing oauth on local connections they could just sign out and watch all your star trek porn parodies or whatever you don’t want them to see. If you remove the server from a “plex home”, it disables the oauth workflow for local connections as expected.
Don’t get me wrong, I’m not really happy with a lot of their new sharing/social features, and their recommendations on the homepage can fuck right off, but I do think it’s important to be accurate when criticizing. Requiring oauth on local vlans when plex home is enabled is the objectively correct solution.
If they don’t matter currently for moderation I have to imagine they’ll be part of a moderation toolkit eventually. Leveraging community voting to detect spam would be decently effective, especially for fresh accounts.
Are… hygienists famously known for not being smart? I don’t think that’s a thing lmao
Pvp is completely dead, which I think was the game’s greatest longevity strength. Mechanically it’s quite dated but the writing is very fan service
In most modern Linux distributions, you could preconfigure retroarch and whatever else first, then set the filesystem to read-only, while mounting an overlay filesystem on top that is discarded at reboot.
The idea would be no matter how hard he breaks it, he shouldn’t have Root’s password and therefore cannot disable overlayfs
Look for the overlayroot package in whatever Linux distro you’re most comfortable with.
A raspberry pi or orange pi could definitely run all of those things at very low power consumption.
Is that not the right answer though? It can do timestamps or offsets for audio cropping without re-encoding. He’s on lemmy, cli can’t be that scary
That is usually more incompetence than malice. They write a game that requires different operation on amd vs Nvidia devices and basically write an
If Nvidia: Do x; Else if amd: Do Y; Else: Crash;
The idea being that if the check for amd/Nvidia fails, there must be an issue with the check function. The developers didn’t consider the possibility of a non amd/Nvidia card. This was especially true of old games. There are a lot of 1990s-2000s titles that won’t run on modern cards or modern windows because the developers didn’t program a failure mode of “just try it”