But at what cost? Duplicating metatags in every kind 1? No thanks.

It's funny that people don't like NIP95 but are completely fine filling kind one with duplicated trash.

Reply to this note

Please Login to reply.

Discussion

When are image uploads reused ?

You can copy a NIP 94 nevent into a new kind one and reuse the meme with it's metatags. No need to upload again.

nip94 is not meant to be used as an image replacement as stated in the spec.

It's not a replacement, people can still post the url. It's a file attachment like you said.

FYI.

nostr.build will soon have the best archive of quality memes in the known Universe.

#nostr

But will the API work? I have been trying to upload content for 3 moths. It never works from Android.

Maybe ask chatgpt for some coding lessons.

Please stop messaging me ✌️

🤣🔥

Burn 🔥

chatGPT is at capacity right now

How long you giving it before it takes over....

your belongings sir.... 😂

The real elephant in the room is JSONs. Will and Peter Todd both mentioned how slow they are. We shouldn’t be afraid of changes that are self-evident evolution — even if some clients don’t follow suite.

It’s not like millions of people rely on #nostr like they do #bitcoin; we are still very early. Optimize while we can, before it’s too late (hardforking with millions of users is a no-go).

Yep. The worst and the best decision of the early days was to use a serialization framework as your semantic data model. Worst because literally nothing is optimized in Nostr. Best because it is the think that actually makes this easy for implementers.

If you could start from scratch, how would you do it without JSONs? Let’s have a thought experiment.

It's hard to say because I don't think other technologies could have come this far. I would have kept things in binary for the base signing protocol with a similar structure to what Verifiable Credentials use for serialization-independent signing (nquads and such). Then the actual transfer of information could happen in any protocol implementers want (JSON, JSON-LD, Protobuf, XML, turtle, etc). That would have freed up several concepts in the early days, but I am not sure it would have catch on like it did with Nostr.

Thanks for sharing. That sounds like a clever plan… ingenious to separate signing from serialization so all notes can use any format.

Ignoring clearly better routes like this for the sake of not fragmenting the space is foolish this early on. If there were millions of people using #Nostr, I’d agree that it is too late. That’s not the case though! We still have time before that happens.