cabalos

Not just each failed attempt, but every transaction. Previously, Radar only checked the card on a subscription at first use. It will now check every transaction unless you opt-out. So not only do you have to opt-out of Radar Standard, you also have to opt-out of having every subscription transaction run through Radar.

Between this and the Invoice feature cost increase a couple years back, Stripe now has a track record of being disingenuous when it comes to pricing. If they need more money to run the feature, just increase the cost per transaction and tell everyone why. Don't try to backdoor it with weird opt-out patterns.

My understanding is if you opt-out and move to the Lite plan you get AI powered protection nonsense but lose access to the default block rule "if payment matches one or more values in default Stripe block lists". That makes zero sense and should be the other way around.

Edit: support is saying the default rules will continue to work under the Lite plan. This is at odds with the language on their pricing page and email. At best it's an oversight, at worst it's an attempt to make Standard seem like the successor in features when it isn't.

Also, good luck sending in a PR and getting it merged. Unless you are part of Matt’s inner circle, it isn’t happening. Even the most basic bug fix PRs are routinely ignored.

Development has dropped off a cliff over the last couple of months. The release cycle has moved from quarterly to yearly. He's basically taking his ball and going home. My guess is we'll see more internal initiatives like this AI builder instead of focusing on the core product.

This would be an okay strategy if his core product wasn't in such a state of disrepair. I've seen multiple issues on Github projects from Automattic developers saying "this would be easy to fix upstream but we're not allow to fix anything in WordPress right now." It's pathetic and actively harming his own business.

Diamond Salt is still made this way north of Detroit. Almost all restaurant salt in the United States is sourced here.

Not only this, but a user who understands how to switch their default search to Google is likely not being fooled into clicking on search ads anyways.

Element visibility should not be triggered via focus or hover. Visibility states should be triggered with a button click or enter key press.

Someone has been running a massive fake DMCA notice bot targeting website contact forms with links to Google Cloud Storage files for the last year. I wonder if this is in response to this ongoing campaign?

I could see that. The reason I think it could be more extreme is the AppStore. I don’t have stats to back this up, but I would assume they make far more money from the iOS/iPadOs AppStore than Mac AppStore. It never truly caught on with the Mac, likely due to the long history of loading your own apps. Apple would love nothing more than to break this cycle.

I have a theory that they’re not actually intending to make it more touch friendly but rather they are trying to unify the interfaces between MacOS and iPadOS for when iPadOS supersedes MacOS. Slowly boiling the frog, so you don’t notice when they move iPadOS to the desktop.

Agreed. I think the long term strategy is to continue to iterate on iPadOS until it's close to feature parity with macOS and then drop macOS. It may take a decade or longer. Instead of rethinking the desktop UI to fit touch interactions, they're rethinking the touch UI to fit pointer interactions. The last major hurdle to clear is windowing, which you can see small steps towards in iPadOS 15.

I don't think people give enough credit to iPadOS's adaptive pointer. It's a complete rethinking of what a mouse should be in the context of current tech. It's a pointer that can adapt its resolution in different contexts. For UI's that do not need high resolution accuracy, it's much faster to target and click elements.

Agreed. This is going to be my exact use case for Universal Control.

My instances have stayed up but I am having problems with API calls. If your instance is down, I wonder if it's isolated to CloudSQL Proxy connections. Seems like this could be an issue at the API level.

A few years back, I stumbled on the master transit plan for the Metro Detroit region prior to the freeway system being built. The original plan called for rail running in the median of the freeways, similar to how spots are in Chicago. The plan included artist concepts, layouts, etc. Not sure if its true or not, but I had read reports the auto industry fought the rail component of the project to its death.

It was a really fascinating document. It's somewhere on the internet; I wish I could find the link.

I think this is credit card company policy and not specifically Stripe. IIRC, there is some language regarding using your own credit card because it could potentially be used to give yourself a loan. Credit cards have a much higher APR and lower limits for a cash advance. Processing your own cards could be used as an avoidance.

You're right; regardless of which model you pick, one side is going to be affected more. I'm sure you ran the math on it and saw Stripe customers skewed closer to the $10/mo sub than the $1,000/mo sub.

In the survey, there were a lot of options for dual pricing models. It must have been something you were considering. I'd be curious to hear why this was decided against?

To be honest, none of the new Billing features are relevant to us. We'd much rather have new features gated, like customer portal is, than paying 0.5% for features we never intend to use.

You're welcome; appreciate the response. For what its worth, I have yet to get an email about the increase and HN is the first I've heard of it.

I should have known something was up when Stripe sent out the email survey two days ago about subscription pricing. Very strange that you only sat on those results for a day before pulling the trigger on this. Interestingly, some of the survey answers included concepts of a free tier.

To me, the percentage makes little sense. You could be running 1,000,000 $10/mo subs, or 1,000 $1,000/mo subs and the cost is the same. This pricing model hits high value subscription companies significantly harder, even though Stripe's costs are lower.

I feel that spinning this as a several-year grace period is a bit disingenuous. I'm a huge Stripe fan, but this is leaving a bad taste in my mouth. Here's the exact notification that went out on April 6, 2018 in the dashboard:

"As a user of Stripe Subscriptions, you will get all the functionality of Stripe Billing's starter plan with no change in price. You can continue using it free of charge on your existing Stripe pricing, even beyond the $1M free threshold. This will be automatically applied to your account. Contact support@stripe.come with any pricing questions"

As far as I can see, the Billing Starter plan has not changed and still applies. Not only that, it claims we get "all the functionality of Stripe Billing.." when this hasn't been the case for a few months. New features have been gated recently, ie. the new customer portal.

You have every right to change your pricing how you see fit. However, if this message was worded as it being a grace period, we would have taken steps two years ago to consider other tools or building something in-house.