Being an indie dev with a pihole setup has been tough - I’ve gotta turn it off a lot for various client projects - but it’s also helped me build more resilient applications that work just as well for people who don’t have trackers enabled.
Being an indie dev with a pihole setup has been tough - I’ve gotta turn it off a lot for various client projects - but it’s also helped me build more resilient applications that work just as well for people who don’t have trackers enabled.
As a web dev I'm running into a lot of security products dorking up web projects and processes these days. It seems to be increasing.
I've got customers with security software or other privacy related tools that are constantly 'trying' to do the right thing ... but just become support ticket overhead for me.
It's ULTRA frustrating at this point.
I've run into several customers now whose email scanners not just block emails arbitrary, but also follow links (fine by me) ... and even SUBMIT A FORM (NOT ok). Presumably to avoid some malware delivery, but now they've submitted something to us on a one time use form...
So just sending them an email means their software submits accept or decline options on a form (with our without the email reaching them) and we get a ton of "but I didn't get the email and I didn't decline anything".
Meanwhile the end customer is too technically behind the ball to entirely understand what is going on, and some ultra aggressive IT admin just keeps doing it. If you have a lot of customers it just seems to never end.
I kinda want to abandon email because of it but there's not a lot of good options.
Other issues include some unknown software installed by someone's kid (their IT guy) that blocks rando boring API calls ... the list never seems to end.
I support these privacy / security initiatives 100%, we don't do any insidious tracking or anything like that, but it is starting to hit entirely innocuous stuff.
The upshot is that the latency between our apps and the application server/database (hosted in the same domain) is much lower than for a conventional web app.
How does this not break large parts of the existing web, ex. 80+% of password reset mechanisms?
When you get enough established paying clients, consider firewalling work gear from home gear.
My client work computers are not my personal computers. My client computers have their own router that is separate from my personal router. At one time I had my personal internet on cable, and my clients on DSL, but unfortunately that's not possible where I am now.
I get a lot of peace of mind from knowing the two are isolated from one another. The only thing they share is a desk. But when work time is done, client laptops go into the closet. Helps with the work-home balance, which is harder working from home.
Thinking about it, I might just do that when I get back home :)
Because the router I own is better than the router I don't own.
Further, everything you describe is a bunch of complexity I don't need in my life. My time is too valuable to spend fiddling with configurations every time some piece of kit does a software update.
The way I do it, I plug a wireless router into one ISP, and a different wireless router into another ISP, and I'm done with it. Simple and clean. I'd rather spend my time with my family than "handling layer 3."
>Because the router I own is better than the router I don't own.
That's obviously not necessarily true. By this logic all upgrades for all time are pointless. Why get a better CPU/GPU/SSD? "The CPU/GPU/SSD I own is better than the CPU/GPU/SSD I don't own" after all. Except it's not, hence the interest in upgrading.
>Further, everything you describe is a bunch of complexity I don't need in my life.
Your setup sounds much, much more complicated actually.
>My time is too valuable to spend fiddling with configurations every time some piece of kit does a software update.
This isn't actually a thing. If anything, a core reason for using VLANs is precisely being able to just have any system at all and plug it in/join network and have it all be isolated and routing the right place with zero configuration.
>The way I do it, I plug a wireless router into one ISP, and a different wireless router into another ISP, and I'm done with it. Simple and clean.
Sounds complex and PITA, not least because it requires multiple ISPs and associated infrastructure, billing, tech support if needed, dealing with any security issues in their bottom barrel AIOs, etc. It's not free either, dual ISPs at least around here could easily add $400-1200/year. That's real money, even at the low end it's more money than a basic quality switch+router would cost.
I have a family member who works in marketing and am regularly asked to either turn off the pihole or add a new URL to the ignored list for exactly this reason.
Or they could ask their employer to pay for a VPN services that comes with DNS. Your family member will then have an easy to understand and easy to spot (VPN is ON) way to 'go into work mode' and out of it for private.
Brave for work, Firefox for private.
With both programs in their computers, or both apps on their phones, people could more easily isolate the two phases of life, without going through all the rigamarole of profiles.
If you care about privacy at all, the web is a very broken place.
By the way, I use VPN to bypass PiHole when I encounter these problems. It's a lot less hassle than switching the sinkhole off/on.