I just have to point out this little page of caveats: https://support.stripe.com/questions/payments-that-qualify-f...

Biggest thing for our company: "The payment must be submitted to Stripe by your customer via Stripe Checkout. This means that recurring charges are not eligible for Chargeback Protection"

Meaning this does not protect our B2C subscription company from any recurring charges which is a huge percentage of our charges if not all of them.

Also: "The dispute must be one of the following types of reason codes (as identified by the relevant Card Network) listed in Appendix 1 of the Terms of Service: Visa: 10.4 Other Fraud - Card Absent Environment Mastercard: 4837 No Cardholder Authorization Mastercard: 4840 Fraudulent Processing of Transactions Discover, Diners Club, JCB: UA01 Fraud Card Not Present Transaction American Express: FR2 Fraud Full Recourse Program American Express: FR4 Fraud Full Recourse Agreement American Express: F29 Fraudulent Transaction - Card Not Present American Express: 4534 Multiple Records of Charge (ROCs); Card Member denies participation in Charge American Express: 4540 Card Not Present; Card Member denies participation in Charge"

Many of our chargebacks fall outside of these chargeback reasons so it would likely not be worth it for us to use this feature, as I'm sure is the case for many other subscription based companies.

> The payment must be submitted to Stripe by your customer via Stripe Checkout. This means that recurring charges are not eligible for Chargeback Protection

What's going on here? I thought Checkout specifically supported setting up subscriptions:

https://stripe.com/docs/payments/checkout/migration#client-s...

If recurring charges are not covered that's fine I guess but I don't get what it has to do with Checkout.

You’re right that wasn’t very clear. If the subscription is started using Stripe Checkout and charged at sign up, the initial payment is protected by Chargeback Protection. Trials that are charged at a later time and future recurring payments are not protected. We want to broaden the scope of use cases for Chargeback Protection over time.

First thing I thought when I saw this was autonomous trucks. I think this could be a good way for them to ease into a position where they have enough trucks on the road so they can justify working toward autonomous shipping. Right now they are making huge savings in their warehouse with kiva, I'm sure they want to expand that to other parts of their operation.

Exactly what I was thinking. Basically it is just this connected to a drive shaft. http://hyperphysics.phy-astr.gsu.edu/hbase/magnetic/mothow.h...

Although yes "connected to the drive shaft" in a sense is how it works but there can be some great discussions of 3 phase motor design, torque demand motor control systems, power electronics, regenerative breaking... The list goes on and on

I could build something in there to make it a bit easier. What is your use case?

These are some pretty shit domain names hehe. Here is everything with fewer than 8 chars. Lorded.com seems promising though.

with open('domains.txt') as domains: for line in domains: if len(line) < 8: print line

befogs

cagily

dourer

drolly

gusted

livia

lorded

neglig

scrods

shirrs

soughs

tyroes

unmans

unsays

vilyui

You seem to be counting \0 as a char, or meant to find words less than 7 chars. Either way, there are just over 100 names available with 7 chars.

Probably counting \n as a character since Python is pretty good about never dealing with \0's.