

Just put everything that doesn’t have OIDC behind forward auth. OIDC is overrated for selfhosting.


Just put everything that doesn’t have OIDC behind forward auth. OIDC is overrated for selfhosting.


I occasionally use middle mouse paste, but I switched my partner over from Windows recently and they were used to scrolling by holding MMB and dragging which seems to be the default on Windows…
I expected there to be a toggle to turn off middle mouse paste but there just wasn’t. I had to go into multiple different places to disable it and enable autoscroll for all their apps. I ended up installing a hacky tool that would just clear the clipboard whenever MMB was pressed.
If anything can make this process easier, I’m all for it.
Base 1 usually uses ones, because it represents summation at that point. Using zero as the numeral would be a bit awkward. Also historically zero is pretty new.
Tally marks are essentially a base 1 system.


You’re arguing two different points here. “A VPN can act as a proxy” and “A VPN that only acts as a proxy is no longer a VPN”. I agree with the former and disagree with the latter.
A “real” host-to-network VPN could be used as a proxy by just setting your default route through it, just like a simple host-to-host VPN could be NOT a proxy by only allowing internal IPs over the link. Would the latter example stop being a VPN if you add a default route going from one host to the other?


Fundamentally, a host-to-host VPN is still a VPN. It creates an encapsulated L2/L3 link between two points over another network. The number of hosts on either end doesn’t change that. Each end still has its own own interface address, subnet, etcetera. You could use the exact same VPN config for both a host-to-host and host-to-site VPN simply by making one of the hosts a router.
I see your point about advocating for other methods where appropriate (although personally I prefer VPNs) but I think that gatekeeping the word “VPN” is silly.


“It has effectively the same function as a proxy” isn’t the same thing as “it’s not actually a VPN”.
One could argue you’re not really using the tech to its fullest advantage, but the underlying tech is still a VPN. It’s just a VPN that’s being used as a proxy. You’re still using the same VPN protocols that could be used in production for conventional site-to-site or host-to-network VPN configurations.
Regardless, you’re the one who brought up commercial VPNs; when using OpenVPN to create a tunnel between a VPS and home server(s), it seems like it’s being used exactly to “create private communication between multiple clients”. Even by your definition that should be a VPN, right?


VPN and proxy server refer to different things. There’s lots of marketing BS around VPNs but that doesn’t make the term itself BS, they’re different and it’s relevant when you’re talking about networking.


Yeah, they mention in the article that the team tries to get “sensitive items” and “harmful substances” but Claude shuts it down. Tungsten cubes, on the other hand…


It’s only “running” the business so much. The physical stocking and purchasing happens by human hands, who would presumably not buy anything that would bankrupt the company because then it’s on them.
Here’s Anthropic’s article about the previous stage of this project that explains it pretty well. Part two is a good read too though.


The idea is that it isn’t just operating the vending machine itself, it’s operating the entire vending machine business. It decides what to stock and what price to charge based on market trends and/or user feedback.
It’s a stress test for LLM autonomy. Obviously a vending machine doesn’t need this level of autonomy, you usually just stock it with the same thing every time. But a vending machine works as a very simple “business” that can be simulated without much stakes, and it shows how LLM agents behave when left to operate on their own like this, and can be used to test guardrails in the field.
If you want to share software like that, just use AppImage. It’s perfect for sneakernet software sharing: no internet access required, and it requires less technical knowledge from end users than telling them to use a package manager. Just copy the file and run it.
Wine literally stands for “WINE Is Not an Emulator”.
That said, Proton is pretty transparent, you can just install any game off Steam right now and it’ll work 9 times out of 10 without you noticing that you’re using wine. I often can’t tell if I’m using proton or not and get surprised when I go into the game files for one reason or another expecting proton and am surprised to find a native Linux build. There has even been at least one time I’ve switched from a native Linux build to Proton because it ran better, and it was just one toggle.
Why the resistance to wine? Did you have an issue while using it, or is it the principle of using a compatibility layer?


If you don’t like the functional syntax you can usually use for each loops to the same effect.
for element in array.iter() {
println!("{element}");
}
If there’s a port you want accessible from the host/other containers but not beyond the host, consider using the expose directive instead of ports. As an added bonus, you don’t need to come up with arbitrary ports to assign on the host for every container with a shared port.
IMO it’s more intuitive to connect to a service via container_name:443 instead of localhost:8443


It’s a trend for homelab folks to use Cloudflare themselves…
5e commoners are 10 across the board.


The UX just isn’t there for MPV. Jellyfin isn’t always ideal but it gives an interface roughly on par with a streaming service. Why should I replace that with a tool like MPV? I don’t need keyboard controls, I watch from my couch. It seems like all downsides to me.


Where’s the second part from?


You’re right. Incidentally, I searched lemmy for “transpeople” and found quite a few hits, some of whom were trans themselves. Not just allies can do it, I suppose. Maybe I’ve just not noticed it before.
I’ve never noticed “transpeople” before, but I’ve heard a lot of trans folk use “transgirl”, “transwoman”, “transman”, etc, including myself once upon a time. I think it’s an easy mistake to make if you don’t think about it that hard.
I definitely feel the lab burnout, but I feel like Docker is kind of the solution for me… I know how docker works, its pretty much set and forget, and ideally its totally reproducible. Docker Compose files are pretty much self-documenting.
Random GUI apps end up being waaaay harder to maintain because I have to remember “how do I get to the settings? How did I have this configured? What port was this even on? How do I back up these settings?” Rather than a couple text config files in a git repo. It’s also much easier to revert to a working version if I try to update a docker container and fail or get tired of trying to fix it.