I use a variant of this: https://github.com/linuxserver/docker-wireguard

You don’t need two different containers for this. They’re going to either fight each other for control over the networking tables or run wireguard in wireguard

So I had a chance to try this out. It wasn’t on Google Play Store, only F-Droid. There isn’t really SSO support, you either login with User/Password or a token. Instead, I login with my browser, get the token and paste it in. That works fine, but an ideal world is just pop up an browser WebView and go through the flow, then grab the token. Maybe it was intentional, but PaperlessShare registered as an Open handler for PDFs and the share menu, whereas this is only share menu. This seems to mean that I need to grant file access, whereas the open handler didn’t need that I think.

Overall, it does the job and gets my docs uploaded.

How hard would it be to contribute these improvements back to the project in the form of either distro package updates or documentation changes? Did you consider that?

Can you expand on the OIDC/OpenID support? Does it support SSO based authentication to Paperless? That’s my biggest problem with PaperlessShare right now. I can’t actually sign in because I use an SSO provider.

I respect your strong ethics and sticking to them, but saying they people support genocide for using software hosted on GitHub is an extreme position.

I could easily change this: Do you drive a car or fly a plane? Then you must have no red lines against climate change.

Tailscale Funnel

Not from PSU data, but I was running Kepler on my dev servers. But then I stopped because it correlated strongly with system load and didn’t really think I learned anything new from graphing it. Having the full system usage might actually make this monitoring useful.

If you alter it to 0.0.0.0 then it shouldn’t pop an SSL error, it would be a connection failed error.

Right. Zero trust means at the very least you need to add AuthN and AuthZ to every endpoint with no exceptions for internal IP addresses.

Encryption at rest just means the data itself is encrypted when stored on disk and the key is somewhere. It doesn’t dictate that the key is not visible to the server.

Encryption in transit refers to an encrypted channel from client to server.

E2E encryption usually refers to encryption from one entity to another where any intermediary servers do not have the ability to decrypt

Source: too many years doing application security at my job

After I read this, I thought it would be really cool to try to make this myself. But then I realized I’m barely able to get a simple circuit working much less one that involves complex RF signalling.

I really want to like Nix. The idea of declaratively defining my entire system sounds great. I can manage it with Git and even have multiple machines all look the same. I can define my partititioning once and magically get a btrfs disk working. Wow!

But I find the language confusing no matter how many times people say it’s easy. I have a lot of experience with other programming languages so maybe it just doesn’t mesh. It also gives terrible error messages that are hard for me to understand. And Nixpkgs is unpredictable for what version I’m going to get. One of the services I installed ended up being a release candidate version which was a surprise. What if I don’t want the latest version of Docker? How do I pin it? Do I have to duplicate part of Nixpkgs? It just feels like a monorepo where everybody has to be on the same versions. Why on earth do the Nix language docs start by introducing math expressions instead of here is a simple self contained thing that installs one program. Here’s how you configure it. Here’s how you expand. Why does the dependency graph seem to pull in so many unnecessary dependencies? For example, I tried to build a minimal Docker image (which Nix looks to be a very good fit for), but I couldn’t figure out how to strip out dependencies that likely were only used during build for a dependency.

I still like the idea and have managed to get my server defined entirely with NixOS which is very cool, but I can’t recommend this to my tech friends because if I’m confused they will be more so.

The point seems to be able to handle a UPS failure

My Framework laptop uses fwupd for all the firmware. I was pleasantly surprised when I plugged in my Logitech receiver and it told me there was an update for the receiver.

Its not difficult for technical people like you or me, but my friend who just wants to watch their favorite show on my Plex on their TV won’t know how to traffic engineer the traffic over a Tailscale network to my network. My mom won’t be installing Tailscale on her laptop and phone.

With Plex, you’re getting the easy ability to grant access to users. You get a single pane that can search across multiple Plex instances, and NAT traversal/port forwarding. Jellyfin makes you figure that out yourself.

Oh that would be nice. I would use that to just go into the database and fix all my broken music metadata which I can’t see to fix any other way.

https://www.recompile.se/mandos

You’re right. Unfortunately, open-source has proven time and time again to be unsustainable and burn maintainers out

That’s a good reason for people to take the money they would have spent buying a proprietary solution and instead donate that money to an open source project. For me it’s not always about the cost, but what I get out of it. I’d rather the money go to the community and better it.