So much done today. We are in a series of bug fixes and new features have to wait. 
SSE + POST over http2 is much better than WebSocket.
It comes down to the use case. For a collaborative editing software, yes we need all histories and a branches. But for configurations, it’s probably ok to forget old state and mutations don’t happen that often.
Nothing. Just after 2 months of experience I feel it’s a tech debt instead of asset. Simple set of strings can be implemented standalone.
Yes it’s one of the reasons
nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn Now I consider using auto merge a bad idea because it’s a black box that’s super hard to debug.
Error handling is my favorite part of programming
Replaceable events are mistakes and Blowater will remove all replaceable events usage
The JP trip is, well, I won’t simply describe it as awesome. It has ups and downs. I have experienced the great, the good, the bad and the ugly. No place is perfect and perfection varies for different people.
Now I have removed my imaginary filters about Japan from animations and movies. Having a more realistic view of Japan.
That been said, Japanese Nostr users and developers are awesome. I will learn more Japanese and next time we can have a better conversation in your language.
The kindness of random people on the street always touches me deeply because we will probably only gonna meet once in life and there is no way for me to show gratitude. The only thing I can do for them is to live a better life and possibly make something good that may make their life better in some ways. This is a thought I have from time to time but it’s hard to execute.
Nostr users in Wakayama ？
Legacy fiat bullshit. We the nostrich will create the new standards of our own.
The railway system in Japan is very established and complex. I took the wrong way everyday. I personally am fine with it. It’s a foreign land and mistakes are expected.
I used 3+ booking apps in my trip. Booking is not a protocol yet.
