Bravo.

For anyone else wondering, it's AS27612 and the registered address is mentioned online -- unsurprisingly -- as the "CALEA Implementation Unit".

WWDC has gone from a launch announcement to an upcoming roadmap, so these are basically iPhone 17 features for most folks.

It's a third-party client making authentication and data collection requests, just like the hundreds of other credential stuffing toolkits (OpenBullet et al.) that are smashing the Venmo platform 24/7.

The most likely outcome for anyone using this is their account becoming restricted for unusual access patterns by the existing models already in place.

Taught me everything I needed to know about being a painter.

Perhaps not the 'best' book ever, but certainly one of the most impactful for me as a common-or-garden 18-year-old realising for the first time that our political and economic systems aren't some sort of almighty edict and could be critiqued.

My two main takeaways were:

1) This is fun

2) Why do we put up with all this garbage in modern development

2a) Okay I guess Tailwind is more useful that I assumed

And it’s legitimately made me think I could build and launch something on my own, which I’ve never had the confidence to try before.

Not intentionally though - I have my password stored in 1Password, so I know it's correct, yet every time I try to purchase something through bestbuy.com I trip some sort of ATO protection that falsely claims my password is invalid.

I'm entirely willing to believe it's something on my side (ad blocker, local DNS blacklisting, etc.) but after a certain number of occurrances, you get bored trying to debug the problem and just follow the path of least resistance.

I wonder if the Starbucks story was one of those situations where the CEO had a pet project but the rest of the company silently conspired to kill it? I feel like I'd be the exact target market for this, yet I've never heard of either Clover nor Starbucks Reserve before.

What level/grade are folks generally talking about here? Or is this a difference between applying for a role vs. being hunted for it?

At $previous_job (payments provider), the sales engineers would often spot merchants using sequential order IDs and mention it to the account managers.

Rekt? I guess not, but knowing what percentage of their business we processed was extremely valuable information when it came to renegotiate the contract.

When there's a new python version I'm interested in, I install it via Homebrew and update my zshrc to clobber everything else via $PATH. All my scripts and tools are broken? Just reinstall the packages globally. Whatever.

Since the big 3.x transition, it's pretty rare for forwards-compatibility to break (IME), and if something does, I can just try running prior python3x binaries until I find the last version that worked.

It's hideous, but honestly the least stressful way I've found to date.

In Arizona, it's required that all immunizations given to <=18s are reported (along with "encouragement" for providers to report adult immunizations) and this is the basis for determining if the child may attend a public school, for example.

It sounds like you've put genuine thought into this, and your privacy policy is very readable, but it suffers from the generic "WTFPL" clauses.

For example, you clearly specify who the third-parties are and what data is shared, which again is commendable. But it's combined with "we may use your data for [any] other purposes", "we may sell and may have sold [extremely personal PII]", and so on.

Are you doing this? Doesn't seem like it. Could you? Apparently, and that's part of the concern.