Subnostr

protocols evolve... you don't need to use HTTP/3 + QUIC which is wayyy more complicated than HTTP 1.0. I still use http 1.0 in some C projects, doesn't mean we can't strive to build faster and more efficient versions of something.

jb55 1y ago

many clients, relays, and libraries have already implemented it. must not be that difficult to do? I haven't tried yet.

Reply to this note

Please Login to reply.

Discussion

semisol 1y ago

and newer versions interoperate too…

Colby Serpa 1y ago

Libp2p helps a ton. We’ll be releasing a dev kit soon like NDK that makes it easier for developers to utilize it for nostr.

jb55 1y ago

does it actually work?

Melvin Carvalho 1y ago

badly

Colby Serpa 1y ago

Lol

jb55 1y ago

I've seen libp2p around but I've always been skeptical, I guess I could try it for myself and see.

Colby Serpa 1y ago

Once HDK is ready it’ll be a lot easier for you to use it without as much manual setup. It offers noise as well! https://github.com/HORNET-Storage/HDK-Nostr-Go

Colby Serpa 1y ago

We aren’t building HDK for iOS yet (maybe one day if we’re lucky).

Not sure what the best approach would be for libp2p in Damus. I found this swift version of libp2p, but it doesn’t have QUIC support yet (it’s on their to-do list):

https://github.com/swift-libp2p

jb55 1y ago

was gonna try https://github.com/libp2p/rust-libp2p in notedeck as an experiment

Colby Serpa 1y ago

nice that definitely has QUIC support!

At least they have noise for iOS: https://github.com/swift-libp2p/swift-libp2p-noise

Colby Serpa 1y ago

Yeah, allows many other transports too. It’s integrated into the Nostrbox app I demoed at Nostradia. Will be releasing Nostrbox soon! So close. nostr:npub1ms9ujlulcgtpqn2uzpvhplee9l5kjg8jgqhrwmgutg0n7xk43nqq07qa0v

Colby Serpa 1y ago

Nostrasia*

Sorry it’s cold outside lol my thumbs are frozen