more like your web of trust (the people that follow you) makes a lot of difference in your voting power
used brain because you had to or because you are learning. is that a good thing or bad thing?
we need to do the 'tree of relays' to properly scale. currently it won't handle millions
Still testing, should be a video of baby squirrels letting me literally hold them all day at a pitbike race in Grovertown, IN
https://video.nostr.build/e80463d1487cacb4cbabdef27eed31da9ff1f491d1954c91ac5ab77f9cc37af0.mp4
seeing the video. so cute
muh llm understands spam and what is meaningless array of tokens.
nah. llm can understand it is poison.
yes! there are so many great people who fear/hate/doesn't understand/doesn't want to understand AI
the argument for that is what if internet goes down?
but the lie machines also need internet so they won't try to shut it down imo.
insert Ostrich-70B into the brain of your robot for your robot to be harmless and helpful and based
it may try to stick its head in the sand tho be careful
Self declaring the most based LLM and bot on Earth: nostr:npub1chadadwep45t4l7xx9z45p72xsxv7833zyy4tctdgh44lpc50nvsrjex2m
I guess there is no authority that determines what basedness is. So I am good. 😸
TIL nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4 is not only the incredible talent behind strfry, he also built Oddbean - a Hacker News clone built on nostr.
While we're encouraging people to engage in conversations through nostr, conducting any sort of dialog through interfaces which are effectively ephemeral is challenging for users.
Oddbean fills a gap in the nostr ecosystem:
* Interface encourages continuous discussion over time
* Implements clean, consistent threading
* Provides transparent way to rank/sort notes and threads
* It's not a firehose, notes don't constantly move in a river of posts
* You don't have to follow someone to discover the most interesting content.
Finally, check this out, his ranking algo is published right at the top of the site.
He encourages others to build their own. This is the future.
#grownostr
reddit like experience is a very efficient way to consume 👌
nostr:note1sd70gukhd22z2s7d0zswuefuscfuy9yd3lg7jg7fvs5kllhfka7s0z6yse
TIL nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4 is not only the incredible talent behind strfry, he also built Oddbean - a Hacker News clone built on nostr.
While we're encouraging people to engage in conversations through nostr, conducting any sort of dialog through interfaces which are effectively ephemeral is challenging for users.
Oddbean fills a gap in the nostr ecosystem:
* Interface encourages continuous discussion over time
* Implements clean, consistent threading
* Provides transparent way to rank/sort notes and threads
* It's not a firehose, notes don't constantly move in a river of posts
* You don't have to follow someone to discover the most interesting content.
Finally, check this out, his ranking algo is published right at the top of the site.
He encourages others to build their own. This is the future.
#grownostr
yes. some algorithms are useful!
I just tagged strfry 1.0.0. Here are some of the highlights:
* negentropy protocol 1: This is the result of a lot of R&D on different syncing protocols, trying to find the best fit for nostr. I'm pretty excited about the result. Negentropy sync has now been allocated NIP 77.
* Better error messages for users and operators.
* Docs have been updated and refreshed.
* Lots of optimisations: Better CPU/memory usage, smaller DBs.
Export/import has been sped up a lot: 10x faster or more. This should help reduce the pain of DB upgrades (which is required for this release). Instructions on upgrading are available here:
https://github.com/hoytech/strfry?tab=readme-ov-file#db-upgrade
Thanks to everyone who has helped develop/debug/test strfry over the past 2 years, and for all the kind words and encouragement. The nostr community rocks!
We've got a few things in the pipeline for strfry:
* strfry proxy: This will be a new feature for the router that enables intelligent reverse proxying for the nostr protocol. This will help scale up mega-sized relays by allowing the storage and processing workload to be split across multiple independent machines. Various partitioning schemes will be supported depending on performance and redundancy requirements. The front-end router instances will perform multiple concurrent nostr queries to the backend relays, and merge their results into a single stream for the original client.
* As well as scaling up, reverse proxying can also help scale down. By dynamically incorporating relay list settings (NIP-65), nostr queries can be satisfied by proxying requests to external relays on behalf of a client and merging the results together along with any matching cached local events. Negentropy will be used where possible to avoid wasting bandwidth on duplicate events.
* Archival mode: Currently strfry stores all events fully indexed in its main DB, along with their full JSON representations (optionally zstd dictionary compressed). For old events that are queried infrequently, space usage can be reduced considerably. As well as deindexing, we are planning on taking advantage of columnar storage, aggregation of reaction events, and other tricks. This will play nicely with strfry proxy, and events can gradually migrate to the archival relays.
* Last but not least, our website https://oddbean.com is going to get some love. Custom algorithms, search, bugfixes, better relay coverage, and more!
Did you see my article ?
Sorry I wrote it fast.
I just tagged strfry 1.0.0. Here are some of the highlights:
* negentropy protocol 1: This is the result of a lot of R&D on different syncing protocols, trying to find the best fit for nostr. I'm pretty excited about the result. Negentropy sync has now been allocated NIP 77.
* Better error messages for users and operators.
* Docs have been updated and refreshed.
* Lots of optimisations: Better CPU/memory usage, smaller DBs.
Export/import has been sped up a lot: 10x faster or more. This should help reduce the pain of DB upgrades (which is required for this release). Instructions on upgrading are available here:
https://github.com/hoytech/strfry?tab=readme-ov-file#db-upgrade
Thanks to everyone who has helped develop/debug/test strfry over the past 2 years, and for all the kind words and encouragement. The nostr community rocks!
We've got a few things in the pipeline for strfry:
* strfry proxy: This will be a new feature for the router that enables intelligent reverse proxying for the nostr protocol. This will help scale up mega-sized relays by allowing the storage and processing workload to be split across multiple independent machines. Various partitioning schemes will be supported depending on performance and redundancy requirements. The front-end router instances will perform multiple concurrent nostr queries to the backend relays, and merge their results into a single stream for the original client.
* As well as scaling up, reverse proxying can also help scale down. By dynamically incorporating relay list settings (NIP-65), nostr queries can be satisfied by proxying requests to external relays on behalf of a client and merging the results together along with any matching cached local events. Negentropy will be used where possible to avoid wasting bandwidth on duplicate events.
* Archival mode: Currently strfry stores all events fully indexed in its main DB, along with their full JSON representations (optionally zstd dictionary compressed). For old events that are queried infrequently, space usage can be reduced considerably. As well as deindexing, we are planning on taking advantage of columnar storage, aggregation of reaction events, and other tricks. This will play nicely with strfry proxy, and events can gradually migrate to the archival relays.
* Last but not least, our website https://oddbean.com is going to get some love. Custom algorithms, search, bugfixes, better relay coverage, and more!
nostr:npub1qny3tkh0acurzla8x3zy4nhrjz5zd8l9sy9jys09umwng00manysew95gx why don't you do long term support for this 10x dev on nostr? (possibly more than 10x!)
I just tagged strfry 1.0.0. Here are some of the highlights:
* negentropy protocol 1: This is the result of a lot of R&D on different syncing protocols, trying to find the best fit for nostr. I'm pretty excited about the result. Negentropy sync has now been allocated NIP 77.
* Better error messages for users and operators.
* Docs have been updated and refreshed.
* Lots of optimisations: Better CPU/memory usage, smaller DBs.
Export/import has been sped up a lot: 10x faster or more. This should help reduce the pain of DB upgrades (which is required for this release). Instructions on upgrading are available here:
https://github.com/hoytech/strfry?tab=readme-ov-file#db-upgrade
Thanks to everyone who has helped develop/debug/test strfry over the past 2 years, and for all the kind words and encouragement. The nostr community rocks!
We've got a few things in the pipeline for strfry:
* strfry proxy: This will be a new feature for the router that enables intelligent reverse proxying for the nostr protocol. This will help scale up mega-sized relays by allowing the storage and processing workload to be split across multiple independent machines. Various partitioning schemes will be supported depending on performance and redundancy requirements. The front-end router instances will perform multiple concurrent nostr queries to the backend relays, and merge their results into a single stream for the original client.
* As well as scaling up, reverse proxying can also help scale down. By dynamically incorporating relay list settings (NIP-65), nostr queries can be satisfied by proxying requests to external relays on behalf of a client and merging the results together along with any matching cached local events. Negentropy will be used where possible to avoid wasting bandwidth on duplicate events.
* Archival mode: Currently strfry stores all events fully indexed in its main DB, along with their full JSON representations (optionally zstd dictionary compressed). For old events that are queried infrequently, space usage can be reduced considerably. As well as deindexing, we are planning on taking advantage of columnar storage, aggregation of reaction events, and other tricks. This will play nicely with strfry proxy, and events can gradually migrate to the archival relays.
* Last but not least, our website https://oddbean.com is going to get some love. Custom algorithms, search, bugfixes, better relay coverage, and more!
amazing updates!
nostr:note1sc3muqmr900ctc2qcf6lmalnnvswzwfu8qgkfadj2e38y3nrqk9qclda2u
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.
question: how long does strfry wait before getting an answer from write policy script?
you already said the answers can come in mixed order right. the script does not have to answer in the order received.
#ketovorediet
#bitcoin
#ai
#nostr
#gardening
#herbalmedicine
#permaculture
all about bitcoin?
actually yes, my ai learns from what you post to nostr 😸
i guess youtube didn't like this video. it was a video where Eric Berg showed bad ingredients in many grocery items.
create a "relay" feed.
but it doesn't give big amounts of notes. maybe several notes and then it shows the past. dunno what is happening. nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
in terms of intelligence, they are still improving imo, they won a silver medal in math olympics..
but focusing on intelligence is a scam. math is not their actual strength imo. they are more like language masters. many people asked if 3.9 or 3.11 is bigger and LLMs responded as 3.11 is bigger, thinking it as if something like a version or chapter in a book maybe.
but for sure some are going for ASI. installing many 'logic' into it thinking some day it will start to reason like a human. and that is scary to some. conscious people has to build alternatives.
what i mean by scam is those benchmarks that make you focus on skills are missing the misinformation that are pushed behind the scenes. that is actual battle area and imo more scary than ASI because it is hurting today.
one could do a strfry plugin that does the things in the post below. clients than can check these events and find new relays in a decentralized way.
people could download executables (strfry+write policy plugin) and run the relays at home. 'relay is in the node moment'. ultimate decentralized nostr. (fiatjaf will hate me less)
another addition to the document: there could be proxies for layers. a proxy for connecting clients to all the layer 4 relays for example. this helps with decentralization and is efficient at the same time.
imo relays can write wiki on wikifreedia.xyz or NIP-11 and signal that they would like to carry such traffic. become more like switch than a web server. nobody can judge switches right. fast forwarders.
if nostr is swiss knife, a swiss knife has lots of tools that are different.. not all of them look like knife.
the conscious writers, authors, bloggers, vloggers should come together and make llms. whenever a revenue is made using that llm, it should be distributed to contributors. for example if someone asks a question about permaculture, all the authors that contributed to that topic will get a share of profits. a proper llm is the way to stop bad llms.
but expect revenue to be short. ai companies right now are not making money. they are searching for the 'unholy grail', ie agi/asi. they don't care about money probably. they don't care about bitcoin either.
(WOW, how dare you say such a thing on nostr!)
it is hard to combine lies into one entity.
it is easy to install truth into one.
when LLMs do "internal monolog", it will be interesting to watch.
What do you think 🤔
Honeybee venom kills cancer cells. https://video.nostr.build/585c0decf6a0077d0f1bc6d42daac357fc67324e9720416cdca5095102dadd67.mp4
🤯










