Everyone here is using Lemmy and is either in SWE, Sys Engi, Sys Admin or DevOps.

/s kinda

Bring back the original. Bring back Jeff.

KeePass + Tresorit

Is that Louis CK?

Also from San Andreas (or maybe Vice City) R1 R2 L1 R2 left down right up left down right up. It was used for different weapon sets and I think you could change the dpad combo at the end for different sets (eg left down right up left down down down)

Good idea. I should back these up to Tresorit from time to time as well. Thanks!

Maybe this isn’t a robust strategy, but I run HA in Proxmox and have nightly snapshots of that VM. Anytime I need to restore I just revert to the appropriate snapshot

+1 to this. Tresorit and Mullvad are both exceptional

I left to Tuta (E2EE and German based) and switched from Simple Login to Addy. Took less than an hour and it’s been smooth sailing.

Reminds me of project Silica. Media historically was more durable (stone/ ink and cloth paper, etc) but had a low data density. As density increased, so did fragility

So sad, I remember seeing his YT vid announcing his health updates and mentioning he was getting things in order to make his network more manageable for his family :(

He seemed like a great dude.

The file in question can be found here

You’re a legend. Changing SEARXNG_HOSTNAME in my .env file solved it.

Thanks! The output of the xml is as follows

<OpenSearchDescription>
<ShortName>SearXNG</ShortName>
<LongName>SearXNG metasearch</LongName>
<Description>
SearXNG is a metasearch engine that respects your privacy.
</Description>
<InputEncoding>UTF-8</InputEncoding>
<Image type="image/png">
https://192.168.2.20:8080/static/themes/simple/img/favicon.png?60321eeb6e2f478f0e5704529308c594d5924246
</Image>
<Url rel="results" type="text/html" method="GET" template="https://192.168.2.20:8080/search?q={searchTerms}"/>
<Url rel="suggestions" type="application/x-suggestions+json" method="GET" template="https://192.168.2.20:8080/autocompleter?q={searchTerms}"/>
<Url rel="self" type="application/opensearchdescription+xml" method="GET" template="https://192.168.2.20:8080/opensearch.xml"/>
<Query role="example" searchTerms="SearXNG"/>
<moz:SearchForm>https://192.168.2.20:8080/search</moz:SearchForm>
</OpenSearchDescription>

It looks like it’s set to use https://192.168.2.20:8080 for some reason. https://search.home will resolve fine but using https with the underlying IP will not.

Not that this makes it any better, but a lot of other tech companies are also doing this, and it shouldn’t go unnoticed

Is keeping everything inside of a local “walled garden”, then exposing the minimum amount of services needed to a WireGuard VPN not sufficient?

There would be be no attack surface from WAN other than the port opened to WireGuard

Exactly this. Everyone focuses on how fast you can charge a phone, but 99% of the time I’m charging over night and would prefer a slower charge.

I just capped mine to 90%, if that goes well I might go down to 80.

Do you think trickle charging via wireless would be significantly worse?

I was actually thinking of using the battery charge limit feature to prevent charging above 90%. Not sure I could do 80 without an charge during the day, lol

Yes. It’s a tech/ nerd bubble here.