Christian Bitcoiner and developer of Coracle and Flotilla. Learn more at flotilla.social.
Recent Notes (10)
10
KIND 1 / NOTES
Note
One of the generalities most often noted about Americans is that we are a restless, a dissatisfied, a searching ppeople. We bridle and buck under failure, and we go mad with dissatisfaction in the face of success. We spend our time searching for security, and hate it when we get it.
Flotilla 1.15.0 is out, along with a new version of caravel that brings everything zooid used to do into a single monolithic binary. This makes hosting community-oriented relays much easier — there's now only one service to manage, and it's all written in rust.
Changes:
* Redesign threads with a board view, search, and related threads * Suggest existing answers while composing a thread * Schedule posts for later * Show a note's stats, with a histogram of interactions * Manage members and invites from one dialog * Jump from a search result to the exact message * Store events in an on-device database instead of loading a cache into memory * Read an article from outside your spaces on a page of its own * Upload space and room images to the space's media server * Log in to a space without waiting on relay authentication * Fix replies counted twice, threads scrolling themselves to the bottom, and feeds leaving gaps in cached history
it's possible my IP will get blocked, but relays have to protect against spam anyhow. At any rate, this won't get blocked by small inbox/outbox relays, because not a lot of events will get published there.
I have seen nostropus, for the longest time I thought this was something for clients to fix (and I still do, clients can auth as their users). For primal and damus, they already do rate limiting, so I think this will be ok, especially since I've set it up to be very respectful with limits. But maybe my IP will get banned, who knows.
Are there any relay implementations that accept events with created_at in the future and hold them until they're in the past? Bonus points for serving them to the event's author so users can see a queue of scheduled notes.
Sure, but how does it work? There's no source code, and the site just makes a bunch of claims without explaining them. I've always found nostr.land weird to work with too — it's pretty restrictive, and I have no mental model for what it's supposed to be able to do.
Just put together a small project for helping heal the nostr network. This is a follow up to my `canoe` project, which is a personal relay that actively replicates events across your inbox/outbox relays.
Snorkel is a daemon that crawls the network, replicating a random pubkey's events between their outbox/inbox relays every few seconds. It's less reliable, because a lot of relays block unauthenticated users (like nostr.land), but it should really help with deliverability and lost notes.
It's intended to run in the background with reasonably low resource usages, syncing ~100k profiles per day. If you want to run one, it's a good way to contribute to healing the network for people with poor relay selections, or who haven't migrated their events.
