Hence my response:
> Aliases are fair game .. for organization for just hiding your own email to limit tracking.. that's fair .. but bad, known disposable email generally just costs too much and is too risky for businesses.
Aliases are fair game .. for organization for just hiding your own email to limit tracking.. that's fair .. but bad, known disposable email generally just costs too much and is too risky for businesses.
IDK man .. many services really just don't even want to deal with a sign up they are never going to reach. By using a disposable email, you're telling the business, I want to use your service, get value, but I don't really want you to reach me. To them, it sounds like a loss loss situation. Business are there to make money, and they offer a signup/trial/free account so they can give you access in exchange for being able to reach you.
But I do sympathize with the stupidity of marketing email madness.
Rupt started as an account sharing prevention project. Customers kept telling us we need this feature, we need that feature and we kept adding them.
Turns out they were asking for a trust and safety platform. One platform to handle the intelligence, the rules engine, and the enforcement in one place.
Introducing Rupt3 the platform to tell you which users and actions to trust and which ones not to. With an AI agent that monitors the rules 24/7!
I'd love feedback from people who want to enforce policies against abuse and fraud. Thank you!
are you using it to write code? $20/mo was never enough and I'm not even full time on coding .. yeah different models are worth experimenting .. but I'm okay with paying higher for the best model .. just need predictability and stability of pricing, which Claude doesn't give, and yet we still use and pay for .. because it's such a good product.
I'm only entered T&S space recently (compared to you), but since I entered it, it was never separated from security. It was mostly product security and user trust and safety as one function. I suspect they will also need shared tools, which is why I built my current product.
When you build something people REALLY want, you can pull of ridiculous stunts like Claude's pricing:
- Vague limits
- Weekly/monthly usage stats ??
- 50% of your usage on Fable 5
- $200/mo subscription that doesn't include Fable 5
- But you can use it with "usage credits"
That's a good guess .. but I bet they are also paying price for this in support costs .. I'd be curious what percentage of their support tickets are related to this (also the require you to cancel subscription, create a new account, create a new subscription if you want to change a pro account)
You cannot change your google email itself .. because there's no other reference to identify you with them. But you can use your email as the "inbox" for all other services. OpenAI doesn't have an "inbox" .. they accept other "inboxes" so they should allow you to change it.
According to Gemini, it's because OpenAI uses the email as the unique identifier of the user. But if that were the case, it's probably an week's project for a single engineer at most. I thought there was a better reason for this like some security measure for such a fast growing company, it never occurred to me that the reason could be so simple
We send & receive a lot of emails internally. One of the first things we have to do in every project is build sending & receiving emails. So this is open source and reusable so that every new project can use it.
Please try it out, give feedback and contribute.
Next:
- Templated emails (AWS only)
- Simple editor (God knows we had to do it more than a few times) & AWS sucks at it.