## ⚠️Important notice for nostree
How's it going nostr! Recently I was working to standardize the format I started using in nostree, it
used lists with a new kind (30303). I thought it was a good idea to use a new kind, but finally discussing with the main court of nostr we
thought it was a better idea to use the kind 30001 that is currently used for categorized bookmarks, but extended to give it a bit more
flexibility. You can read the pr here: https://github.com/nostr-protocol/nips/pull/723 . This implies that
lists that were created using the old format must be updated to the new format, otherwise they will not be visible in the future. For this I
have released in parallel the nostree client updated to work with the new format, and with a utility to update your lists in a very easy way.
You can find it here: https://w3.do/B3Zu3bOA I have also prepared a short video to illustrate the list migration process.
https://nostr.build/av/e48a2930e3b46d79da556e55cbe8f595ffc6c502c948d8e91104ec2244ab8275.webm
For the moment I will not update the client in production on nostree.me , I
will make a couple more announcements before that, so don't worry. Tentatively I will switch the client to the new format on the 29th and it will be accessible from the main domain. After that if you haven't updated your lists don't worry, you can still update them at any time.
This is a necessary change to improve the interoperability on nostr and to
respect the protocol as much as possible. From here on all steps will be in the right direction 💜
Please share 🙏
## ⚠️Important notice for nostree
How's it going nostr! Recently I was working to standardize the format I started using in nostree, it
used lists with a new kind (30303). I thought it was a good idea to use a new kind, but finally discussing with the main court of nostr we
thought it was a better idea to use the kind 30001 that is currently used for categorized bookmarks, but extended to give it a bit more
flexibility. You can read the pr here: https://github.com/nostr-protocol/nips/pull/723 . This implies that
lists that were created using the old format must be updated to the new format, otherwise they will not be visible in the future. For this I
have released in parallel the nostree client updated to work with the new format, and with a utility to update your lists in a very easy way.
You can find it here: https://w3.do/B3Zu3bOA I have also prepared a short video to illustrate the list migration process.
https://nostr.build/av/e48a2930e3b46d79da556e55cbe8f595ffc6c502c948d8e91104ec2244ab8275.webm
For the moment I will not update the client in production on nostree.me , I
will make a couple more announcements before that, so don't worry. Tentatively I will switch the client to the new format on the 29th and it will be accessible from the main domain. After that if you haven't updated your lists don't worry, you can still update them at any time.
This is a necessary change to improve the interoperability on nostr and to
respect the protocol as much as possible. From here on all steps will be in the right direction 💜
Please share 🙏
Been using https://design-v2.snort-social.pages.dev/ for the past few weeks. If anybody wants to try it out and give their 2 cents, please do.
Keep in mind it's still a WIP as usual
Looks nice! the only thing that catch my attention after use it for 10 mins its this line breaks in my about, and colors in the tabs
J Dilla - Donuts (Full Album)
Yep, concurrent connections are limited by your router, also ram and demand of i/o of the db
Sure, of course depends of the scale, but a domestic relay of course
;)
Good writing, and work, about current state of nostr dms
nostr:naddr1qq2nqemddce5g3rf0fp5jetnguk4qs6y949ykq3qjlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qxpqqqp65wq2h8da
We need more nostr clients not less.
https://thepeoplesvoice.tv/wef-orders-firefox-chrome-safari-to-start-blocking-blacklisted-websites/
Feels like this wants to put literally doors to the field. It would be funny if they weren't pure evil incarnate
It would also be good to try how to change relay set or address how ndk have gossip model