nostr:nprofile1qyw8wumn8ghj7mn0wd68ytngw4eh5mmwv4nhjtnhdaexcep0qy88wumn8ghj7mn0wvhxcmmv9uq36amnwvaz7tmwdaehgu3wvf5hgcm0d9hx2u3wwdhkx6tpdshszymhwden5te0wp6hyurvv4cxzeewv4ej7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq32amnwvaz7tmjv4kxz7fwdehhxarj9e3xwtcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcqyr8a0hmz0xdz9cuy5j44m2xyqfkgwkc3n5850sn3dvsvmtyuc8c6v76umwt just read your NIP 77, a couple thoughts.

- On first read, the format is excellent for what it is. I especially like that you included `confidence`.

- I would be hesitant to ask relays to support this. It could be done using special-purpose relays, but DVMs might be a better option.

- I love the ability to request provenance of a trust recommendation by including 30077s in the request. However, this would seem to lock any other metric for trust out of recommendations, making it impossible to make inferences based on kind 7s, 3s, etc., which I think is important to support as there will be orders of magnitude more data from those sources than from explicit attestations. Am I wrong about that?

https://github.com/lez/nips/blob/master/77.md

Nope, that would be nostr.build or whatever media server you're using

It proxies a few minor things, like NIP05 handle requests, zapper requests, and nostr.watch relay metadata. It also tracks usage by page. Pretty minor stuff.

Bitcoiners deleting their twitter accounts and moving to nostr is like the Gauls burning down their own villages when going to conquer a neighboring tribe. We have territory to conquer, and we will resort to psychopathic behavior to achieve our goals.

nostr:nevent1qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uq3gamnwvaz7tmjv4kxz7tpvfkx2tn0wfnj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09uqzqzkqg8t3jrmghdes2srle9ys92eayeueh0vrez6ampm47yu0sw0xamftpf

itshappening.gif

I've experienced this myself dozens of times, I'm sure it's a factor for many folks. But having such a big mission in play isn't something that I've experienced before.

I don't think this is it. It's harder to make big splashy releases when you have 20k+ lines of code to maintain than when you have <1000. Stuff like reactions used to be a huge deal and get lots of attention. Now, when you do something like release private encrypted groups (100x harder) people hardly notice.

I don't say this with any kind of annoyance, I'm very happy to continue to grind with little to no recognition. Hype is fun, but it's not what any of us came here for.

Yeah, yikes, no kidding

Whose likes are nostr:nprofile1qyt8wumn8ghj7etyv4hzumn0wd68ytnvv9hxgtcppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7mn0wd68ytnzd96xxmmfdejhytnnda3kjctv9uq3xamnwvaz7tm0venxx6rpd9hzuur4vghsz9mhwden5te0wfjkccte9ehx7um5wghxyctwvshsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxthwden5te0wfjkccte9eekummjwsh8xmmrd9skctcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsqgzn9kpsmllqnsf7wh5tz3wgy4cclsftqqplv8tpayrhwgw8llunevdukzye censoring? 👀

m'brain. Tan is interesting, can you explain for non-mathy people like myself?

Every time I see purple rain mentioned I think of this instead:

https://www.youtube.com/watch?v=EwTZ2xpQwpA

Nostr is permissionless, knock yourself out

I populate it on every load

😂

The struggle is real, I ended up creating a function where it would fill the entire graph in one shot, which is a lot faster than caching single results.

https://github.com/coracle-social/coracle/blob/master/src/engine/people/utils.ts#L118

I agree, very hard to find the right partner though, someone who not only wants to work on the same thing with you, but also has the same vision.

Bitcoiners probably are the perfect people to bootstrap nostr, because they have already demonstrated they have an insanely high pain tolerance for bad UX.

In certain circumstances, but it doesn't sound like that's what's happening here

Coracle only publishes kind 10002 relays, maybe Damus isn't picking those up? I see nostr:nprofile1qyfhwumn8ghj7ur4wfcxcetsv9njuetn9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpzamhxue69uhhyetvv9ujuurjd9kkzmpwdejhgtcppemhxue69uhkummn9ekx7mp0qyvhwumn8ghj7un9d3shjtnndehhyapwwdhkx6tpdshszymhwden5te0danxvcmgv95kutnsw43z7qgawaehxw309ahx7um5wghx6at5d9h8jampd3kx2apwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qpqjmqznxuxxxrnaj3m7esjrwauxmvg742ltj0gsgumlmtxukzq99yqwvrcn0 's relays on Coracle

Yeah, wot is basically the same as any other content-related algorithm. Different algorithms will take different things into account, and different people will choose different algorithms, maybe by use case. That doesn't mean having data structures that are explicitly wot-focused are a bad thing, they can be a useful part of the solution. But I'm with you — if someone kind 7's all of someone's notes, that's a strong signal, and doesn't require the user to maintain anything to get the benefits.

https://imgflip.com/i/8liwem

Let's do it!

Onion layers are continuous, branches are discrete. Unless you're talking about some kind of fractal onion tesseract

BOIL THE OCEANS

I thought you said you think of nips as an ogre, I mean onion

