I wrote a simple nostr relay that can be accessed via a pkdns domain. It automatically creates a pkarr domain and publishes it on the DHT.
https://gitlab.com/cipres/ssnrelay
The goal is to be able to setup a relay without having to rely on ICANN which is a corrupt system. The relay's websocket URL looks something like this:
wss://9zbr9pp1pkpqdwugzny9o8uuo9yjenc1dxt6gwpwaqxg8qg5omxo
I'm a beginner in Rust but it runs :)
Hello. Pubky and pkarr are great. I wrote a small nostr relay that publishes the relay's address as a pkarr domain: https://gitlab.com/cipres/ssnrelay
i think there's great potential in combining nostr and pkarr.
I customized rnostr so that the nostr relay can be accessed via a pkdns domain. I think it'd be nice if nostr relays didn't depend so much on DNS ...
https://gitlab.com/cipres/ssnrelay
"This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface."
Ok i understand, thanks for the update. Are there many people downloading and using the flatpak ? I'll migrate the data files and use the AppImage, no problem.
Wish i could help, i have some experience with flatpak but not so much with Rust. Good luck 🙏
I ended up compiling it with cargo because the AppImage needs a glibc>=2.32 (i have glibc 2.31). I copied the user data from gossip's flatpak dir (~/.var/app/com.mikedilger/gossip) into ~/.local/share/gossip but when i start it, it ignores the config and shows the dialog to create a new key.
I'll stay on 0.11.3 for now until i figure out how to properly migrate my existing gossip data files.
The "cargo fetch" call fails, can't find the Cargo.toml file. I'll figure it out.
Running: cargo --offline fetch
error: could not find `Cargo.toml` in `/run/build/gossip` or any parent directory
I've changed the org.freedesktop.Platform runtime req version to 24.08 in the manifest and i pulled the latest rust-stable flatpak sdk (also 24.08)
I've found out the problem ... by adding a "rustc -V" command in the manifest's build-commands at the top, i can see which rust version the flatpak env is using.
When you use org.freedesktop.Platform v22.08, the rust version is 1.72.0. If you use v23.08, the rust version is 1.77.2. And if you use v24.08 (the latest), the rust version is 1.81.0.
So setting "runtime-version" to "24.08" in the flatpak manifest should fix the flatpak build problem !
The newly installed interior minister in France recently declared that the rule of law is neither "intangible" nor "sacred". His comment triggered outrage even in his political party.
Basically he's saying that the principle of equality of all citizens before the law, the idea that the state has to follow the law, well that's not set in stone, we're going to get rid of it actually ...
It's too bad that Aether didn't become more popular, it worked great but didn't get the recognition it deserved , it's pretty much inactive nowadays ...
https://getaether.net/
Well, you better be prepared then because microchips formed by intelligent self-assembling nanotechnology can already do just that, and many many humans have already been transformed without knowing it (guess how and when ?) ... Think nanobots (builders) rather than implant. The main limitation is the energy that these chips can use from the host.
Hello and thank you for Gossip, it's a fantastic client, very smooth.
I'm using the flatpak build and the first time i ran it, there was an error "/dev/dri/card0: permission denied" and it didn't start, so i had to run this command to change the flatpak permissions for dri:
flatpak override --user --device=dri com.mikedilger.gossip
I've searched gossip's github issues and didn't see this problem reported, i'll open an issue.
Oddbean new post about login | logout
Notes by Catomizer | export