Avatar
Lez
cfd7df62799a22e384a4ab5da8c4026c875b119d0f47c2716b20cdac9cc1f1a6
Inventor of nsite, building tribewiki.org. Biohacker.

Have a look at handshake protocol. There's no authority there. And it's quite an original approach.

Petname systems are fine, they have their use, but when you want to make a billboard with your name, it's better to have a global unique resolution to that name, because you don't have control over everyone's web of trust. For someone with infinite fiat resources it's easy to register that name in thousands of other webs of trust, so you will be impersonated easily.

And resolving a naming conflict - if both candidates want that name - inevitably comes with a need for authority (community leader) who decides who will get the name.

But I'd be happy to hear what nostr:npub1lunaq893u4hmtpvqxpk8hfmtkqmm7ggutdtnc4hyuux2skr4ttcqr827lj thinks of it.

Most people are bad at memorizing npubs or IP addresses. Therefore most people tend to depend on naming systems like DNS.

Yeah, with IPv6 you can have thousands or millions of addresses, just for you. You can have a public IP for every service, for every tweet, or whatever. So IANA cannot hide behind the narrative of the scarcity of IP addresses, as they do right now. And ISP's don't even give you a public IP anymore, you just get a NATted address in many countries. That's one of the reasons why DHT's don't work in internet scale, because holepunching is a pain in the ass. Even if they give you a public dynamic IP, you can't use it to run a service without a dyndns because it's dynamic. And peer to peer stuff depends on being able to reliably find each other.

nostr:npub1getal6ykt05fsz5nqu4uld09nfj3y3qxmv8crys4aeut53unfvlqr80nfm I'd like to give feedback, but I cannot log in to the feedback app. Take it as a feedback.

IPv6 will deprecate the IP address arbitrators. Handshake protocol will deprecate ICANN on the DNS names.

I learnt about your #realy just now. First I dismissed it because my eyes would just read it as #relay. We as species are not fully evolved for reading :)

#asknostr What tools / clients are out there to synchronize my profile events between my relays? And to synchronize my posts? Blastr is a bit of an overkill for this.

Shouldn't clients or even development frameworks do that automatically and silently, not only for my events but for everyone's? (an idealist here)

Happened to me, too.

I tried to delete an old repo of mine, because I wanted my latest repo to be shown on the frontpage, and not grouped.

I tried to remove every single tag (except the `d` tag) from the repo, but I used the default sec=1 account in nak.

Now it somehow shows 7 empty items as the first item, with no metadata.

I think it should be hidden from the UI if there's no metadata in the announcement event. (e.g. =delete)

It happens to me, too. I visit repo A, read the about page. Then I go back to browse the list of repos, then visit repo B.

What happens is I see repo A's README until repo B's README is fetched.

The solution might be just clearing already fetched data before start fetching the other.

git-remote-blossom and blossom:// are good ideas, I'll employ them!

The npub/relay/identifier scheme definitely keeps the URL well readable.

nprofile contains the same data, but it's obfuscated.

Thanks for the feedback!

I'd love to have a social client only for longform posts. E.g. to see the longform posts of my follows. Should be low hanging fruit to implement, maybe someone already did that?

GM

The #git remote helper I wrote in the summer in #sec02 just got much better. The new Proof of Concept supports sha1 git repos, so you can push your pet project to a nostr relay and a blossom server.

Maybe it's a toy, maybe it's a super project, I don't know. One thing is sure: soon it'll be possible to push to git repos without leaving the browser!

I'd like to have some feedback about the direction I should move on with the git remote URL format. A sole npub in the URL is suboptimal, since it can be difficult to find the relay for the npub.

https://github.com/lez/git-remote-nostr

Probably already discussed, but why do we have 2 protocols for 1 task? It seems there is a lot of overlapping between them.

Tülköljél! :)

Just installed a new relay for the Hungarian Nostr community. It has the most boring name I could come up with: "relay.nostr.hu"

And it's very possible that mold isn't the root cause, but the sensitivity is the consequence of some common underlying issue, which possibly caused her previous symptoms, too.

No solid knowledge here, but I recently came across a podcast where Dr. Klinghardt goes deep into retroviruses... and a multi-level mechanism that can cause various toxicity issues... Retroviruses cause mutations in the genes, like the infamous MTHFR mutation. It impairs the body's ability to detoxify, and toxins build up in the body, causing a wide spectrum of symptoms.

This podcast is https://www.betterhealthguy.com/episode78

But even if he is mistaken, clearly something is going on, since chronic illnesses are skyrocketing.

I started using Ditto as my main client. So far so good!

https://ditto.pub