Avatar
someone
9fec72d579baaa772af9e71e638b529215721ace6e0f8320725ecbf9f77f85b1

why does a dot appear next to RELAY menu like a notification?

muh llm understands spam and what is meaningless array of tokens.

looks like wot is working well

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. 😸

Replying to Avatar Ross

TIL nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4 is not only the incredible talent behind strfry, he also built Oddbean - a Hacker News clone built on nostr.

https://oddbean.com/

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.

https://oddbean.com/algo

He encourages others to build their own. This is the future.

#grownostr

reddit like experience is a very efficient way to consume 👌

nostr:note1sd70gukhd22z2s7d0zswuefuscfuy9yd3lg7jg7fvs5kllhfka7s0z6yse

Replying to Avatar Ross

TIL nostr:npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4 is not only the incredible talent behind strfry, he also built Oddbean - a Hacker News clone built on nostr.

https://oddbean.com/

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.

https://oddbean.com/algo

He encourages others to build their own. This is the future.

#grownostr

yes. some algorithms are useful!

Replying to 21823843...

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!

Replying to 21823843...

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!)

Replying to 21823843...

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

Replying to Avatar jimmysong

AI vs Bitcoin

The AI hype has been non-stop for the last 2 years ever since ChatGPT came out with its 3.0 chat. Since then, there's been an insane amount of investment into AI tech from every direction. There are hundreds of startups, every tech giant has been making investments and companies in between have been putting a lot of money toward it as well. It's not a small amount, either, as the AI hardware costs make Bitcoin mining look like discount bargains.

Yet after two years, what have we to show for it? Maybe some faster image editing on newer phones? Slightly faster answers to questions you would normally ask Google? Some productivity increase among junior programmers? The investment was enormous, as can clearly be seen in NVIDIA's growth, but the results are pretty underwhelming. As with any hyped technology, the possibilities have run past the actual use.

One of the supposed benefits of fiat money is that capital accumulation is unnecessary to create real value. You can build roads, for example, without having to save up for it. What this misses are many obvious drawbacks, but one of them is that there has to be someone that evaluates whether something will create value and create the money out of thin air to fund the project. This is not just inherently centralizing, but also deeply political.

For whatever reason, AI passed this political test and got the blessing of the money printers, which, to a company that sells, shovels like NVIDIA has been great news. But the drawback is that there's bound to be at least *some* that don't pan out. Maybe some segment of the economy can't use AI profitably, for example. Yet the powers that be, mostly Cantillionaires, have decided that this is worthwhile and have poured insane amounts of money into this bet.

But much like hyped tech of the past, it's looking more and more likely that there's little profit to be made here. Yes, there's some useful things that can be made, but the costs are simply too high right now to justify spending that much. It's a luxury item that mostp people simply don't need, and hence don't want to pay for. AI has become an expensive solution looking for costly problems to solve.

This was always my analysis with another hyped tech: blockchain. It never really made any sense as the cost was too high for what was really just a distributed, very redundant but hard to upgrade database. It, too, couldn't find costly problems to solve, with the exception of one. That, of course being Bitcoin.

What differentiates Bitcoin from AI is that people *need* Bitcoin. It's its own killer app. AI is not so popular that people will pay for what it costs right now. And that means that most of the investment will be wasted. Like most hyped things in a fiat economy, it's doomed to have significant malinvestment.

A lot of people complain about Bitcoin businesses and how hard it is to make them profitable. In a sense, I get it. You want more people to have steady jobs and so on. But in another sense, I think this is the market speaking. You're not going to get paid from Bitcoiners easily and there's no flood of printed money looking for a place to go. At least there won't be once fiat money has run its course. Building a profitable company is hard and so few meet that mark, especially in a new segment as AI has shown.

So in that way, I'm encouraged, because the companies that survive in Bitcoin will have something truly worthwhile. By contrast, the companies that survive in AI will probably be the ones that get subsidized the longest.

you are approaching this from the wrong side. they are going after ASI. in a super intelligence world money has little use or with highest productivity they can do more things than money...

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)

https://highlighter.com/a/naddr1qvzqqqr4gupzp8lvwt2hnw42wu40nec7vw949ys4wgdvums0svs8yhktl8mhlpd3qqxnzdejxqmnqde5xqeryvej5s385z

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.

Replying to Avatar calle

NWS works with and without encrypted transport. There are lots of different flavors to explore.

When used without encryption, the entry node must be run by the user themselves because public entry nodes would be able to listen in otherwise. Two options in those cases: run the entry node locally in tandem with your (unmodified) client, or skip the entry node and modify the client so that data is sent through nostr to the exit node directly (the client is the entry node).

When used with encryption, the entry node can also be public. If the encryption doesn't rely on certificate authorities, it just works. You have to make sure you're talking to the right person, but that problem is as old as computer science. For example, ssh will ask you to confirm the fingerprint of the server when you connect.

If the encryption is https and the certificate was issued for a normal domain, your browser will complain (do you trust this website?) and the user will have to say "let me pass, even if insecure". Without ugly hacks (issuing your own root cert for example), I don't know ways to circumvent this. Note that Tor services doen't support https and they don't have to since transport is always Sphinx-encrypted (even hidden from the entry node).

How do you make sure you're talking to the right server if you use https? Couldn't the entry node just send your traffic somewhete else? We can actually do something that is unique to Nostr here: the exit node can publish its own TLS certificate on nostr and sign it. That's right, you don't need an authority to do that for you if you remain within the NWS system. Clients can fetch the cert from nostr before talking to the entry node and verify against that cert.

Here is another cool part that we haven't talked about yet: the exit node can also be configured to reach the global Internet and not only a local service (we call this NWS v2). In those cases, NWS can be used a bit like a VPN. You can type "https google dot com" in your browser and your encrypted traffic would flow from your machine to the entry node, to the exit node, then to Google and back to you. on those cases, nobody complains about the certificate because everything is fine.

Exciting shit. Gm.

which kind(s) does it use?

no chairs. this is the way

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.