David Barroso

> for the benefit of other users If there is any idea that doesn't introduce too much complexity or that requires changing the semantics of the link we are open...

There is no POST method, it's just a GET to BASE_URL/verify?ticket={ticket}

> It feels like a verifyEmail method could solve the problem? Maybe, if someone wants to implement a `POST /verify` that works similar to `GET /verify` but returns data instead...

I did some more research on this and the `POST /verify` solution doesn't work. To do a POST to the `/verify` endpoint you need to use a form but that...

For reference, here you can find a blog post about the solution: https://nhost.io/blog/protect-your-magic-links-from-email-clients and some example implementations: https://github.com/nhost/nhost/pull/2590

Automatic conversion between different formats is something we probably don't want to do but we could add a `?f=webp` or similar to request the output format.

We don't use sharp (wrong programming language :P) but it doesn't matter, the library we use is also built on top of libvips and has support for this. If someone...

Optimize would mean different things for different people so I think being explicit is the best path forward. Also, the backend has no access to browser information so it'd be...

Thanks for the feature request. I have just one question: > this is not a suitable solution for native apps Do you have any documentation about this? I am asking...

> Using native authentication? No, I was asking about your statement "this is not a suitable solution for native apps". We have users building native applications using nhost so I...