Nostr Web Client

The problem is that it is hard to put a size limit after-facts, and the burden that heavy events could create is quite obvious.

This sort of possibility encourage developers to embed images instead of using NIP-96 or Blossom, because it is easier.

And a important and widely used client like Amethyst has a huge network effects in this respect, so with great power should come great responsibility.

I think it's bad supporting markdown in standard note for the same reason, in fact this violates NIP-01 that says:

> Content that must be parsed, such as Markdown and HTML, should not be used.

Please, consider this point of view.

Vitor Pamplona 1y ago

All relays already have size limits. That shouldn't be any problem. We already transmit NIP-95 and other very heavy binary events, like GiftWraps and NIP-04 DMs as well as 2000+ key follow lists, text files, blogs, spreadsheets and wikifreedia entries (5-10Kb for a good article). Relays and clients can reject on the size and that's their choice. But big events will always be there.

On the formatting, we just don't have the flexibility on the parser to decide what to parse per event kind. We just use one for everything. So, if people use markdown or ascii doc, like fiatjaf is requesting, we will have just one parser/renderer for all these types.

Reply to this note

Please Login to reply.

Discussion

daniele 1y ago

> All relays already have size limits. That shouldn't be any problem.

I am not talking about 10 KB non-image blobs. Considering that we have people with profile pictures of about 1MB, let's imagine that they start adding one or more pictures taken by a modern mobile phone (~3MB).

The relay limit is not an argument or a solution, because users cannot easily know if/what relays have rejected events, and especially for what reason, so they simply get a reduced (or none) visibility.

I definitely see problems, and frankly I don't see much real benefit.

Btw, this also violates the kind:01 spec.

> On the formatting, we just don't have the flexibility

Add it to fully adhere to NIP-01, please.

Vitor Pamplona 1y ago

Base64 images will be there regarless of our support or not. Many profiles have had base64 images on kind0 for over a year now.

If people are using and happy with the way base64 image works, they will keep using it, regarless of what the spec says. In that case the spec is wrong and must change.

Let's not forget that the beauty of Nostr is that people can do whatever they want. Clients and relays can choose to support or not the user's payload and Amethyst will always support what's being used, regarless if I think it's a good idea or not.