Mommydommy is going to ruin America

Bro

Fat Zaps Only is the idea to always zap at least $1 nostr:nevent1qvzqqqqqqypzqprpljlvcnpnw3pejvkkhrc3y6wvmd7vjuad0fg2ud3dky66gaxaqydhwumn8ghj7emvv4shxmmwv96x7u3wv3jhvtmjv4kxz7gqyzwfgppcq8wkv9fl0vky88j6hjqrf2ry37juxraftetkckphjj7cxx83zny

I think one of Bitcoin's biggest problems is that people are so far in the future. People are trying to solve hypothetical problems instead of focusing on RIGHT NOW. nostr:nevent1qvzqqqqqqypzqprpljlvcnpnw3pejvkkhrc3y6wvmd7vjuad0fg2ud3dky66gaxaqydhwumn8ghj7emvv4shxmmwv96x7u3wv3jhvtmjv4kxz7gqypexda85yfgs8x8lpw8wcjklxt92elprvynwjmgqgsfhchqp0m8dv96n3wf

I feel like Bitcoin has tried for so long to solve marketing problems with technical solutions

Announcing: shakespeare gift cards shakespeare.diy

Absolutely if you had a file that's 228k tokens long and it used the "view file" tool.

Shakespeare on-chain wallet experiment: https://nostr-to-bitcoin.shakespeare.wtf/ Your Nostr identity is your Bitcoin wallet. You can send Bitcoin to any npub. No setup is required by either party. It "just works"

What platform are you using most? Desktop or phone?

8 x 4TB SSDs are about to power the most powerful Nostr relay the world has ever seen

Soon the biggest part of being a Nostr developer will not be coding. It will be reading NIPs, memorizing them, and creating new kinds.

It's an IQ bell curve meme

The handyman who fixed our fridge accepted Bitcoin, but no less than 1 bitcoin. It was either cash or 1 bitcoin, nothing in between.​

1. Use ChatGPT to write a book called "ChatGPT Millionaire" 2. Sell it for $13 a piece 3. Sell 76,924 copies 4. Be a ChatGPT Millionaire

Going to start being like those crazy YouTube survivalists and start stockpiling cans of beans.

Got accused of being 40 by a zoomer today. I'm 31.

The entire IT industry is cooked. All technology jobs are in the danger zone. Assimilate to AI or become a farmer. At the same time, content creators are more empowered than ever. A 10 year old will build the next big product.

Language detection is surprisingly difficult. The neural networks get basic things wrong. They will say that Korean text is actually Chinese, even though you can obviously see with your eyes that it's not. After multiple libraries failed this basic test, I did something brave and implemented a naive regex solution in #Ditto. It does a first pass on the text before moving it on to the neural network. 안녕하세요 For example, if ALL the characters are in Korean script, it must be Korean. Even if it's a nonsensical sequence of Korean characters, it cannot be any language other than Korean due to the fact Korean makes exclusive use of this character set. There are only a few languages where this is possible: Korean, Greek, and Hebrew. Again, this is only possible if ALL characters in the text match a target language, so simply using "π" in a text does not make it Greek. So, currently this check is very narrow. Notes about other languages: Chinese: it's not possible to do a regex-only solution for Chinese, since Han script is also part of Japanese. Japanese: we *can* definitively detect Japanese, as long as the text contains at least one Hirigana or Katakana character in addition to 0 or more Han characters. So at least *some* Japanese text can be unambiguously detected just by a regex. Russian: Cyrillic text is used by a handful of languages besides Russian. BUT, if the text is entirely Cyrillic, that at least narrows down the *possible* languages it could be. Next steps: To optimize this, the regexes will narrow down possible languages of a text before passing it to the neural network. For example, if a text is entirely Han, we would restrict the model to deciding only between Chinese and Japanese. If it's Cyrillic, we'd do the same thing, but with the 6 or so Cyrillic languages. We could also try to match, say, 90% of the text instead of 100%, to any specific script, to catch outliers like occasional English words used in Japanese, etc. We are already stripping things like punctuation, emojis, and URLs before passing text to the model. Finally, this is all so we can use a lightweight, embedded solution for language detection, instead of calling out to some proprietary API, or even a giant self-hosted solution. In that case, I believe a layered solution will always be needed. We have to do these naive checks to put "guardrails" on the model, so its guesses can't stray outside of common sense. Switching the model can improve it, but these naive checks will still be true.

Elon Musk vs some guy in Japan.

Plus how is WoT not expensive? You have to fetch a bunch of kind 3s and build a social graph.​

WoT WoT WoT, but how do you have WoT on a relay? The only way is to seed it with a specific user's profile, so it has to have an "authority" anyway. The only other way is to implement a Social Credit system for pubkeys, where pubkeys are only allowed to do certain things after they have passed the initial trials, over a period of time. Honestly this seems like a good solution to me, but I think people hate this idea? The problem is that people on Nostr want to have their cake and eat it too. They want absolute freedom to be totally anonymous, ephemeral identity, to see and be seen by everyone. Yet they simultaneously don't want to be spammed by anonymous random accounts. I believe this is the true internal conflict that ReplyGuy exposes. nostr:note19r3nx3qjx0h88028nwfchr36hpepd3z5wuskw40kpzxnkne7lzusv9l7f7