They’re not handing over keys though. They’re just not offering ADP in that region anymore(?) I doubt they would be allowed to hand out keys (which they do not hold) to another government that would compromise American businesses, agencies, etc. The US was already noticing the dangers in this demand and I’m hoping that this was an attempt at a compromise. I guess we’ll never know though, since this included a gag order as well

Ikr? I used Reddit for well over a decade, and left without an issue after the APIpocolypse. Did the same with Proton a couple weeks ago. I have no loyalties in tech.

Monthly for me

Most likely invite links to various groups / contacts

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

/s kinda

KeePass + Tresorit

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)

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, right now Advanced Data Protection (ADP) shows the things that will be fully E2EE, which isn’t everything. Does this mean that, if enforced, that list would remain in place but not actually be E2EE or would be updated to show the items that are still E2EE (if any)? Guessing the former, which is scary.

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.

Yeah, born in 88 and also a lucky number in some cultures

deleted by creator

Meshtastic can be encrypted and is LoRa based. Can easily hit nodes dozens of miles away with a good line of sight. It also relays messages across nodes to reach even further distances.

The file in question can be found here

Ah, I guess I might need to add my RootCA to my phone, laptop, pc huh? That would get rid of the untrusted warnings. Yes, please feel free to share if you have documentation!

Update: I setup my own local CA and got it working. Thanks for the tip!

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

Gotcha, that matches my assumptions. Yes everything is internal. It’s accessible remotely via Wireguard, but I mostly wanted to get some practice with NGINX/ TLS certs (also way easier to refer to things around the house with <service>.homelab isntead of IP:port, haha.

So if I did want this to be fully encrypted, I would essentially need to configure each service (jellyfin, home assistant, etc) to have SSL on them with this self-signed cert/ key that I used on NGINX (or perhaps new cert/ key) and then I would be all set?

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.

I haven’t. I created this custom cert and uploaded in in NGINX (NGINX itself isn’t using SSL) and applied it to each proxy client, then when I visit one of them it appears to be HTTPS, but I feel that it probably isn’t actually giving me the protections I imagine.

They’re both different VMs on different VLANs running on the same Proxmox host