Lez

Disrupt!

Public Key

npub1elta7cneng3w8p9y4dw633qzdjr4kyvaparuyuttyrx6e8xp7xnq32cume

NIP-05 Address

lez@huszonegy.world

NIP-57 Address

lez@npub.cash

Profile Code

nprofile1qqsvl47lvfue5ghrsjj2khdgcspxep6mzxws737zw94jpndvnnqlrfsppemhxue69uhkummn9ekx7mp0qyfhwumn8ghj7ur4wfcxcetsv9njuetn9u27pwtj

Publishing to

nos.lol

purplepag.es

relay.current.fyi

Author Public Key

npub1elta7cneng3w8p9y4dw633qzdjr4kyvaparuyuttyrx6e8xp7xnq32cume

Show more details

Last Notes

2024-06-19 16:19:47

Trustroot, a couchsurfing app is currently being nostrified! Currently it's nostr notes put on a map: https://notes.trustroots.org/
https://github.com/Trustroots/nostr-map

2024-06-11 15:31:34

- reply

Hi, thanks for the feedback!
I don't get the usecase with the git-remote-nostr proxying requests. Do you mean blossom scheme should be used in `clone` tags instead of nostr://, and nostr:// would be some kind of multiplexer for the remotes that show up among the `clone` tags?

2024-05-22 20:43:47

- reply

Seems like no. There were uncommitted trials doing that.

2024-05-21 20:00:42

- reply

You are right, we don't need the git+ prefix. Nobody uses it anyway.

2024-05-21 17:04:39

- reply

I think we would have problems when committing large files in nostr events. Probably there are relays that limit the size of events. And this is the kind of error that doesn't surface for weeks when a project is started.

2024-05-21 16:55:35

- reply

