I hope Trump mentions Peanut the Squirrel. He needs to.
Peanut's murder is all the proof you need about Big Government being bad and why it needs to be scaled all the way back.
New York is full of rabies-ridden animals and rats all over the streets but their biggest concern was to abduct and murder an innocent squirrel and raccoon from a loving family in order to "test them for rabies."
Top early for production, right time to experiment
nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr I use all (webapp, android and ios). Mostly webapp on desktop.
Yes I saw slowness but now seems OK
Personally I like the most to have one set of accounts for every nostr service/site. A sort of Universal SSO
Never forget that if you want to achieve something big you must #fight
https://video.nostr.build/1189b9498656daca2a23e5bc0679b33f9c68290528b58ca6dd434fe9584e38e2.mp4
You convinced me to try It. Yes It have some advantages comparse to the existing Messengers. The architetture Is very close tò nostr tò the point that they should merge for the benefits of both projects
Elon spent 44 billions to be fast to save freespeech. Now with a fraction of that he could ensure long live to freespeech. He should just supporto NOSTR
I just tagged 2 strfry releases: 0.9.7 and 1.0.0-beta1
1.0.0-beta1 is a candidate release of strfry 1.0.0 -- help is needed testing!
The internal strfry DB version has been increased to 3, which means that you will need to rebuild your DBs to use this new version.
0.9.7 has some bugfixes and changes that accumulated in master, and has a "strfry export --fried" feature that can be used to create DB exports that can be rapidly imported by 1.0.0 series releases.
The full changelogs are available here: https://github.com/hoytech/strfry/blob/1f34794945cf380035822278c46070a9923129f3/CHANGES
Thank you to everyone who contributed and helps testing! If you need help or run into any issues, reply on nostr or stop by our telegram channel.
Updated from 0.9.6 to 0.9.7, export with --fried. Updated to 1.0.0-beta2 and imported with --fried. Everything worked perfectly and super fast.
wss://relay.piazza.today
Thanks a lot for making strfry
Had similar idea for my relay.piazza.today that is a bit too much open. But I don't know yet how to setup strfry for this. Any hint?
I got how decentralized social networking is just the tip of the iceberg for all NOSTR enable to get.
What I'm less convinced of is to tight NOSTR to bitcoin and not genericcally to all blockchains. What stop using any layer2 for micropayments other than someone willing to implement it?
I hope NOSTR will find the way to integrate with other blockchains too on top of bitcoin
npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q webapp is finally working properly after latest update. Great work
Jack Dorsey Backs Bitcoin And Nostr To Cut Censorship With Free Speech https://www.forbes.com/sites/digital-assets/2024/08/30/jack-dorsey-backs-bitcoin-and-nostr-to-cut-censorship-with-free-speech/
I agree with those statements.
I offer another view from a person that aspire to build his own instance/community. For me feature N° 1 is having already solved the network effect problem i.e. having already all NOSTR users on my instance.
Then I would like to shape all of those users into my ideal community. A community is made by creators and followers.
I would like to have the possibility to invite, according to my view, creators to appears has if they are local users of my instace/community (if they agree) and in turn share with them any contributions/zaps coming from the users using my instance to access NOSTR.
Creators may participate to many different instances and at the same time instances may have creators not necessarily bound to them.
I'm not sure if nostr:npub10qdp2fc9ta6vraczxrcs8prqnv69fru2k6s2dj48gqjcylulmtjsg9arpj communities works this way or are strictly limited to the users that choose to have @ditto.pub nip-05 handle
strfry on a VPS, wss://replay.piazza.today