AWS is pretty aggressive about banning senders with high bounce/report rates. I know from working in an industry where customers had terrible email systems
This looks pretty neat. When I used SES at a previous company we had to do a lot of stuff like bounce tracking and monitoring ourselves so I definitely see the value.
One recommendation would be to use have customers create an IAM role and use cross-account role assumption to access SES on their behalf. That way you don’t have to deal with handling long-lived credentials
I think iMessage is a great example of “Embrace, Extend”. Apple didn’t build a standalone chat app because everyone (in the US) was already using SMS on their phones and “hey if you happen to be SMSing another iPhone user you get these extra features”
I feel like “email is dead as a decentralized protocol” is paradoxically a meme among Gmail users. Counter-anecdote: I haven’t touched Gmail in years and I still send and receive email fine
“From a content discovery standpoint, I’m really interested in how we can seed conversations and seed experiences with really high-quality content — certainly, editorial publisher content”
I’ve been waiting so long for my mastodon conversations to be seeded with high quality editorial publisher content
> Also, Let's Encrypt security is a joke - they issued fake certificate without serious checking. Using unencrypted HTTP for confirmation is a vulnerability
They can’t use HTTPS if you don’t have a certificate yet
They’re probably thinking of shared hosting environments that don’t have the SQLite library for PHP installed. That seems like a concern you could raise about any database connector, though