wow... and phone number is required too

Anything you can do to improve the performance will be awesome but if its not possible to make it faster then I'll look into wrapping it up in a worker so it at least does not block the thread

Thank you for working on this. specifically making sure its optimized. I'm using social-social-graph in noStrudel to build and cache the users social graph. I was just looking into the code this morning to figure out if it was possible to make the de-serialize / recalculate methods faster so they don't freeze the app. (right now it freezes ~4s when loading a graph of 160k users)

are you signing up for classes or just trying to use an app?

Its BUD-05. If a user trusts a server they can IP-load to the /media endpoint and let the server modify and optimize the picture Then they can use the /mirror endpoint on other servers to copy the new blob to other servers

I like to save metadata on my photos because my personal photo cloud has a really cool map that shows where all the pictures where taken :)

I think it's already doing this in the background, but I probably should make it more obvious in the UI. Maybe something warning the user metadata was found and removed Also your default blossom server might be stripping metadata

I forgot I added that last update... I should put that more front and center when I redesign the profile page

Great breakdown of some clients and the various ways they try to show trust on users profiles

Finally finished all the features for NIP-17 messages in noStrudel and I think I've managed to create the most informative UI of any nostr client, it literally tells the user everything that is happening. although it looks pretty ugly. Next will be to cleanup some stuff and fix any bugs, then release and hope it never has to be worked on again The first flow is using manual decryption and auth The second flow is using automatic decryption and auth

Glad your maintaining your own blossom server. It's better if there are lots of implementations