we can make a kind-whatever for blog posts, but I was thinking it would be desirable to have branle and other clients display blog posts too.

maybe there could be a very lightweight relay people could host at their domain. the relay would only take events from themselves. and then it could do react + some server-side-rendering thing for HTTP requests for requests at `domain.name/post/`.

Would a Nostr-powered blogging platform be interesting? How would that look like?

nevermind, I've confused https://teletype.in with https://telegra.ph.

this writefreely things looks good. I may use it too.

I thought Telegram was uncensorable and the friend of everybody who was against Putin.

no

consigo.

I was thinking about basically that: https://github.com/fiatjaf/nostr/pull/43

if you want to blame me for this, I consider yourself blamed for not developing a different client and calling on me and my broken code.

all mnemonics will die because branle was generating them wrongly.

yes, I have an idea for it. but there are different ways to implement, none of them super reliable, but I think it will work.

it does not. we'll implement ways of properly tagging people, but there are no universal readable names, so it won't be as smooth as twitter. we'll tag keys, but they can be aliased to known local names, or to names based on DNS and other optional external sources.

maybe it was pouchdb and indexeddb having their storage DOM glitches?

not worker pouch because that didn't work, but a manual webworker implementation is ready and deployed.

alex berenson now has a slack. what a weird world.

are you planning on tackling one of these?

but there is also a weird lag thing that I bet is coming from indexeddb. I'll try to solve it with https://github.com/pouchdb-community/worker-pouch

it's just a sorting error. this is what happens when you try to write your own stream sorting algorithm.

koty?