They will, and you’re about to get a very enjoyable AWS bill each month. Definitely my favorite bill to pay. SES is my only regular usage of AWS as well.
They will, and you’re about to get a very enjoyable AWS bill each month. Definitely my favorite bill to pay. SES is my only regular usage of AWS as well.
UUIDv7, communicated as a base-58 encoded string with a prefix like user_…. All the benefits of UUID as a means of storage, compact, URL-safe, and makes the record type identifiable by its ID. v7 because encoding the creation time is also cool.
So maybe try it. Go exclusive here for a month. Pick an engagement metric that matters to you, and check in on your qualitative feelings too. I bet you won’t miss it.
Unpublished because I don’t want to be responsible for someone else’s auth without a thorough review by someone who knows the pitfalls. But the premise is pretty simple: what if you could have phx.gen.auth, with more features, in a library that is meant to be gradually replaced as your product grows
Spent a lot of time and careful thought on github.com/aj-foster/id... and still missed the mark on some things, but the guide+ideas about Progressive Replacement is something I think any identity solution needs. If there’s anything to be proud of in there, that’s probably it.
Wish I could do more.
You might want to check out this action maintained by the Erlang Ecosystem Foundation: github.com/erlef/setup-...