I haven’t seen any client that has a share as DM option.
Generally DMs on nostr are only semi-private right now. Nobody can read the message but metadata is leaked, I.e. the fact that a message has been sent (when / to whom) is public.
Better DM implementations are in the works.
Apple is cracking down on Patreon to extort their 30% fee (nothing new here). This goes to the point, that they won’t allow creators to delist their content on Apple devices:
https://m.primal.net/JxZg.jpg
Great! Have you thought about how to store an album reference? As a music playlist? I would still prefer to have an album field in the spec to have it self contained in one event.
@The Fishcake🐶🐾 It's a kind 1 comment on a badge award even (kind 30009, nip 58). Apps render it as normal post because it doesn't have an 'e' tag event reference.
https://m.primal.net/Jvtf.png
Good question, I have not built any UI yet. Currently I just have NDK with default settings, i.e. uses your default relays.
I think it makes sense to have a set of specifc (public) relays, but maybe even a separate set of private relays where metadata is published that should not be publicly visible.
Publish metadata public vs private
💯 ... and it's not only the information about clients. User profiles with recent posts should also be in the search indexes. This would help people randomly discovering nostr profiles (and apps) when searching on the web.
I tagged FishCake who is the developer of nostr.build ... I bet he will comment on your first question.
I am hopeful the video options will get better. Thank you for your curiosity and patience!
For text notes yes (they are decentralized on nostr), as the are stored on multiple relays and can be easily duplicated and spread.
For media (images / video) we are not there yet. I assume you uploaded to nostr.build so your content is only hosted with them. It is still be better than to rely solely on the corporate platforms.
It is not easily solved as there is always storage and bandwidth costs attached with media. Still, we are working on better storage options (e.g. the blossom protocol) to decentralize media as well.
I couldn’t find any mention of that in the spec. I would expect apps currently don’t carry forward the expiration for reposts.
Also note: expiration is optional, I.e. it SHOULD be considered but it is never a guarantee.
THIS! The main reason nip96 and blossom currently can't work together is that by nip96 a GET /<original SHA256> has to be used even when the content has been transformed.
Oddbean new post about login | logout
Notes by florian | export