so when does it air?
the point of markdown is to `write` almost like plaintext to then be interpreted and re-rendered as proper html, not to be "readable" in plaintext, it is to be readable when you write it. it is not an improvement to plaintext and shouldn't be used to replace or enhance it. it's a poor man's html and belongs in it's own kind where the correct parser is to be used. plaintext is just that plain text, no special parser required.
it is possible but not advised as the nostr protocol is geared towards text, so sending images in base64 is very inneficient, and most relays have a per event size limit, it's better to use proper file formats and link to those instead, or, use torrents as it looks like a good way for nostr to handle files in a decentralised way
* long threads are = long posts are...
yes, that's better, but because a lot of clients try to mimic twitter, they're constrained by the layout that was optimised for character limits, so long threads are a bit of a pain there. slicing into chunks also allows for a more precise discussion as people can reply to just a small portion of the thread
just a thought looking at this, why not keep everything in the same event and have the public be in tags and private in encrypted content? would that simplify or complicate?
authentication for relays is coming soon but the way people do it now is only allow events from specific pubkeys, and you could also limit the access by ip or something so other people can't access it to make requests.
clients can have their own db. they're not "automatically" synced with relays. twitter is different because it's just one client with one harcoded relay, so they control the whole experience on what to serve, but if someone screenshots the tweet, twitter can only try to remove those images, but the content is out there for anyone to see.
nop, once a user receives a note from a relay, there's no asking it back. so if I subscribe to you via relay A, and I receive your note, then when you issue your "delete" event to relay A, I already have your note, and if I then ignore your delete event, there's nothing you and relay A can do and I can send it to relay B that won't delete anything.
once a note goes out to multiple relays, you don't know who is actively replicating those relays, so they'll get everything the relay gets. then, that other entity has all the notes and may never delete them, they can in fact, put up a website that displays "all the deleted content on nostr", therefore, deleting is wrongly worded, because it can never be truly deleted. we simply cannot know, hence, thinking that it was indeed deleted is false assurance and is sure to come bite someone later on. it should be seen more as do_not_serve_this_please, but expect it to still appear somewhere.
yes, but only posts you interact and to relays that did not sent you the event, so we don't overpush stuff to relays unnecesarily, but I think this will be key to posts spreading. at the same time, clients need to be conscious about their users and ask first, because some people may not want to spread other peoples notes to different relays (think private relays)
I'm planning on supporting.. still unclear yet when as I don't see it as a priority. It is kind of supported already if you turn on the 40's kinds and treat them as kind1, but the current layout is not really suited for it, huge threads
alphaama adds the relays that sent the event to an array, so when it builds the reply it just fetches `seen[0]`, so it's the first that returned it.. when adding to kind-3, it's manual, so you manually choose which relay and petname you add to the tag when using the `--f` command
yes, that shouldn't happen, but they're not invalid in tags.
a "nost" is a new type of "post". a note post, nost.