If Bluesky is open, why do I need an invite?

Is there a Nostr client that ensures publication to all "my" relays? It seems, no matter what I use (tried iris, snort and damus), that my text notes are never published reliably.

How did you start your last commercial project?

LinkedIn - Pure dread Twitter - Pure rage Nostr - Pure FOMO

Just published a usable if not feature complete tool to publish Nostr long-form notes! So much to do!

longpub

I just realized that my notes of the last 4 days were never sent, though it seemed like it, since they were held in local storage. Even resending them did not help. Since they were immaterial, I just reset the app (had +4gb data stored). Some indicator for whether notes are "uploaded" or sth. would be cool. #[0]

Having built JS apps for a while now, I can safely say that esbuild is easily my favourite build tool. I also really liked Parcel, but could never make anything work with Webpack.

Switched from sitemap to atom xml, so I can add first publication date and title to url and last update, and use the whole as a cache for state hydrated by long-form notes.

Caddy server markdown rendering and nostr long-form notes are a very nice combo. (Now fully) working implementation:

GitHub

GitHub - canostrical/blogsync: Sync long-form Nostr notes to a local folder.

Sync long-form Nostr notes to a local folder. Contribute to canostrical/blogsync development by creating an account on GitHub.

I want to sync long-form note markdown to a folder and serve it with Caddy. The syncing part feels easier than the Caddy config. Have a look at the first draft: https://github.com/canostrical/blogsync! Working Caddy config hopefully coming soon.

Software is often built by people not using it themselves. Maybe too often.

"Editing" long-form nostr text notes, how would one approach that?

Should Google index nostr notes?