"hister 2: histlectric histerloo"

OMG, you win!!! :-D

I tried the on-device image input model with an app I am building. It's not very good at world-knowledge recall, but can describe the submitted image well enough.

We have one of these in my town, Denton TX. KUZU FM. I think it was one of the first. It was originally a pirate radio station, that went legit with LPFM.

I'll have to see if I can pick that up. KNTU is my go to for music while in the car while hoping to not hit dead spots. It's also a favorite joke on why UNT can't have its station call letters updated when they rebranded from NTSU.

i love this

i thought this was for actual candy and got excited for minute when i saw there was a free tier

Found my answer: https://www.reddit.com/r/ios/comments/14hyn3n/pink_qrcode_li...

https://developer.apple.com/documentation/ios-ipados-release...

I have seen this a lot lately. I am curious to understand how these are used and/or what benefit they provide?

I've not seen this before. Looks more like visual artefacting from a graphics processing error to me on first glance.

Where was this specific ad? Might try to find one in the wild myself?

If it is a QR code it seems like maybe some kind of proprietary watermarking tech to track ads for some very specific purpose. My phone either can't lock onto it or can't read it.

I see them all the time. Here’s an example on drudgereport. https://imgur.com/a/hOl9x2m

I am using an iPhone 13 browsing via chrome. iOS 17.0

Also occurs in safari

What happens if you take a photo of the ad? Does it takes you to the website?

drive by exploits

reminds me a little bit of snackdata.com

willing to bet that 99.999% uptime is just static text, because 5+ hours out of 2190 hours is not 99.999%

From @koopajah on discord: "We don't really drop nines if one specific feature is having issues". Pretty convenient payment processing is just a "feature" of a payment infrastructure SaaS

This is a bullshit and untenable position. This “one specific feature” takes out the core feature. Shameful, deceitful and reputation tarnishing position.

To be fair, it only takes out the core feature for people using Stripe Tax, which is apparently a small fraction of customers.

In a OKR culture, the way to make your KR good is to add lots of useless and very simple microservices, which are always up, so the overall metric is 100%.

If your KRs are the uptimes of your simple microservices, you're not in an OKR culture.

I guess 99.999% uptime is no longer an engineer's well-earned badge of honor at Stripe. Now it's just sales puffery, like a LOWEST PRICES IN THE CITY!! sign at a discount store.

Sorry, but true class isn't just elegant rectangles decorated by various subtle shades of gray sans serif.

Hate it when companies do it. It should be the min of the availabilities of your APIs.

a.k.a. "my probed availability ignores user journeys that are actually an important part of my product"

the service doesn’t look to be down for everyone.

if their status is a percentage of requests, then a relatively small number of 500s compared to a big total volume will be tiny, even if ongoing.

Stripe has only existed for 2190 hours? /s

It's disingenuous to report "partial degradation" as "uptime" when some customers are unable to process any payments.

Yes, you either need to have a per-customer uptime number (that is visible to those customers) or you have one unified uptime number that takes a hit if any customers experience downtime. You can't have it both ways.

Why can't you maintain and report an average uptime across all service usage? So if you have an outage that affects 1% of traffic it moves your figure 1/10th as one on 10% of traffic?

That's what I'd expect a reported number to be, since that's what a client experiences on average.