They probably should (Coracle doesn't)

I'm literally dying

Maybe nostr should have used uuids instead of kinds nostr:nprofile1qyt8wumn8ghj7un9d3shjtnddaehgu3wwp6kytcprfmhxue69uhhyetvv9ujuumgd96xvmmjvdjjummwv5hszxthwden5te0dehhxarj9e3k76twve6kuepwv9c8qtcqypuu9jhpzn4z32vpua2eknl8s49ywdfp4rfz5e4m4w06yj8tsg8lvxxqdcn

You'd understand if you had experience using either of those platforms

"SB 1228... would require users with more than 25,000 followers or who are sharing more than 1,000 pieces of AI-generated content to verify their name, phone number, and email. For users over 100,000 followers or those sharing more than 5,000 pieces of AI-generated content, the platform is required to seek verification of a user’s government issued ID."

https://sd18.senate.ca.gov/news/senator-padilla-and-legislative-partners-announce-bill-package-combating-election

Coracle and Iris tgat I'm aware of. Coracle has wot mute, and folows of follows feeda, but that's all. More clients may have added wot features recently though.

Maybe an important clarification would be "nostr as social media" rather than "nostr as an architecture". The network itself has the bear the burden of all the use cases currently attempting to be fulfilled on it.

Much obliged, thanks for banning me 😂

For the same reason I prefer outbox to inbox, I think it makes much more sense for clients to fetch the notes the user wants to see. It isn't the publisher's problem to make sure their followers see their note, it's the follower's problem to find a tool to curate their content in the way they would like.

If I were to pit nostr:nprofile1qy28wumn8ghj7un9d3shjctzd3jjummjvuhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0qqs04xzt6ldm9qhs0ctw0t58kf4z57umjzmjg6jywu0seadwtqqc75s957w80 's solutions against one another, I prefer fomostr to shipyard (at least as far as this use case is concerned) 😂

😂😂😂 I doubt it, but maybe we'll have a different topic du jour by then

It is

I was calling it "outbox" for a while, but I gave up. I wonder why "NIP 65" didn't catch on 🤔

It might be an interesting experiment short term, and might get some people to support gossip, but long term we can't stop blastr, we have to be better than blastr. The real way forward is relays figuring out their own authentication and retention policies.

That's something that I've done a lot of experimentation with but everything is currently sort of languishing. PRs are open if you want to use Coracle as a WoT playground!

Pyramid only allows cool people to write to it (this supports global, and stores my notes)

hodlbod.nostr1.com is my personal relay (hosted on relay.tools, basically redundant with pyramid, but I control it, sort of)

purplepag.es is an index of pubkeys to profiles and relay selections (allows me to find notes by any pubkey that has published a relay selection)

It's really quite elegant

That's a great question, I don't know. Maybe it can't be answered, because it's dependent on a whole bunch of social factors, like how likely relay runners are to censor users, or what a given user's risk profile for censorship looks like.

In theory, 2 relays for the entire network is enough. But that introduces scaling issues and the possibility for them to cooperate in banning someone. My best guess is that at the network's current size, 5-10 hubs is probably enough, plus relays that support special use cases, like authenticated communities and archival relays. Nerds will run their own relays, which is fine, but it doesn't really benefit anyone as long as censorship or relay failure is only occasional. I guess what's most important is that 1. there are backups of important data, and 2. it's easy to create a new relay when one is needed.

I literally talked about this with Cloud Fodder on TGFN a few weeks ago, so no, I don't think "nobody cares about the back end".

Sold the dip again 😔 ah the joys of being paid in bitcoin

I haven't thought that far out yet. But it's an important project, hopefully it can be monetized somehow

BEEEEEETCOIIIIIINNNNN

If replication and distributed retrieval can be solved I'll be excited. Same problem nostr has in general. I think it's doable, but it hasn't been done.

For sure, you always need to bootstrap. And Coracle currently uses static lists too, it's a fine first step. But it would be amazing to see these bootstrap lists turned into a "explore" tool which opens up the network based on dynamic trust networks.

Yeah, I agree with this. And I know people operate differently, so if you want to have a constant drip of stuff to fill your brain with, fine. But mindful social is much harder, and possibly more rewarding.

no

Terrence Malick, Danny Boyle, Ridley Scott

I'm on team "replaceable events are bad". nostr:nprofile1qywhwumn8ghj7mn0wd68ytndw46xjmnewaskcmr9wshxxmmd9uq3qamnwvaz7tmwdaehgu3wd4hk6tcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsqgzsm98u9kzcp35zkpc62shck8335gqtq5yt4w26xwl0pp2a72qavvkw9mkh race conditions frequently happen regardless of client implementation, where a stale version forms the basis for an update. The more attributes on kind 3, the more potential for race conditions.

Do you have any opinions on how hybrid nostr/pear apps might work? DHTs are ok for indexing, but can't hold all the data. Maybe pear could be used to replicate indexes of the nostr network (i.e. kind 10002 and maybe kind 3's, what purplepag.es currently does). Nostr keypairs could also maybe be used along with that index to bootstrap p2p DM channels. But does pear work offline? IOW, to receive a DM both peers would have to be active I assume. So nostr's relay idea could be used to bridge the temporal gap between peer availability.