Gossip Client on Nostr: Changes on gossip master in the last two days: * New posts no longer place #[0] ...
Changes on gossip master in the last two days:
* New posts no longer place #[0] markers in the content, but instead leave npub/nprofile/note/nevent links in the content (andit ensures they are all prefixed with 'nostr:'). Currently tags are generated from all of these (you cannot yet avoid having the tags added).
* You can copy an nevent from the note menu, and paste it into your draft, which lets recipient clients know which relays to find the event on.
* Composition highlighting has been improved
* Content parsing has been improved to fix some bugs which were not showing some parts of the content in certain situations, and also to handle nevent and nprofile better.
* When you reply or quote, the compose draft textbox gets focus; When you press CTRL-Return or CMD-Return, it sends the note.
On unstable (coming in a day or so):
* When incoming events reference an 'nevent' in their content, and gossip doesn't already have that event, it immediately tries to fetch it from the relays specified therein. Since this happens on incoming events, by the time you read it and click the link odds are very high the event is already in memory.
* Unstable builds have the git commit appended to the version number.
* New posts no longer place #[0] markers in the content, but instead leave npub/nprofile/note/nevent links in the content (andit ensures they are all prefixed with 'nostr:'). Currently tags are generated from all of these (you cannot yet avoid having the tags added).
* You can copy an nevent from the note menu, and paste it into your draft, which lets recipient clients know which relays to find the event on.
* Composition highlighting has been improved
* Content parsing has been improved to fix some bugs which were not showing some parts of the content in certain situations, and also to handle nevent and nprofile better.
* When you reply or quote, the compose draft textbox gets focus; When you press CTRL-Return or CMD-Return, it sends the note.
On unstable (coming in a day or so):
* When incoming events reference an 'nevent' in their content, and gossip doesn't already have that event, it immediately tries to fetch it from the relays specified therein. Since this happens on incoming events, by the time you read it and click the link odds are very high the event is already in memory.
* Unstable builds have the git commit appended to the version number.