Could you include some screenshots in the README of the functionalities? that would go a long way! thank you in advance!

• aetherspawn

  yesterday at 11:10 PM

  Yeah GitHub repos need screenshots.

  • ttul

    yesterday at 11:51 PM

    Just have Codex or whatever take the screenshots and post them to the repo. Easy peasy.

    • brazukadev

      today at 12:46 AM

      it is more efficient to prompt the meat proxy

I get the temptation to self-host your support platform, as the existing tooling out there can be quite expensive when you want to upgrade from just using an email inbox.

If any founders find themselves reading this, and don't think it's the best idea to self-host your own support infra, I've just spent the last 6+ months building stayupfront.com which has, I think, quite reasonable pricing, and a few more features than this... largely around the customer's portal experience (changelog, roadmap, etc.) and includes monitoring & incident management which I think should all be ran from the same surface.

I've only just soft-launched, so still have founding pricing on there. Would certainly love to speak to others in this space too, as I was surprised how neglected an area it seemed to be when I was trying to find a replacement for jira service desk for a company I was working with at the beginning of this year.

I built something similar, but for in-app Issue Reporting, as my macOS app needed a way for users to file bugs without having to create an issue in GitHub https://github.com/kushalpandya/Sluice

Just used a very similar stack to make my own mail client. Workers for routing, Resend for sending, uses a CF and Resend key to set up any inbox on any domain I want ~instantly so I can have inboxes for everything. Very cool, I think workers are underrated!

• aetherspawn

  yesterday at 11:11 PM

  You don’t need resend anymore, email is CF native.

It may be very nice, but with no screenshots and no demo site you're going to have trouble getting people to try it out.

Can it kill Jira? That’s all I ask :(

• ngram

  today at 2:27 AM

  For what specific use case would you like to kill Jira?

nice stack. one question from someone who just built one of these: how do you handle inbound email threading? in my case the provider (SES) rewrites the Message-ID in transit, so In-Reply-To/References matching silently breaks. I ended up putting the ticket id in a plus address on the Reply-To, the envelope survives even when the headers don't. also curious how you handle webhook redeliveries, for me duplicates turned out to be the normal case, not the rare one.

• ttoinou

  today at 3:39 AM

  Yeah Im sure threading detection must break at least 30% of the time