Worth reporting the phishing domain(s) so they can potentially be red-banned https://safebrowsing.google.com/safebrowsing/report_phish/
579 karma · joined May 17, 2011
Mastodon https://hachyderm.io/@GBrayUT Threads https://www.threads.net/@GBrayUT
[ my public key: https://keybase.io/gbrayut; my proof: https://keybase.io/gbrayut/sigs/gjXWe_M0-pf2NttqXdOE_0cjYyuN9inOSy9Ev1DRLIc ]
https://youtube.com/@cuttingedgeengineering
https://youtube.com/@snowballengineering
https://youtube.com/@noengineerhere (but probably too much comedy for your taste)
https://youtube.com/@matthiaswandel
https://youtube.com/@agingwheels
Also use the Bee Motion ESP32-S3 (https://www.crowdsupply.com/smart-bee-designs/bee-motion-s3) for their PIR motion sensing and running other sensors around the house.
And I have an old Wemos D1 mini connected to my Arduino based smart garage door that helps automate things like lock/unlocking the front door or triggering other presence based actions.
Would having a 3rd party host the services in the EU meet your requirements? Or having data residency restrictions with strict key management, EU based support, and access transparency/approvals?
IMO Google is also taking this seriously, but I am genuinely curious if any off the above would meet your requirements.
I used that trick when .dev was launched and snagged a-z.dev for all my future domain name needs
https://airflow.apache.org/docs/apache-airflow/stable/concep...
I've only ever used their site when moving money in or out of the IRA but it's a pretty terrible UI and they don't seem to be very responsive. I've had a withdraw pending for over 4 weeks now trying to move money to another custodian.
You are probably better off finding a different approach.
Once the vendor fixed the issue it shaved a few minutes off the install time that had previously just been a UI glitch (processing the large backlog of progress bar update messages).
"This should not be taken terribly deeply as a judgement of bazel. Our other build (make) is full of issues, it's just impractical for us to continue to maintain both & for our usage & as voiced by our contributors we opted to stick to the build we've been releasing with for ages"
Providence: Failure Is Always An Option
https://jasonpunyon.com/blog/2015/02/12/providence-failure-i...
Which has one of my favorite quotes about scope creep:
Kevin and I have essentially become allergic to big projects. We attempt to practice “What can get done by Friday?” driven development. Keeping things small precludes a whole class of errors like “We need a new datastore”, ‘cause that ain’t gettin’ done by Friday. It’s hard to sink a week on something you weren’t supposed to be working on when all you have is a week.
That's the one that took down Stack Overflow a few years ago https://stackstatus.net/post/147710624694/outage-postmortem-...
It also has a "take on call for the next hour" button, which (for logged in users that matched a pagerduty user) would create an override for the next hour. Really handy when you are starting a change window and don't want to risk waking up the on call.
Are you using envoy at all in your main http ingress path? You mentioned haproxy and AWS ELBs, but it wasn't clear if envoy is also being considered for public ingress traffic.
Keep up the great work!