Plus Foldersync is way harder on battery, I’ve experimented a lot.

This is very configuration dependant. With an aggressive schedule checking a large number of files, it certainly can use a lot of battery; but I’ve had it setup to sync my entire device to my server a couple times a day, while also monitoring/syncing images immediately on creation/change. It doesn’t even register on androids battery usage monitor as it uses so little power.

Anyway; just listing an option for people to look at

I’ve always just used Folder Sync + an ssh server, if people are looking for alternatives.

This seems like a bad time for everyone.

Idk about you, but I take bites of my hotdogs…

Yo short stuff; you can’t be smokin the stickey-icky in my house and not sharing… That’s just rude

Telus is the one that’s sent me dozens of notices; they don’t care. They just pass on the message they received and wash their hands.

In Canada, I get letters (well emails) when I rawdawg some torrents; but it’s never gone further than that.

Prior to using usenet, I constantly torrented w/o a VPN (talking 10+ TB of data across 3ish years) and received a new email notice or two every other day. I’ve still got a folder with 60+ notices. ISP doesn’t give af, they just forward the copyright notice in the form it was sent to them, and that’s it.

Now though I primarily use usenet and haven’t gotten a notice since. Downloads are also way way more reliable and faster.

That’s covered in the article you’re commenting on.

Another user on GitHub also pointed out that Microsoft’s own DISM can be used to disable the Recall service without the File Explorer consequences, although Titus points out that this behaviour seems inconsistent, as in his testing, the File Explorer still changed its appearance after a restart. Inconsistency aside, it’s unlikely that any non-technical Windows user will even know what DISM is, never mind how to use it, and this reliance on a command-line utility to remove a controversial feature is indicative of MIcrosoft’s goals.

Because 2 letter tlds are reserved to be issued to countries. Ideally the country’s 2 letter country code.

https://en.m.wikipedia.org/wiki/Country_code_top-level_domain

All ASCII ccTLD identifiers are two letters long, and all two-letter top-level domains are ccTLDs.

at least for the technology-related domains.

It’s not a technology related domain though; it’s a country’s domain that happens to be used for a lot of tech.

With the country dissolving, the domain does too, so it can become available for future countries.

So the .su domain was handed to Russia to operate alongside its own (.ru). The Russian government agreed that it would eventually be shut down, but no clear rules around its governance or when that should happen were defined.

But ambiguity is the worst thing for a top-level domain. Unknowingly, this decision created an environment in which .su became a digital wild west. Today, it is a barely policed top-level domain, a plausibly deniable home for Russian dark ops and a place where supremacist content and cyber-crime have found cover.

I seems IANA would like to not repeat past mistakes.

More than any other piece of self-hosted software: backups are important if you’re going to host a password manager.

I have Borg automatically backing up most of the data on my server, but around once every 3 months or so, I take a backup of Vaultwardens data and put it on an external drive.

As long as you can keep up with that, or a similar process; there’s little concern to me about screwing things up. I’m constantly making tweaks and changes to my server setup, but, should I royally fuck up and say, corrupt all my data somehow: I’ve got a separate backup of the absolutely critical stuff and can easily rebuild.

But, even with the server destroyed and all backups lost, as long as you still have a device that’s previously logged into your password manager; you can unlock it and export the passwords to manually recover.

There’s a simple solution to make everyone happy:

I’ve heard of ytdlp many times, but I rip so little from youtube I just haven’t had the need to look into it.

YouTube tends to be one of my last resorts for media sources.

I tend to rip music videos from youtube with yt1s.com

It’s manual and tedious, but works. I’d like a solution like the arrs, but I also don’t keep many music videos so 🤷

@[email protected] I could kiss you. You’ve been invaluable my friend, thank you!

Just gave this a test: CNAME ombi.domain -> local.domain with cloudflares proxy re-enabled.

Now the HTTPS, A, and AAAA requests all receive the CNAME response and browsers are happy. I didn’t even have to modify ngnix to recognize local.domain like I thought I might.

I think I’ve found the problem:

It seems my issue is pihole being unable to block/modify dns requests for HTTPS records, which don’t match the LAN IPs pihole handed out in A/AAAA records.

I’ve disabled cloudflare proxying so they don’t have HTTPS records to serve, but I’ll have to replace pihole with a better lan DNS solution if I want to turn that back on.

Thanks. That seems to be a similar, but slightly different error. I think the below may apply though.

I believe I’ve tracked down more of my issue, but fixing it is going to be a hassle:

When cloudflare proxying is enabled, there are 3 DNS records involved; A record with cloudflares ipv4, AAAA record with cloudflares IPV6, and the key to this puzzle: an HTTPS record with cloudflares ech/https config.

With pihole I can set DNS records for A/AAAA, but I have no way of blocking/setting the HTTPS record so it gets through from cloudflare.

The LAN A/AAAA records don’t match the HTTPS record from cloudflare, so browsers freak out.

Once I disabled cloudflares proxying, I no longer get HTTPS records returned and all works as intended.

I’ll either have to keep cloudflare proxying disabled, or switch pihole out for a more comprehensive DNS solution so I can set/block HTTPS records :(

Thank you @[email protected] for pointing me in the right direction.

That unfortunately did not work. I am only getting the ipv4 address now, but I still get the same ECH error in chrome 1/5 tries.

Firefox now changed errors from ‘invalid certificate’ to ‘connection is insecure but this site has HSTS’ (true). Still wont show the cert or provide any further info. (forgot to grab a screenshot before the below ‘solution’)

I’m really annoyed at this point and have just disabled cloudflare proxying for this service. That seems to have sorted it for all browsers. I may look further later, I may just say fuck it and leave it like this. Gotta walk away for a bit.

I’ll look into that next if what I’ve done doesn’t work. (see other comments)