Why not? I’m agree about hyperdrive and holepunch but do know how nostr related. Also gateway can be more that one without having nostr discovery problem

Yesterday I was doing a lot of research on how #hyperdrive and the #holepunch project work. Would it be possible to use it to make #twtxt an easier gateway for new users? Could we stop using web servers?
My conclusion: We would end up being a #nostr. On the one hand it would become more complex to use, it would force the user to have software installed, and on the other hand the community would need a central proxy to make the routes accessible via HTTP. In other words, it’s not a good idea.
However, it’s an AMAZING technology. I want to start playing with it.

Why not nostr way? https://github.com/nostr-protocol/nips/blob/master/05.md#showing-just-the-domain-as-an-identifier

One benefit with bluesky is your username is also a website. And not a clunky URL with slashes and such. I wish twtxt adopted that. I have advocated for webfinger to for twtxt to let us do something like it with usernames. Nostr has something like it

By default the bsky.social urls all redirect to their feeds like: hmpxvt.bsky.social
Many custom urls will redirect to some kind of linktree or just their feed cwebonline.com or la.bonne.petite.sour.is or if you are a major outlet just to your web presence like https://theonion.com‬ or https://netflix.com

Its just good SEO practice

Do all nostr addresses take you to the person if typed into a browser? That is the secret sauce.
No having to go to some random page first. no accounts. no apps to install. just direct to the person.

In nostr/simplex you did not bounded account to server because its just a relay. In matrix, xmpp and salty.im you store account data on broker and when broker is down you will no longer to communicate

I think salty.im is simplest than simplex. But attempt to implement this i have problems than salty cli cant decrypt messages from another saltpack realization (and reverse) . Also simplex is more decentralized (like nostr?)

@falsifian@www.falsifian.org TLS won’t help you if you change your domain name. How will people know if it’s really you? Maybe that’s not the biggest problem for something with such low stakes as twtxt, but it’s a reasonable concern that could be solved using signatures from an unchanging cryptographic key.

This idea is the basis of Nostr. Notes can be posted to many relays and every note is signed with your private key. It doesn’t matter where you get the note from, your client can verify its authenticity. That way, relays don’t need to be trusted.

I’m still alive ! Here’s a quick, brainless recap dump before I switch back to the other side:

• Been daily driving FreeBSD on the o(ther)ld machine for the last couple of days.
  
• Read through the handbook, played around with jails, pulled on my hair because of network issues (I think I might have maybe fixed that) … etc.
  
• Still procrastinating over migrating my Jenny/Mutt setup out there. until then, I’ll be getting my Twtxt fix reading through conversations over on the twtxt.net ✌
  
• Gave a couple of Nostr based platforms a try, it was … not for me to say the least.
  
• Started learning Emacs (I know, I’m in trouble LOL) and might even start twtin’ from there instead.

Seriously, where is the suckless-style Nostr client?

I love this website
nostr

*chuckles
Is this the future of the web they brag about?