Why not use (git+)nostr:(//)npub1xxxxxxx/some-project as git remote url? It tells more about the owner and the project, too. Relay discovery is a thing to solve but with purplepag.es we are quite good I think.
The git+nostr: scheme could be more descriptive to what kind of URL this is, e.g. where to paste it.

2024-05-20 19:34:31

- reply

Yes, I can bootstrap trust data from zero by using follows, but the more difficult part is to bootstrap the content itself, e.g. make people to post lots of interesting articles and discussion starters and come back regularly. Like it happened in reddit. I still like the simplicity of the idea.

2024-05-19 12:59:17

- reply

For step 3-4:
I'm thinking about a site where you can have discussions on each context category. A discussion can be initiated by posting a articles with some personal comments, or just asking a question. So this becomes a reddit clone based on web of trust.
The web of trust calculation can start as simple as taking follows and mutes into count.
Next to the discussion comments there is a BUTTON where you can express your trust in the author's expertise in the category under which it was posted. It creates a new trust event (NIP-77), that is processed the same way as a follow, only difference is that it has much much more score for the exact category it was issued for, somewhat more score for parent categories, and waaaay less score for all other categories.
With this app there is 1 to 1 link between category and trust attestations, so it's probably good way to bootstrap contextual trust.
Problem with this approach is that there is no initial data to start with, so it might be hard to bootstrap the idea.

2024-05-17 13:03:38

- reply

nem látok zepet, mikor mennyi lett volna?

2024-05-17 13:00:17

What's the difference between a client and an app? #asknostr

2024-05-16 15:13:02

- reply

Halló!

2024-05-15 15:30:31

- reply

Drop me a msg if you have something to test out!

2024-05-08 21:13:55

- reply

You mixed up the graph, it's VAT in Hungary...

2024-05-07 20:57:39

Nostr is the way you want the web to be.

2024-05-04 16:37:11

- reply

No worries, the tools are on the way!https://m.primal.net/IDHj.jpg

2024-04-27 07:52:29

- reply

Yay! You can shitpost now!

2024-04-22 20:23:18

- reply

Me too.

2024-04-19 08:30:22

- reply

Or there is an opportunity in decentralizing those registries. I guess it hasn't been done because it's not particularly rewarding job to do.

2024-04-16 17:19:03

- reply

This is utter bullshit! You are not free, freedom is relative. You must breath, you must have social relations, you must have a place to live, and so on. And what do you do with the freedom you've been fighting for? You fill it with purpose! And then, you're not free anymore. You take on responsibilities, make promises to yourself and the world. And you continue to fight for your freedom to be able to fulfil your purpose even better. You'll need social, economic capital to succeed. And if you call out bullshit in the wrong place, or too much, or too cruel, you will be cut out from the social network and it will be hard to achieve your purpose alone.
But yeah, there is a point in time when you have to take that step and call bullshit on everyone around you, so as you can experience true perfect freedom for a few hours, days or even years, just to realize it's not what you wanted in the first place.

2024-04-06 05:26:49

- reply

If you need filtering based on that tag, then maybe a separate kind is better. Otherwise, "proto" would be self-descriptive and wouldn't interfere with "p" at all. Intuitively if I would see "P", I would associate it with pubkey, too.

2024-04-05 16:31:59

- reply

Haha, it feels a little bit like this classic xkcd: https://xkcd.com/927/
I think it's not a task of a NIP to define how we're going to use existing trust attestations, explicit (38000) or implicit ("827919") or proxy (zaps+likes). This is a field where "read" algorithms will compete. Maybe a NIP could be used to define the inputs or outputs for such algorithms, but it was not my intention with NIP-77.
I would be fine if app developers in the future chose this uniform format to express trust. I also think it's useful to have a query that returns a recursive trust graph, and algorithms can do anything on this data, possibly including other data sources. The goal is to avoid the xkcd situation as much as humanly possible.
And thanks for mentioning couchsurfing! https://www.trustroots.org wants to bring his community + reputation system to nostr, I'll contact him!

2024-04-04 14:10:02

- reply

Updated NIP-77 proposal about Web-of-trust.
https://github.com/lez/nips/blob/master/77.md
It feels clean and simple to me, also extensible, but I would love to hear feedback on that.
#wot #sovwot #wotnip #nip77 #trust #hierarchy

2024-04-04 14:08:22

Updated NIP-77 proposal about Web-of-trust based on explicit trust attestations. https://github.com/lez/nips/blob/master/77.md
It feels clean and simple to me, but I would love to hear feedback on that.
#wot #sovwot #wotnip #nip77 #trust #hierarchy

2024-03-30 11:37:30

- reply

Here is my 2 cents for the questions:
1. App developers often make bugs, and for list events it means that it's easier to unwittingly erase the list if the user wants to add a new pubkey and cannot find the previous event on the network. Apart from that, it's easier to build graph from individual events (as VictorPamplona mentions in the github issue).
1.5 Replaceable events or static events? - Replaceable events can be updated, if trust relation changes over time. Also, event deletion seem to be not well implemented in relays.
2. Another model is private to the author + shared by relay/DVM when needed. I think the common sentiment is that we all see usecases for private trust events, but implementation is more complex. We need interactive protocol for this - as Hodlbod mentioned - or ZK proofs, and who knows what. For now, I think we should go for public, discover the possibilities and implement private model when we know more about the problem / we see what the main usecases are.
3. I would vote for an optional scalar "score" and "confidence" value. If they are absent, it's a binary true value.
4. I like the "context" term. I think it could be optional, but see a lot of value in embedding into the event, so as it can be used by filters as input. I don't see clearly what is the usecase for it derived by filters. Is it like "I trust this guy", and the algorithm tells me the context it was used in?
5. I'm probably not the one who has dig into it deeply. Not sure if this is what you mean by spec, but I'd like to know: what are the inputs/outputs, where the filter should be ran (client / relay / DVM / phone) and when (when content is created OR when queried). Should I be able to make a relay subscription based on a content filter?

2024-03-29 11:20:02

- reply

"ostriga" means Oyster in my language (Hungarian). Just saying.

2024-03-28 18:23:46

- reply

One of the many approaches to this problem: https://github.com/lez/nips/blob/master/77.md

2024-03-28 11:27:55

- reply

If you're already in there, get well soon. If it's just a feeling that you're tired more than you should be, there is still a chance to fight it back agressively and early. My tactics on this is to take 50k vitamine D + 50k vitamin A + 3 drops of MMS, later on 4g of vitamin C. Add Zinc 30mg and Magnesium 200mg (from glycinate). Next day, continue with 50k vitamin D, 50k vitamin a 2 times, 12hrs delay in between. Usually I can avoid getting sick by doing it, or if not, it will be much less severe.

2024-03-26 21:43:54

- reply

Looking forward! Tired of imgur and aws URLs.

2024-03-26 21:35:02

- reply

On nostr, I would share them.

2024-03-26 21:14:13

- reply

I could see the blue sound level going up and down as I speak on the mic icon before it disappeared.

2024-03-26 19:09:40

- reply

I'm ready to test further, if you have any suggestions, or a new version. I'd be happy if it worked.

2024-03-26 16:45:15

- reply

Thank you, I appreciate that. Are you affiliated with Nostrnests?
I'm not on VPN, using Linux desktop, adblock disabled. I can see some messages in the console (this is when the mic icon disappears):
```
pc state change: from CONNECTING to FAILED
Object { room: "c064f73c-4a2b-45f0-8eca-2dccda8c5c9d", roomSid: "RM_QRFskwji8tox", identity: "cfd7df62799a22e384a4ab5da8c4026c875b119d0f47c2716b20cdac9cc1f1a6" }
Error: could not establish pc connection
Hd https://nostrnests.com/assets/index-A7UgGz23.js:143
vt https://nostrnests.com/assets/index-A7UgGz23.js:143
l https://nostrnests.com/assets/index-A7UgGz23.js:145
index-A7UgGz23.js:151:20689
```

2024-03-24 10:41:12

- reply

The kernel does the buffering for you, you don't need a library for that. This is my long time favourite because of it's simpleness and complete control over what's going on in lower layers. Simple to debug. HZRD can probably make a decision for himself if he wants to dive in, or go in a different direction. He is not a newbie in programming, and after talking to him in person, I'm sure as hell he can do it.

2024-03-24 10:10:01

- reply

Just send over type + lenght + data for each fields over a TCP connection. It's easy to implement

2024-03-24 09:06:44

- reply

Ott és akkor a .hu domaint kerestem, vagy bármi ismerőset, de semmilyen támpont nem volt.

2024-03-22 11:41:04

- reply

Egy jó kis magyar relay, bizony az frankó lenne. Régebben már próbálkoztam nostr-rel, és a relay-választásnál hasaltam el (gossip). Ha lett volna egy `.hu` relay, lehet máshogy alakult volna.

2024-03-21 21:54:20

Nostr podcast is up (Hungarian language):
https://www.youtube.com/watch?v=ZJ9WCUxmxgU

2024-03-21 18:27:47

- reply

It's inevitable, but there's lot to do until then so as we don't get enslaved by it or a small group of humans using it.

2024-03-21 17:13:08

- reply

It works!

2024-03-21 14:26:29

Working on a new NIP. It makes possible to have multiple different moderators on the same set of events. And more.
https://github.com/lez/nips/blob/master/77.md

2024-03-20 12:15:37

We are doing a Nostr podcast! Yay! Link coming later.

2024-03-14 17:06:50

- reply

Azt hiszem, hogy csak az én kliensem csinálja (primal). Ahol #hashtaget raksz, linket csinál belőle, de csak az első #ékezetig. Tehát a #felezés-ből #felez és lesz.

2024-03-13 00:48:11

- reply

It's moving too fast to be practical for measurement

2024-03-12 19:28:17

- reply

Vicces ahogy az ékezetes karaktereknél megszakad a #hashtag (primal)

2024-03-04 01:28:54

Bitcoin Atlantis was a game changing experience for me. I became excited every single day. I met my blood, found my kind and taken pills of various colors.