Hey, thanks for the response.

I think one of the biggest points to improve on relay implementations is the ease of deployment. Right now, it's still a bit arcane to manage your own relay and a lot of them still rely on docker magic to make them work.

I'm not sure if this is a controversial take but I always view a project's reliance on docker as a sign that it's gone a bit unwieldy and complex. Aside from that, it's also hard and messy to troubleshoot docker containers when things go wrong.

If I'm to ponder about it, my ideal "small group" nostr relay would just be a plain package that someone with little experience can install using their distro's package manager, with standard config files under /etc and a basic rc/systemd script that starts and manages it.

Oh yeah, Paranoid Void is great. I haven't found a lot on them though I really liked their Literary Math album.

I've seen a bunch of nostr relay implementations that focus on high performance, high throughput scenarios.

While those can be great for large public relays, I hope someone takes the torch and makes a simple and easy to deploy relay that focuses on individuals and small groups.

I think modern social media websites warped a lot of people's expectations on data hosting.

This looks uncomfortable to be in.

The word "toxic" carries the same weight as "engineer" nowadays. Haphazardly put on things that represents neither.

One of things that always lingered in the back of my head with Bitcoin is its feasibility for use in interplanetary trade. While the idea of interplanetary trade is still a stuff of science fiction, I think it's a nice brain exercise to ponder on how Bitcoin will adopt to that kind of environment.

I found this fun bitcoin stackexchange thread that asked the same question that I've been mulling over if you are interested in picking apart this question [1].

[1]: https://bitcoin.stackexchange.com/questions/56480/is-it-possible-to-use-bitcoin-as-interplanetary-money-store-of-value

Lol, they're cutting themselves in the knee.

It would be nice if the people who develop clients for Nostr would break the mold and make those "dark features" optional or, even better, remove it entirely from their clients.

I finally got myself to upgrade postgres on my relay box. It was supposed to be a quick job but a mistake on one of the commands made it longer than it should have been.

Either way, it's all good now.

Why do "modern" websites do this?

I personally think that marriage and, subsequently, raising children will inevitably give you a lower time preference. I don't think any dude who decides to marry a woman with the intent to raise children with her wants instant gratification for doing so.

Yes.

2.

I think manpages, especially OpenBSD manpages, are one of the most useful parts of a UNIX-like system.

Yeah. Thanks for bringing that up. I think the main issue once relays start banning people for their speech is alternative relay discoverability. For example, if the sysop of nostr.band bans me we wouldn't be able to communicate since it's the only relay that we have in common.

It would be nice to have an immutable list of relays that currently exist. Probably something like the PGP keyserver protocol where a sysop can submit their relay address signed with their npubs. The keyservers can then share their contents with each other to make the records uncensorable.

That hypothetical protocol could also probably borrow the idea of revocation certificates to remove a old relay record in the server.

That can be a potential issue if Nostr centralizes to a few large relays. As long as it's possible to run your own relay and that there are people run relays that like the idea of free speech, I don't think you'll have any issues.

No, I mean if a relay blocks you what's stopping you from going to another one or making one?

How can you be banned on Nostr?

Spartan is a nice, lightweight document transfer protocol that removes some of Gemini's fluff while retaining the ability to use gemtext markup and its niceties.

It also doesn't require a TLS certificate to function properly. While this makes the protocol a little less secure, it makes up for it by reducing the amount of complexity when hosting and maintaining a site.

You can learn more about spartan by going to the protocol author's gemini page [1].

[1] gemini://spartan.mozz.us