"There is a Remnant there that you know nothing about. They are obscure, unorganized, inarticulate, each one rubbing along as best he can. They need to be encouraged and braced up because when everything has gone completely to the dogs, they are the ones who will come back and build up a new society; and meanwhile, your preaching will reassure them and keep them hanging on. Your job is to take care of the Remnant, so be off now and set about it." https://mises.org/mises-daily/isaiahs-job

after delving into the outbox model ( https://mikedilger.com/gossip-model/ ) I'm realizing it is much simpler than I thought, and makes perfect sense. thank you @Mike Dilger ☑️ for pushing this through. if you are working with nostr clients, this should be on your reading list

nostr will be the seed for our time's Republic of Letters

Republic of Letters - Wikipedia

gm 🌄 ☕ humanity is onboarding to bitcoin and nostr, this makes the future brighter than the past. but the present is brightest of all, because we are lucky enough to be here, at this time, realizing that future is ours to build.

what is the best practice for nostr CLIs accessing nsec's?

I'm pulling in RSS feeds and publishing articles for each item. when I do so, I set the published_at date to the same as that of the RSS item, but leave the created_at date on the event to be the present. this seems like the most protocol-respector way of doing it. but now I am running into the pain of returning articles from a certain date, filters can generally be made to apply to the presence or absence of tags, but not "since" or "until" type of operations on the "published_at" tag. tl;dr - are there any obvious drawbacks to back-dating the events so I can filter appropriately at the relay layer?