Marks & Clerk Opiniões 2

Service is not usable and support is not anwsering!

I have just spent the past week testing Clerk authentication on a project I am working on. The result is that I must stop using it as it is flawed in many ways and therefore not viable to use in a development or production environment.

Here is an example. The claim for complete user management is false. Even with a paid solution you do not get a unique username management therefore impossible for applications to allow for users to contribute with transparency of who wrote which post or comment etc. The clerkId is unique and perhaps you could remove username from Clerk user management which returns you back to application user management. As events are also handled behind webhooks user management and syncing although possible result in say username unresolvable uniqueness etc. All in all I see no use case where I could use Clerk which is very disappointing given the idea of Clerk being so promising. I am sure in the future Clerk will resolve unless it is just not technically possible. So for an alternative I was forced to return to next auth.