chandler

joined 2 days ago
[–] chandler@lemmy.world 1 points 8 hours ago

It was my mistake. The post should be updated now, but please let me know if you're still not seeing the link.

[–] chandler@lemmy.world 1 points 8 hours ago

You can certainly use SMTP in place of an email provider like SES or Resend, but I don't generally recommend it if you're concerned about deliverability and metrics.

[–] chandler@lemmy.world 2 points 8 hours ago* (last edited 8 hours ago)

I agree. Bad for SEO as well. I'd say that Discord chose us more than we chose it. That's where our initial users wanted to talk with us.

There's a link above the body, but I just added one to the body as well. Thanks for the note!

[–] chandler@lemmy.world 1 points 8 hours ago (2 children)

Mainly that it's self-hostable which makes it better for data security, lowers cost, and makes it extensible.

[–] chandler@lemmy.world 1 points 8 hours ago (4 children)

Hi apologies, could you clarify for me? Difference with reference to what?

[–] chandler@lemmy.world 2 points 8 hours ago (1 children)

Hi sorry, I didn't realize the previous image link replaced the github link. Just edited the post to fix that, but here it is as well: https://github.com/dittofeed/dittofeed

Thanks for brining to my attention!

 

Hi self-hosters, we're building a self-hostable, MIT-licensed alternative to Klaviyo, Braze, Mailchimp, etc. You can automate email, SMS, WhatsApp, and lots of other channels.

The core functionality of the platform includes a user segmentation builder, a low-code email template editor, and a low-code drag-and-drop journey builder for creating automated messaging workflows. We also have subscription groups to manage unsubscribes.

Link to repo: https://github.com/dittofeed/dittofeed

If you need any help with deploying an instance, reach out on Discord! https://discord.gg/HajPkCG4Mm