I've used it a couple of times in the past. It was too complex for my VC-backed startup, so I haven't adopted it for my one-person business.

Google conceived Kubernetes for running data center. If you're not running lots of different containers on lots of different machines, it's overkill. It solves problems like "Recovering from a host failure" and "Running background jobs on low-utilization CPUs" well, but those ultimately are problems of scale.

I assume that they think the domain is close to stripe.com and that it might be used for phishing. Also, it was purchased using an anonymized email address, which increases the suspicion level. So, I'm not surprised.

Also, it seems that they've just limited your ability to buy new domains - not outright disabled the account.

What were you planning to use the domain for? I think that getting your account reactivated involves emailing them and telling them that you had some legitimate use for the domain.

Thanks!

Some of the early use case for Booklet have been:

• Investors connecting their portfolio founders in a network
• A marketplace building a community of workers to engage them between gigs
• A Substack newsletter adding a subscriber community
• Companies replacing Google Groups for internal announcements

My goals is to basically move from hobbyist usage -> non-work communities -> core work tool.

Thanks for catching the broken link - just pushed a fix for it.

Check out Booklet, which is a modern email community. It’s my indie project, and I started it for the same reasons you highlight. Chat is noisy and people don’t pay attention. So, I build it on email - and use AI to make really good summaries and subject lines, so people can stay updates without staying logged in or getting tons of notifications. And, with email there’s nothing to install.

You might try posting to Hacker News, because more Stripe folks tend to hang out there.

Besides that, try looking for another payment processor. There are others out there - such as Braintree.

A couple I don't see here yet:

• Company of One
• The Artist's Way
• Small Giants
• Reality is Broken
• So Good They Can't Ignore You

Hmm, I'd be concerned about security. Can I give you access to commit messages, without giving you access to code?

I just set up Sendy based on this reco - thanks so much!

Another downside of Intercom is that their unsubscribe logic is basic, so if users unsubscribe from onboarding campaigns - then I think they will not receive broadcast emails.

While building MoonlightWork.com, we built an email digest that auto-sent every week. It read from different feeds - including a headwayapp.co feed, our blog, some internal APIs, and a "custom intro" feed. So, any announcements we included in that weekly email. It worked super well.

I do like HeadwayApp.co, but they don't handle email subscriptions. Perhaps there's an opportunity for a product like that, but with subscriptions?

For #postcard I'm just subscribing everybody to a postcard at updates.postcard.page. My goal is to build personal websites for people, but it's conceivable to update the product for an api-driven updates mailing list. If you're interested in this, I could definitely experiment with it.

No, I do the weekly email - I'll switch to daily.

The main point of a forum for me is non-realtime discussions. Replying via email is secondary for me.