GOSSIP USERS on "master" branch:
I've just merged in a lot of unstable work. Here is an explanation of what changed:
Expect some data migrations.
PESON LISTS:
The main change is that you now have multiple curatable PersonLists which you can view as feeds. There is a new menu item "Person Lists" where you manage these. And under "Feeds" you can view any of these lists as a feed. "Followed" and "Muted" are now under this system ("My Notes" and "Inbox" are separate).
These PersonLists are all manually synchronized, just like your kind-3 Contact List (Followed) has always been, because other clients may clobber these. You have to publish them manually, and merge or overwrite changes found in nostr events manually.
You can manage who is on these lists from each person page too. Click an avatar and flip switches!
RELAY COMMS
Just this morning I improved gossip's communication with relays, retrying failed subscriptions when appropriate, waiting for AUTH, and handling CLOSED messages better. This code did not wait for the normal unstable testing, so if you notice any problems with it let me know.
TAGGING
This was already on master, but in case you hadn't noticed we finally fixed the horrid tagging UX. Now you type an @ and start typing a name, and you get a picker to choose from.
TLS
This was already on master. We changed how TLS works. By default it uses rust-based TLS code, but your operating system's native certificate store. This combination helps support relays that live on Tor .onion sites as you can now install .onion certificates locally. However, rust-based TLS code does not like self-signed CA certificates (technically they are not valid - you should instead make your own CA and then issue SSL certificates from it), so if you get "The Trust Settings Record was corrupted" you might want to use native TLS code instead by compiling with "--features=native-tls --no-default-features"
RELEASE
We have a few more things to do like renaming a person list, some bugs to fix, and polish, and then I hope to release a new version
Happy Sunday to those people still living in the weekend!
mikedilger /
npub1acg…p35c
2023-12-10 21:05:57
Author Public Key
npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35cPublished at
2023-12-10 21:05:57Event JSON
{
"id": "0ab35c02694c9e56047de9306d56eed592668c982574f6927c4cca2b56d0d7df",
"pubkey": "ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49",
"created_at": 1702238757,
"kind": 1,
"tags": [],
"content": "GOSSIP USERS on \"master\" branch:\n\nI've just merged in a lot of unstable work. Here is an explanation of what changed:\n\nExpect some data migrations.\n\nPESON LISTS:\n\nThe main change is that you now have multiple curatable PersonLists which you can view as feeds. There is a new menu item \"Person Lists\" where you manage these. And under \"Feeds\" you can view any of these lists as a feed. \"Followed\" and \"Muted\" are now under this system (\"My Notes\" and \"Inbox\" are separate).\n\nThese PersonLists are all manually synchronized, just like your kind-3 Contact List (Followed) has always been, because other clients may clobber these. You have to publish them manually, and merge or overwrite changes found in nostr events manually.\n\nYou can manage who is on these lists from each person page too. Click an avatar and flip switches!\n\nRELAY COMMS\n\nJust this morning I improved gossip's communication with relays, retrying failed subscriptions when appropriate, waiting for AUTH, and handling CLOSED messages better. This code did not wait for the normal unstable testing, so if you notice any problems with it let me know.\n\nTAGGING\n\nThis was already on master, but in case you hadn't noticed we finally fixed the horrid tagging UX. Now you type an @ and start typing a name, and you get a picker to choose from.\n\nTLS\n\nThis was already on master. We changed how TLS works. By default it uses rust-based TLS code, but your operating system's native certificate store. This combination helps support relays that live on Tor .onion sites as you can now install .onion certificates locally. However, rust-based TLS code does not like self-signed CA certificates (technically they are not valid - you should instead make your own CA and then issue SSL certificates from it), so if you get \"The Trust Settings Record was corrupted\" you might want to use native TLS code instead by compiling with \"--features=native-tls --no-default-features\"\n\nRELEASE\n\nWe have a few more things to do like renaming a person list, some bugs to fix, and polish, and then I hope to release a new version\n\n\nHappy Sunday to those people still living in the weekend!\n",
"sig": "55c24bc7616dfdacd48caf4674484ea5f1f756d929674774afc561974bd10b8b1abad63bf02a961b55e5c0ef071abd49e2bb586154dc4074b3fa227de18bdf50"
}