I guess there are different ways to do it. I've always put it in .gitignore in libraries, and kept it checked-in in binaries.

As a binary, Cargo.lock's precise selections matter. I do "cargo update" from time to time.

Well I just pushed a fix so .... regossip

Paid.

Yeah, I was far too categorical. There are many reasons. And I disagree with Peterson on the whole. But I highly doubt he would be swayed.

I'm pretty sure he does. He's a psychologist, it's his field to know about human behavior.

I think nyms are only needed if your government seems likely to become very oppressive in the near future and punish you for past political wrongspeak. That's unfortunately true in all Western countries right now. The unfornate downside is much less self-control over one's behavior.

I'll process this when I get home. Have to mine fiat atm.

Centralization that is chosen rather than required is still much better

Paid.

This is one reason I don't thing nostr should contain multimedia. They would come here and put a target on us.

GOSSIP USERS: primary support for NIP-65 has been merged in. That means:

* You can configure which relays you read and write to

* You can advertise this configuration to many relays other than you normally write to

* You will not miss quite so many posts from other gossip users who have done this (you can still miss some but it will get better with more code and more uptake)

The code that watches your read relays for mentions might not work in practice as relays drop connections on us. It doesn't recover currently. But the code that writes posts that mention you to your read relays isn't in there yet anyways.

And remember, this is experimental. Things might not work as expected. Please let me know if there are problems.

Try to browse around anything you can. On people's names, you can click and view their feed. On posts you can click the right arrow and try to get the thread. Over time it will pick up where people post so it can follow their stuff.

it's hard to get started

FYI

#[0]

your NIP-11 on wss://nostr.einundzwanzig.space/ should have the pubkey in hex format, like this:

031ea306188fee631a86f1a0e49cee8f3d62592b2e7be5f8eb1788e327db340a

I would prefer a new kind 10002 like this:

id = id

pubkey = pubkey

created_at = created_at

kind = 10002

tags = [

[ "r", "wss://nostr.mikedilger.com" ],

[ "r", "wss://nostr-relay.wlvs.space" ],

[ "r", "wss://nostr.fmt.wiz.biz" ]

]

content = ""

sig = sig

That means "I (pubkey) post to these 3 relays." I spread this far and wide so people who wish to follow my content can find my content.

> If you have this then you have the censorship problems we've seen solved (we don't need Carmen Sandiego clients that try to stealthy find our censored follows). Your follows list(s) can go with you but you do not need to abdegate clever stuff to your client that hides it all from you and asks you to trust it.

I want to follow Steve Bellovin but I don't know where he posts. So I ask several "bootstrap" relays to get his "relay list" (relays that specialize in just storing relay lists). One of them serves it to me (because he sprayed it far and wide). I can now see on his "person" page in my client that he posts at A, B, and C. Ok, now I can manually surf to A, B, or C and see his posts (or in my client you don't have to it just shows up in your general feed... but I don't want to argue that point, it's immaterial).

The client doesn't need to do any clever stuff (gossip is far too complex). It doesn't have to hide this "relay list". It can be right there, an event you can view in raw form if you want. It's pretty simple, but it requires a paradigm shift of spraying our relay lists and clients using them.

I think that is a great model. Make relays front and center, and users travel around browsing them.

I also think some users want to know "What is Edward Snowden saying?" and they don't really care where he is saying it, they just want the "it" being said.

So we need multiple models working in parallel.

Interesting. This allows people to move around rapidly. However, what if I want someone's events spanning a longer time period?

It's the same problem of following threads across multiple relays which isn't fully solved either.

I interpret kind 2 to say "Hey this is a great relay, you guys should try it", rather than "If you want to find my posts in the future, I expect to be putting them here". kind-2 also only has a single relay in the contents.

kind 10001 in nip 23 (pr 32) would work. I'm not excited about parsing the runes language, but it would serve.

Currently gossip does excessively complex tracking of stuff because "here is where I post" information is not easily and widely available.

I am in favor of "spraying" relay lists, and posting regular events to just 2 or 3 relays. Even if you get booted from all 2-3 of your relays, just spray your relay list again with updated information and people can find you again (once clients start following people instead of following relays).

It might also be useful to have "bootstrap finder" relays dedicated to accepting and serving only relay lists. Spray to those so you can be found.

The spray isn't very bad because it is just 1 event per relay per person (a replaceable event).

I'm in favor of kind 10001 or similar relay lists (using the contents of kind-3 Contact lists is heavy-weight because Contact lists are huge).

This is a refinement of my thinking and not something I've explicitly said elsewhere yet afaik. #[1]

Yeah. I think posts should show where they came from ideally without needing to click a pulldown. But I'm trying to figure out how to make it not take too much space at the same time.

You don' t have to pull everybody's messages from all 40 (or 500) relays. You can pull them from just N (I use 2 or 3). That way you aren't getting massive duplicates.

Oh! I see. He will get far with that one. 😆

I was just mentioning something someone else was talking about. I also don't know anything about DHTs. These are just words I hear bandied about when talking about services that help people find people.

There has been some chatter about services that specialize in bootstrapping like this, DHTs, nprofile servers, etc. I'm staying out of the server-side of things, but happy to subscribe to such things when they exist.

For writes, users manually choose. I think this is going to be more and more necessary as relays start requiring subscriptions.

I think posting normal messages, just a few relays. For posting your relay list, might be smart to post it to many relays so more people can find you. I'll be adding something for that.

Ah I just saw your reply to a similar question.

I like the idea, but a timestamp doesn't really indicate something has expired unless there is a policy to make a new one every N days. And 'nprofile' is defined in a NIP without having a timestamp, so you'd have to debate some people to have that changed. If you wanted the QR to contain things other than nprofile, then other clients wouldn't understand. So I think this isn't going to work.

If you look closely at the picture I posted, you can see that I do including the QR code for it (which is quite large).