why，any specific reason？it was hardcoded before，unable to switching and grouping
Today's build #foodstr #cookstr #washoku
https://nostrcheck.me/media/public/nostrcheck.me_3360752157107064851688469887.webp
i am curious how to eat those tofu ， without any source？
ah, I didn't do any test yet. mobile might not work correctly. will check after.
I do think the new https://flycat.club has the most beautiful UI across all the web clients now.
the different relay modes on flycat. I just realized the fastest mode might be dropped since it is kind of useless. the global/auto mode is my favorite. I think every client should impl such relay selector component. combine with the hand-pick option and gossip mode
here is me and rabble talk about this stuff nostr:note1w45d4er9msgnyhg2t7mn9lflpdcepjsxt2sj0dtr9plw758r5s5s4c8rq5 what do you think of this Nip-172 approach for building community? nostr:npub1wmr34t36fy03m8hvgl96zl3znndyzyaqhwmwdtshwmtkg03fetaqhjg240
https://blowater.deno.dev supports inline pubkey profile rendering now!
npub1dww6jgxykmkt7tqjqx985tg58dxlm7v83sa743578xa4j7zpe3hql6pdnf
doesn't it required “nostr：” as prefix？
And this is already happening on nostr. Just look at the Japanese community, they are a total different universe, they got thier own relays, their own tools, What Japanese have today is what we will become tomorrow
One step towards that would be to make a web app to show a view in to a relay, who’s on it, how to join, what content is published there, how to follow a relay. Some of that we’ve got in nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch but a bunch isn’t done.
We made a viewer for scuttlebutt pubs, you can see it at planetary.name. We need something like that for Nostr I think.
I like this approach because that make the relay operator be the last content curator makes more sense to me. People will and only will save whatever they likes to save for data, unless they got paid to save
that is my vision too. however, instead of the current community NIP, I prefer to build on relay-base community, which bascially each relay is a different community host different people and different content. you can also setup different profile metadata on different relays. it is compatible with current protocol. we just need more small relays/diversity relays.
I think it is just wasm bytecode right now. I would love some standard runtime with predefined nostr stuff on the client side
那边在想着怎么限制 api 访问，这边已经在想 AI 对抗 AI，让AI做内容管理员了 nostr:note1ryfqnwfvntxd7qz6zp7rt5h89mk5ku2m9ylg84e5rz264ytt4j5sdy900z
