TIHI.
Simultaneously, I couldn't care less. I do, though, feel this push for transparency in the GUI is counter-productive. Thankfully Apple is bringing "Tinted" as a Liquid Glass option to iOS 26.1.
Readit Newslocaltoast commented on Windows new icons for AI era techcommunity.microsoft.c... · Posted by u/mojo11
localtoast commented on Google's shortened goo.gl links will stop working next month theverge.com/news/713125/... · Posted by u/mobilio
Same here. I am geniunely asking myself for what though. I mean, they'll receive a list of the linked domains, but what will they do with that?
It's not only goo.gl links they are actively archiving. Take a look at their current tasks.
localtoast commented on Google's shortened goo.gl links will stop working next month theverge.com/news/713125/... · Posted by u/mobilio
ArchiveTeam is trying to brute force the entire URL space before its too late. You can run a Virtualbox VM/docker image (ArchiveTeam Warrior) to help (unique IPs are needed). I've been running it for a couple months and found a million.
Docker container FTW.
Thanks for the heads-up - this is a project I will happily throw a Hetzner server at.
localtoast commented on Cloudflare 1.1.1.1 Incident on July 14, 2025 blog.cloudflare.com/cloud... · Posted by u/nomaxx117
That sounds good in principle, but is there a more private configuration that doesnt send DNS resolutions to cloudfare, google et al. ie. avoid BigTech tracking, and not wanting DOH.
dnsmasq with a list of smaller trusted DNS providers sounds perfect, as long as it is not considered bad etiquette to spam multiple DNS providers for every resolution?
But where to find a trusted list of privacy focused DNS resolvers. The couple I tried from random internet advice seemed unstable.
dnsforge.de comes to mind.
localtoast commented on The seedy underbelly of the life coaching industry bbc.com/worklife/article/... · Posted by u/Brajeshwar
Life coaches are the new yoga instructors.
"successful" is a very optimistic way of looking at it. it has several downsides but largely works for my needs:
- read access is mostly available for sensors, even if access wasn't granted.
- some integrations (especially custom integrations) don't care about authorization. my fork mentioned in the blog does, because I explicitly added logic to authorize requests. the HomeAssistant authorization documentation is outdated and no longer works. I looked through the codebase to find extensions that implement it for an example. maybe I should submit a PR that fixes the doc...
- each entity needs to be explicitly allowed. this results in a massive JSON file.
- it needs a custom group added to the .storage/auth file. this is very much not officially supported. however, it has survived every update I have received so far (and I always update HomeAssistant)
I will share what I did in detail when I get some time on my hands
Much appreciated. Sounds as if you're way out of spec. Still; should be interesting to go through your methods.
I do it, but I'm completely insane:
- I actually stay on top of all patches, including HomeAssistant itself
- I run it behind a WAF and IPS. lots of VLANs around. even if you breach a service, you'll probably trip something up in the horrific maze I created
- I use 2-factor authentication, even for the limited accounts
- Those limited accounts? I use undocumented HomeAssistant APIs to lock them down to specific entities
- I have lots of other little things in place as a first line of defense (certain requests and/or responses, if repeated a few times, will get you IP banned from my server)
I would not recommend any sane person expose HomeAssistant to the internet, but I think I locked it down well enough not to worry about a VPN.
> - Those limited accounts? I use undocumented HomeAssistant APIs to lock them down to specific entities
Mind sharing your process to achieve what sounds like successful implementation of the much-requested ACL/RBAC support?
localtoast commented on Fly through your shell history github.com/cantino/mcfly... · Posted by u/lovestaco
I'm enjoying this immensely. Thanks a bunch.
Like if I backup photos from iOS, then remove a subset of those from iOS to make space on the phone (but obviously I want to keep them on the cloud), and later the mobile app gets out of sync, I don't want to end up in a situation where some photos are on iOS, some on the cloud, but none of the devices has everything, and I have no easy way to resync them.
client_max_body_size 50000M;
proxy_read_timeout 600s;
proxy_send_timeout 600s;
send_timeout 600s;
FWIW, my library is about 22000 items large. Hope this helps someone.