@ChrisMakeSense I think perhaps using it directly instead of through the replit integration might be the solve for you here? If you make the app on clerk you can instruct replit to use your own apps credentials and then retain dashboard access this way
I'm working on a Clerk feature that would allow you to send emails - transactional + marketing campaigns, tied directly to your users.
It's gonna be a bit before we have something ready to use, but I would love to get some feedback on what would be most useful if interested!
@bolinfest Any chance that codex could be given the capability to update it's own thread title? Would be a game changer for me at least to be able to use the thread title as a status indicator π
For sure! Our goal is to reduce the pain of having to set up a bunch of different SaaS vendors and wire them all together when building an app. It sounds like you're on the same page here. Let me know if you have any other feedback or feel free to drop it in here: https://t.co/Jna0iWJxrY π
Ah ok, this is unfortunately an email/domain reputation issue that will self-resolve over time as you send more emails from your domain, wouldn't be fixed by different implementations. I wrote a bit more about this here in our docs: https://t.co/e5H0shNGC4
For the second comment, I'm not sure I understand what you mean here - you want to add them to the waitlist manually like, through the dashboard?
Iβve been a Hermes user from very early on. I have contributed as well. I am a big fan of what youβre doing. That being said, I do not think the way you engaged with Theo here was the right angle, it feels like you got defensive and antagonistic immediately when he has a valid point.
Donβt get me wrong, Theo also could have engaged and delivered this feedback more respectfully as well. But giving fair feedback but delivering it very aggressively is kind of theoβs brand I guess at this point, so itβs kind of to be expected from him, whereas I have watched your engagement for a while on twitter and expected a bit more from you.
Just a perspective from the sidelines. I think thereβs an easy solve here, which is making a more universal, basic set of skills that are likely to be used by everyone that install by default and leaving the rest to the users choice as part of the installer process π€·ββοΈ
@_ix_drew@clerk I went through our codebase to confirm this - there's no waiting period. If you're still getting this error, it means there was an issue with the deletion or another user with the same username slid in there somehow. Did this end up resolving for you or still an issue?
@theZachChen@clerk@supabase Clerk doesn't rely on AWS fwiw. We do have a huge free tier (up to 50k MAU) and a startup discount (https://t.co/aOTTnCx5qM) though that should get you a good ways along!