Thanks to your comment, I think I have integrated now most of your suggestions!

MaViLab

Oh, I didn't notice that it's a editable text, the weak border confused me!
A list with dedicated add/remove button would be a better solution.

By the way, you should automatically retrieve and use my Blossom media server fetching kind:10063 (https://github.com/hzrd149/blossom/blob/master/buds/03.md).
Same for NIP-96, you have kind:10096.

So you should check the presence of these events and according set the default media server type, using the correct value (if both are present I would suggest using Blossom as default).

Woow .... This is a gold mine for me... Gonna come back later, to see what we can implement to improve UX further.... Thanks!

As for Blossom Server, users can already add their own under settings ;)

All'ultima request posso risponderti io: è la prima cosa che gli ho chiesto ed è già possibile farlo :)

isolabellart

Publishing to NIP-65 relays should be the default, why forcing the reccomanded?

Really important feature request: use user's Blossom server for uploads

nostr

Introducing Pidgeon, a privacy‑first Nostr scheduler

Very cool!

Some UX suggestions:

- Improve the onboarding showing a modal explaining what the service does
- Simply the interface moving the quick status on the top, in a more compact form
- When saving a draft, don't remove it from the composer, often the user just want to backup what is writing
- When a draft is used, completed and sent, remove it from the recent drafts (or at least propose it interactively)
- Disable buttons that have a not applicable action in that context, instead of returning a "nothing to do" message (e.g. saving a draft with an empty editor)
- Offer a light theme option
- Add the github repo to the page footer
- Add you npub to the page footer

Publishing to NIP-65 relays should be the default, why forcing the reccomanded?

Really important feature request: use user's Blossom server for uploads