#gossip is simply the only sorta decent desktop app for nostr... i've resigned myself to using coracle and nostrudel because they help me do relay dev and they work pretty good mostly
gossip is overly complex IMO, hard to use, i recommend https://coracle.social to get a really nice intro to this protocol... https://nostrudel.ninja is a more geeky client that lets you poke at lots of things (inside the other stuff section on the sidebar)
also, hi! you are the co-inventor of the Lightning protocol, welcome!
i just want to say, isn't source routing a bitch... the problem of nodes learning the state of the paths on the network... but there's no obvious path routing solution for atomic, anonymous transfers of balance state between nodes to route payments, so it had to be source routed
Thanks!
Yeah I need to learn more about how this works, and I'll try to stick to the desktop / 'self-hosted' stuff if I can.
Right now what seems to work is using a website like iris.to to find replies, then copying the event ID into gossip. With the event ID gossip finds posts and I can reply (like this!)
you just need to figure out the relay configuration
it's too obfuscated for me... gossip is written in Rust so i'm not touching it, and i don't understand how other people figure out how to get it working, it seriously is a several hour episode the one time i got it sorta working, i personally feel that people who use languages like C++ and Rust have their models of reality warped in a way that is difficult for primitive natural minds to decode the output from
fwiw, it's very possible to host nostrudel (or other web clients) locally instead of using it from the author's website
this is what i do, it's simply a static website once built
So like it lives on your device at some ip:port within your browser? I ran sillytavern, that's my only concept of something like that
sometimes you can even get away with file://.../index.html, pointing it at the local output, but not all web apps work that way due to cross-site permission issues
so usually you'd run a local web server and host it from there, either on the same machine or within your LAN
the javascript build systems usually have a webserver built in for developer use; eg "pnpm run dev" will spin up its own webserver locally (see https://github.com/hzrd149/nostrudel?tab=readme-ov-file#running-locally)
Cool, I will try that, then it's also "multi-device" in an easier way than using sshfs for ~/.local/share/gossip :)
oh yeah, you could also use wireguard and host it on a VPS only accessible over wireguard
well, even you could run it on your own home server, if it has a wireguard tunnel to a VPS and you would then be able to access it away from home too
i seriously doubt mike's client can cope with two instances writing to the app DB... that stuff will just be in the browser cache if you run a custom instance of coracle or nostrudel
If you run two instances it won't obviously fail right away, but it wasn't designed or tested. I've run single commands while the UI is running though to no ill effect.
have fun causing race conditions
welcome to the real world of concurrenc networks
this is correct: local state for webapps is stored in the browser, even if you host them locally
i don't think this is easier to sync multi-device than eg gossip's local files
nostrudel does store its settings in a relay-side 30078 event as well, this gives it automatic synchronization of settings between devices, maybe this is enough for what you want
yeah, this is also one of the big hassles with web apps is the web browser doesn't easily let you connect the app to a local cache relay... you could then also connect that cache to wireguard and use the same cache on your other devices as well
to do shared state like this you have to build a separate configuration/cache service
I haven't tried multi device at the same time, yeah I can image that would mess things up. I'm closing gossip on the desktop, then sshfs mounting on a laptop and using that.
Now that you mention, I will probably forget to close it on the laptop at some pont and try accessing both at once and get to see what kind of fun that leads to.
yeah, since you are linked via ssh just do a "killall gossip" before mount
gossip is one of the hardest clients to onboard onto.. it starts to work a lot better as you start following others and also, setup a relay list that includes some mega relays to read from so it can find more replies. the mega clients dont play nice with outbox so people's replies will go to those client run relays instead of the relays you wanted them to reply on. (damus, primal, ..)
Thank you for doing computers the right way and running desktop programs. I'd say you have to stare and hover around the "My Relays" page on Gossip and all its dozens of configurations before it starts to work, but I don't know how it sets up things for you when you first create a keypair through it, maybe it just doesn't set up any relays at all by default? @bu5hm4nn @M. Dilger @dtonon
Try adding relay.damus.io and nos.lol both as read/write/outbox/inbox just to see if it starts to show at least something, then you can tweak it later.
Oh, and set purplepag.es and relay.nos.social as "discover".
In every note there are some buttons on the upper left. One of them is a circled dot. That takes you to the thread view. This shows that note in context of a thread, with it's replies and ancestors. The equals symbol is a menu of things, each with a popup submenu. The eye, when hovered, shows the relays that the event was downloaded from.
There are buttons at the bottom of events too. The chat bubble lets you reply. The refresh arrow lets you repost. The ellipsis lets you quote. The lightning bolt lets you zap a lightning payment to the author. And the heart lets you react with an emoji.