Subnostr

Basically, it gives the user the ability to decide which media provider to use in their preferred media client. This also implies a home server that the user has set up at home (as long as it is compatible with NIP96).

It helps to decentralize nostr, and also allows developers to forget about this (I have had to bother many developers to add nostrcheck.me to their app), with NIP96 they will only do the work one last time.

We will add and remove media providers as we do now with relays.

There are apps that do not want to add nostr.build, others do not want to add nostrcheck.me, this decision is up to the user, not the developers.

I see it as so important and necessary that I can't explain why it is not already being implemented everywhere

I am going to try to PR as many nostr clients as I can so that (if they accept it) they will have compatibility with NIP96.

(Sorry, I got a long answer)

captjack 🏴‍☠️✨💜 2y ago

sounds very interesting

after one year starting to understand importance of decentralized / distributed MEDIA server is if image load SLOW as backup

wanna POST image in 3 servers

1.local/global

2.nostrcheck.me

3.nostr.build

only one will load if one of service is down not sure if this thought right or wrong same can done with relay n text easy

soon will DEEP Dive into local install of nostrcheck.me and nostr.build (thank you again to BOTH) look deep into NIP96

Reply to this note

Please Login to reply.

Discussion

Quentin 2y ago

NIP96 allows you to do this. We haven't gotten to the point of discussing the specifics of simultaneous uploads (but it does allow it as it is now). Right now I'm trying to make it possible to at least choose the media provider from a user-managed list in all nostr clients (of course, if NIP96 is approved, it's only a draft at the moment).

More info:

https://github.com/nostr-protocol/nips/pull/547#issuecomment-1772301779

captjack 🏴‍☠️✨💜 2y ago

that will be important start !