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.
I highly recommend the https://dailytechnewsshow.com/ podcast by Tom Merritt which usually runs 30 minutes episodes, or their 5 minute Daily Tech Headlines version.
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.
Many TLDs don't count (letter dash letter) as a premium/reserved domain like they do for other dictionary words or 2-3 character domains. Looks like v-s.space is claimed but for example z-s was just $9.99 a year
I used that trick when .dev was launched and snagged a-z.dev for all my future domain name needs
Strata was the custodian for LendingClub IRA accounts, but sounds like they have had some sort of falling out recently. Got an email this month about switching to https://www.altoira.com/ and then another from Strata trying to get me to stay. Now Stratas charging $100 fee for any accounts that didn't renew earlier this year.
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.
Reminds me of a Windows installer I working on many years ago, that seemed to take a long time using CPU but otherwise not doing any real work. Turned out the SDK we were using tried to update the progress bar every kilobyte or something like that, and our near-gigabyte sized packages filled the message loop with a bunch of pointless updates (30.001% -> 30.002% but both displayed as 30%).
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"
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.
Is there any way to setup a sharding solution for Prometheus? Like instances per AZ or that only scrape a certain set of nodes? On our larger clusters we had issues even with the optimized Prometheus instance in kubecost, and it's starting to look like metrics collection/processing may be a big driving force on our cluster scaling designs.