Never respond to these, even just to tell them to go fuck themselves. It only confirms to them that the message is reaching someone, encouraging them to keep your number on their list.
Darkassassin07
joined 2 years ago
Weed + movies/tv/youtube
It's also only going to run for like 10min with three engines and that tiny fuel tank.
Fuck them, with a drilldo covered in rusty razor blades.
Two coworkers on equal footing is one thing (though still discouraged), but when there's a power imbalance (ceo-hr, manager-associate) it becomes a pretty significant conflict of interest.
Some examples;
A Manager gives favor to their lover and promotes them over other employees that fit the position better or did more to earn it.
CEO signs off on a big bonus for their subordinate lover, who then shares it with them on a fancy cruise.
Lmao. I'd seen the photo floating around, but didn't know the story behind it
You've always got the human element, bypassing security features; but extra little hurdles like a password manager refusing to autofill an unknown url is at least one more opportunity for the user to recognize that something's wrong and back away.
If you're already used to manually typing in the auth details, you may not even notice you're not on the site you were expecting.
If you really want your kids to know how to take a bullet; you'll just have to shoot them yourself obviously. There's only one good way to learn.
In the last couple of weeks, I've started getting this error ~1/5 times when I try to open one of my own locally hosted services.
I've never used ECH, and have always explicitly restricted nginx to TLS1.2 which doesn't support it. Why am I suddenly getting this, why is it randomly erroring, then working just fine again 2min later, and how can I prevent it altogether? Is anyone else experiencing this?
I'm primarily noticing it with Ombi. I'm also mainly using Chrome Android for this. But, checking just now; DuckDuckGo loads the page just fine everytime, and Firefox is flat out refusing to load it at all.
Firefox refuses to show the cert it claims is invalid, and 'accept and continue' just re-loads this error page. Chrome will show the cert; and it's the correct, valid cert from LE.
There's 20+ services going through the same nginx proxy, all using the same wildcard cert and identical ssl configurations; but Ombi is the only one suddenly giving me this issue regularly.
The vast majority of my services are accessed via lan/vpn; I don't need or want ECH, though I'd like to keep a basic https setup at least.
Solution: replace local A/AAAA records with a CNAME record pointing to a local only domain with its own local A/AAAA records. See below comments for clarification.
All ~~roads~~ videos lead here:
Honestly I'm surprised it took this long. The only other issue I've ever seen (between revanced and the original vanced app) is the watch history not saving a couple weeks back.
That's an interesting but subtle little security feature. Honestly, well done Apple.