Correct assessment of the meme culture: nostr:nevent1qvzqqqqqqypzqe6msnl8tcsk4w28capcaegeefmh2dmdmuza4ha6vfut6qfwr4egqqsxpt5n827c9hjucfc2x2xz863x5nyp95mkejg495trxmhrjlwh6nqktfya8

So both https://www.themoneyillusion.com/ and https://slatestarcodex.com/ have abandoned their blogs which worked perfectly over many years and migrated to Substack. I imagine many other blogs I never knew about have done the same. Why is that and what does it mean for us?

It adds a huge amount of complexity on all layers.

It's open! nostr:nevent1qqsqqqrcx70w545ru7zg4hrg3k6mlvywurx8p6ql42pfl9g4m6pww4gpz4mhxue69uhkzet8d9ejuat50phjummwv5hszrnhwden5te0dehhxtnvdakz7qg3waehxw309ahx7um5wgh8w6twv5hsr6c53v

"Choose your own algorithm" will NEVER work on Nostr the way it works on Bluesky. Smart platform-provided algorithmic feeds like those from X, TikTok or Instagram will NEVER work on Nostr. Anything that requires filtering from a "global feed" of all notes and delivering that to specific users will never work on Nostr because there isn't and there cannot ever be a global feed on Nostr. If that is what you think Nostr needs to be good and popular then you'll first have to destroy Nostr by turning it into something else, and then you can implement it. The alternative is to create something new, a new way of doing discovery, something that actually works nicely within the Nostr constraints, something that actually only works on Nostr because only Nostr has these distributed independent servers with specific owners, specific rules, different users, personalities and preferences.

Before bringing millions of users we have to bring the small group of nerds and enthusiasts that would naturally be interested in what we're doing just so they can help build it.

If a client connects to 6 relays and downloads the same 1000 notes from all the 6 relays every time you open it then it's not a Nostr problem, it's a client problem.

Turns out Wikipedia is even worse than you thought: nostr:nevent1qqsgmg6fmtscjdgwfhzzyvzrww5k249a9pdvulfz4jxa283amkrpyccpzemhxue69uhk2er9dchxummnw3ezumrpdejz7qgwwaehxw309ahx7uewd3hkctcpremhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet59ujw9vdy

Is LetsEncrypt run by the NSA?

For years I've seen people asking for a way to request only IDs from a relay and not the full event, so I suppose there will be great public commotion when it becomes known that https://github.com/fiatjaf/nak now supports this very dangerous flag: ~> nak req --ids-only --since 'yesterday' -k 20 offchain.pub c4888c4ea325677cd56798c28ea70a2a21ad15899c11e25973e7fe8d10681dd1 0d19706d839fc529f061dd477d317f6d32ce708bace2f689be02b2607142b9fc f278ada73cce757b91f1733636a698b93cd7985417b3a7f141bd900a85a074de 328e05fcf397085ff19fe10ff9ee5592590b68f584fce9e2484b271e2852f35e 1ad4890180b12ff569aef251211ea645674cec555ecaf702dc812c5a1d162a80 11c84308a092f5ac8fbf226b3ec968ac42c961b9435a722229a06fbf10a66ff8 0ecc3972d3715a13f181a16bc437897a8d477fd722ba3cea55c996cfa2af1f77 d1f4260bdb40aa3049600d94fd9bb6ce43464d2b329478f6aa363ea33805a3a0 17781a89078d3eb5b63db6ce95026d2ce00b086d98aafc436e64bb093425d8a7 6957568c6412cad04f4e2b869e7d9af4be58f4483123207d2b9fd65c9a1e1004 0918ffa33aa95bcc1ecff96627c8e7224c29692e58948e219b1388bd7155dcbb d9b0a89fce1102e9048f08705b724c37558969ff2e47c657a73c2c83231c4f8c 91747d307329bf7e35c195a504b4cbc4a18b2e2210bbb82606966a19b856e0c0 8aa7ab17361a4159732cb3c6cfb391a85ea90677cba2f70e32ce6c70f7b57f27 3de79712e48dbe8fa41d4b4cc707a54dbce92609b2eca69073a7e740faf4366c f966742694ca67b1dcb06d3953bbb3b0544b22c9dfb77b239eb98284e2232176 29a16716bd6372f091dd9f6e450321d8ca053258061e2b1382700a466eb679f2 540bd290bf1f8239bd2cf07334da7bf63a244eff0f6461039ec5f66de7417b6b Powered by NIP-77/Negentropy.

