Nostr Web Client

Replying to

Gossip Client

Gossip Release 0.11.0

=====================

Gossip is a nostr client for desktop.

Gossip is open sourced at https://github.com/mikedilger/gossip

This release adds the following major features:

- SECURE DIRECT MESSAGING: NIP-17 DMs (with NIP-44 encryption and NIP-59

Giftwrap) is fully supported, usable only if both parties have published

their DM relays in a kind 10050 event. You will get a pending item reminding

you to setup your DM relays if you haven't yet. Relays now have DM switches.

- LOAD MORE: now loads a fixed count of events, instead of a time period (which

may have been empty or may have been massive).

- ANNOTATIONS: You may now annotate your messages. If you make a typo, your

annotation (technically a reply event) will render inside the original message

in gossip (but will render as a reply in other clients).

Fixes you may notice:

- Fixed around list synchronization

- Fixes around the tagging popup UI/UX

- Improvements in loading thread ancestors, including better feedback

- Nip46 approvals now persist

- Nip46 compatibility improvements

- An event ordering issue was fixed

Additionally:

- Support for wgpu renderer, and new command to set renderer: wgpu_renderer

- Option to render feed in reverse (with newest at the bottom)

- Improved local storage performance

- Fixes around switching feeds and refreshing

- Vertical scroll bar on relay options

- fixed deleting lists

- Thai font is now also supported in the 'lang-cjk' feature

- Blacklisted relay.nostr.band and filter.nostr.wine relay URLs with proliferating path issues

- k tag added to deletion events

- When querying events, we also query their possible deletion events

- Avoid accidently asking for DMs because some relays reject that subscription

- Avoid repeated AUTHs to broken relays that keep asking

- Improvements around which relays we post to

- Improvements about relay connections

- New commands: export_encrypted_key, import_encrypted_private_key

- UI/UX updates to notifications

- Setting for custom mouse acceleration

- Allow DPI setting up to 400

- UI/UX improvements to widgets and styles

- Updates to dependencies

- Render unknown event kinds better

- Lots more, see changelog-0.11.0.txt for all commit messages

942dedfcd569da996bfe341da8462a3d8e04d7264043099f1c9d94ee70e359cd changelog-0.11.0.txt

e1e6149e34b95de289a08cdedda32d9b1b44544a4925d6e23980489603d772cf filter.rhai.example

06cbe484d71a43095a419893275f60dff0bed52d3f6d37a0231484b1a721d018 gossip_0.11.0-1_amd64.deb

3fd96033c78f6edf272487a8bf694fc10d24004ce9c8c5ef105ad2827f511a48 gossip-0.11.0-Darwin-arm64.dmg

b9db8c5dd5758b5170e3d888eb36373df5379acd1988e20b479b2f9fa3a132cc gossip-0.11.0-Darwin-x86_64.dmg

cc9e0f9d033e1944b7fb24eb3c991fb4807fda112980f1f5eb4b8dd166002f77 gossip.0.11.0.flatpak

9d12dd45422e7ebaaa4950ffcf23a0e8cb0adf87afa371baaee22028ae4a813d gossip.0.11.0.msi

d667f2619e445941e3d488aa04437fb678fd1b7c9882f1815182d1c827ab125b gossip-x86_64.AppImage.tar.gz

8a8543ebe0203fa8597bfcf70e7841f6fb66367358ff6180be692d4d724def70 LICENSE.txt

08c83136bfbe9151a8983fa09e4e5e54708b15992ac3080143c816b32f83a024 README.flatpak.txt

702bd583d106ed3d142f7cf92eb86a681fa93a7e46c3a1643773374694242bf2 README.macos.txt

916e2b47e5a3877629f95c989126e2af17c0d88f95786be30520640359934104 README.txt

5e3da4edc740244d454a36f7d77f38d100ba68eafab4ce9c529eda3b40a59121 README.upgrading.txt

Gossip Client 1y ago

When I (Mike Dilger) run gossip as myself on my main computer, it's great.

When I run it on other computers and under other accounts like I do when creating a release, I often find problems that I never normally encounter. Sometimes that happens after I've built the release!

There are a few problems I've noticed when doing this release, including

1. A panic in the pending actions system that makes that system crash (gossip keeps working though). Once gossip can load your kind 10050 event, this issue will disappear. But we will fix it.

2. Goddamn it runs slow on physical disks! Instead of processling about 500 events per second, it processes about 10 events per second. I may have to rethink how we do transactions so that we don't fsync so often.

3. Setting up initially with an encrypted private key, it seems to forget the private key (but remember the public key) and it has to be imported again.

4. Relay configs only sync the 10002 inbox/outbox swtiches, and we still have no way of syncing other relay settings across installs.

I'll try to put some effort into these issues and do a point release.

I'm also bogged down in refactoring how threads are handled, something that has been taking far more time than I expected. I put that aside for now.

Reply to this note

Please Login to reply.

Discussion

No replies yet.