Subnostr

what does LogSeq use protocol-wise?

Well predominately it's a local application. I believe as far as transmitting these pages across the web, it's limited to third-party applications. Somewhere in my notes I have collected some of these tools. There are bridges from LogSeq to other editors and so on. It's a bit of a complex position, but there is no protocol with LogSeq. Merely a proprietary backend that connects with their central server ecosystem, for users who want that.

They released an open source build of their frontend at one point which some people have run with in creating parallel apps.

Reply to this note

Please Login to reply.

Discussion

jb55 1y ago

I was thinking more in terms of data formats

Tekkadan, ゲロゲロ! 🐸 1y ago

I can say the application is predominately written in Clojure. I don't know much about how it really works, unfortunately. I can say there is quite a bit of discussion online about LogSeq and its history.. believe the devs still post semi-regular (quarterly maybe) updates..

Tekkadan, ゲロゲロ! 🐸 1y ago

I battle the idea of using VSCodium or an IDE as a backend. There is a demand amongst these apps to flow between the "LogSeq experience" and the Hypertext Markup experience provided by long-form text editors. I'm convinced no one has successfully offered a fluid combination of both.

An application like NoteDeck can of course be forked and specially designed around these concepts. I am basically following in your path to some extent for now, because I'm not a rust developer and struggle to get great results for being a novice.

In practice, I'm learning a lot of good skills trying to work out a client with Rust-Nostr built with Bun,sh / Buntralino, but it feels futile to essentially copy NoteDeck in a different environment. However, I don't think it's pointless, because I think different Nostr applications in the future will desire different frameworks. I'm hoping to set a standard for local-forward apps which most Nostr clients have not approached..

But- Rust-Nostr works very well. And is seemingly one of the more approachable libraries, so I want to thank you for working on it nonetheless. Hopefully I can contribute to some documentation once I get more comfortable with it.