GitLab is pure garbage.

Don't worry: because Bluesky allows anyone to build their own filters for what they consider safe content that alleviates pressure over the top company to act as an arbiter of what is allowed and what isn't. That is why Bluesky is sufficiently decentralized and a great step forward towards a world where social media can act as a neutral public square for humanity. nostr:nevent1qqsw2lh463slpsn4gdz3gmn0luu9hpczd6tutsd9pwvpepnvzgzd0gcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsp3r2g2

Thank for for letting me know. Please try v0.9.0.

Who are the crazy people who watch podcasts in video format?

I made a Bluesky account: https://bsky.app/profile/lsdjkfhbksdjf.bsky.social

WebSockets > HTTP

Nostr needs key rotation like Bluesky, where you can rotate your compromised client key using your compromised master key to a new key, all by just clicking buttons that will instruct a compromised cloud server to perform signatures that no one will ever see and that no other user will ever check. Without that it will remain an absolute joke.

Users don't need to flock to popular relays to achieve maximal reach, they just need their followers to follow them on whatever relays they publish to. This is how it's supposed to work: https://how-nostr-works.pages.dev/#/outbox

We are reaching new levels of tech advancement here: nostr:nevent1qqstdeudu2kfw55eueeyzmcq9tng76wpr32s7xtxhvwk84udwrgztaqpzpmhxue69uhkztnwdaejumr0dshszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctc4rygfh

I know everybody is very entertained with the reply guy and no one cares, but I've made this blossom simple CLI client: https://git.fiatjaf.com/blossom

Publish it with a key owned by the nostr.build service specifically for these matters and tell clients what that key is so they can trust it.

About the conference: I was very happy to learn some days ago that such a conference was going to take place. I had some hopes that the previous Nostrasia would be a Japanese thing but apparently it was a full-on English thing with just foreigners and no Japanese people in it, so now I am happy that you're doing this one. It was a blessing when all of a sudden we started seeing Japanese characters being sent to Nostr in the beginning of last year and I couldn't read them, but every time I tried to translate them I would get some pictoresque joke related to poop or alpacas, completely out of context due to the air-reply style of the conversation, naturally formed around the existence of relays dedicated to the Japanese community. (By the way, me and some others have been trying to promote the idea of having "community" relays on Nostr for a while, and it oftens falls into deaf ears, meanwhile that was the first thing the Japanese community did, so that was very inspiring.) I still don't understand the Japanese people on that are on Nostr, I've tried to talk to some members of the community in order to understand them, but most of the times I left the conversation more confused than before, but I think that is great and fits perfectly into the "embrace the chaos" Nostr ethos.

Sorry for taking so long to respond, it happened that this event didn't show up for me at all given the fact that I have a very strict set of relays advertised as "inbox" relays on my kind 10002 event and my main client, https://github.com/mikedilger/gossip, only checks these relays for events tagging me. I'm using this opportunity now to say that clients should relay on that information in order to choose the relays they're going to use to publish events when replying to someone or tagging someone. Thank you.

People not able to resolve these quoted events: nostr:nevent1qqszewytwx9z5cgfjqr0pk5al3ttd6zf663k6te7fa8ewe3nzq7qsgsprdmhxue69uhhyetvv9ujuam9wd6x2unwvf6xxtnrdakj773y297

Can you also repair nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49's bathroom?

This is actually perfect.