Real kids get shit done

One doesn’t simply panic

Sad that I missed it. My phone doesn’t have signal and I am afraid to be lost lol. See some of you in Japan.

So tired that I passed out in hotel.

This is amusing but WTF?

Where are you guys hangout in Amsterdam? I am transit here so I have the night to hangout! nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub17plqkxhsv66g8quxxc9p5t9mxazzn20m426exqnl8lxnh5a4cdns7jezx0

Yes, religions should not be the universal passport to get by all situations. It’s just one aspect of the person. But on the other hand, I actually don’t personally know many religious people. So I’m curious.

No, I’m not that gay.

Yes, the main difference is the design philosophy here.

The reason I really like & respect nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3xamnwvaz7tmjv4kxz7tpvfkx2tn0wfnszxmhwden5te0vd58y6tnw3cxjmrv9ehx7um5wgcjucm0d5w28rcn is that he will criticize you with real reasons and yet he keeps the human side and say "sorry" afterwards.

I was not even offended by the criticism because good criticism inspires me and even enlightens me. Plus the criticism is about my work instead of personal.

This is a virtue that's lost in many people, even for those who are well educated with a degree.

Just several hours ago, I was criticized by someone for a joke I didn't even say to her (instead, to another dude) solely for her ignorance of humour and bad emotional control. Last month, I was also criticized (or rather insulted) by some PhD dude solely because my action was not aligned with his belief & value systems. But I did not even harm him.

A strong rational critism won't hurt me, yet a weak personal attack just breaks my heart (a little bit).

These kind of people will never admit they were wrong. If facts came out, they would just ignore facts and attach you personally. Actually, they just attack you personally from the beginning.

Sometimes it's not even about right or wrong, it's about being human and have empathy.

Nostr platform, at least now, has been the best platform in terms of public social behaviors of human being. We are free & strong here, but we are not chaotic assholes.

The fiat system does not only fuck your money, it also fucks your mind. It traps you in this rat race mentality that you easily make other people your imaginary enermies. Because the fiat system makes you weak so that you don't even dare to see & admit the real enermy because the real enermy is strong and will punish you. Criticising another person & attacking their humanity might make you feel good, but it will never solve your life problems. Even if you win the rat race, you are still a rat. I don't race with rat.

nostr:nevent1qqsdcgyej4ryarrkr890uskzwdwjky8wyrl9wfvamsf7frd5w2fr65qpz3mhxue69uhhyetvv9ujuerpd46hxtnfduvpmcyz

It was 4am yesterday and my brain was dead. Looking back at the conversation, we (you and me and other devs) should definitely work together. But we need to have a rough consensus about what it means to be working together. NIP discussion, codebase etc.

But even before any of these material outputs, we need to figure out what each client dev is trying to do at the first place.

We need to figure out the product difference and similarity among clients. Sometimes, one client, Blowater for instance, might just have very different design goals.

But I can't be certain because we never discussed our design goal, product goal and potentially business goals.

Therefore, 2 suggestions:

1. We should definitely have an in-depth disussion in Tokyo.

2. We should (or mostly I shoud) engage in more public discussions about product designs.

Regarding feature richness, you are right. The current state of Blowater's GM is poor and it's intentional.

The core design is extensible enough to implement many useful and interesting or even weird features on top of it. But in terms of user experience research, I would like to be conservative and only let users to do minimal features at first. Once we have a solid foundation, we will be more confident to implement more features, progressively.

And I firmly believe that Release Small & Release Fast is a superior approach than a longer up-front design circle.

The receipt that the JP embassy counselor gave me was signed in traditional calligraphy!? Are all JP people this much well learned or JP has a very high standard for public officials? The characters look so beautiful.

Rabbit soup is GOAT

Any Nostriches in Munich?

We can definitely work together. So much work and I need some rest

I am not offended and the point of hacking ahead is to understand the problem space. There are many features that I have discussed with nostr:npub14kcnaaguwqww5cac9m2p755g8z0ugpg7zzcnczll5al86cwfj67sjk2chk but we don’t have enough engineering power to implement just yet.

Since group chat is a feature that we will implement anyway, at least from my perspective, it’s more prioritized to get the common UX right before finalizing any particular implementation.

I also need to refactor the code base to a state that implementing group chat is possible.

So even if Blowater ends up throwing away all current implementation, the effort is not wasted.

What is Nostr-in-Nostr?

https://blowater.app has 154 files, averaging 100 lines of code per file.

I'm a small file, large number kind of dev.

What about your project?

There isn't a NIP yet.

My methodology is to get UX right first, the implementation can be changed later. The problem with writing a NIP up front is that the design was changing during our implementation. Reviewing a NIP without real software to try out slows the whole community down. Writing a NIP after implementation also means now we understand much deeper about the problem. The NIP later on will be better quality.

nostr:nprofile1qqsverg89m7ucem0ewkpfakddqj7ms6hde27k7r292t4acp556szdjcpp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqscamnwvaz7tmzwf3zu6t0g2ep0q will write a NIP or at least that's what she proposed during the meeting LOL.

nostr:nprofile1qqs2mvf775w8q882vwuza4ql22yr387yq50ppvfup0l6wlnav8yed0gpr4mhxue69uhhyetvv9ujumn0wd68ytnhd9ex2erwv46zu6nsqyxhwumn8ghj7mn0wvhxcmmvqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsxwfdau still needs to finish up some UI. But the logic is already in the production, we just hide the UI.

The plan is to release this feature for testing by the end of Friday and then Sherry or I will draft a NIP.

If we are productive, we can release it on Wednsday.

The implementation is very similar to NIP-87. Some details are different. For example, meta data leakage is much smaller. Group members are not tagged.

I might consider switching to gift-wrapped event after some examination.

NIP-112 is way to big.

The key features in my design is that:

1. only use one kind

Creation, invitation, acceptance, message are all the same kind. Their data are all encrypted. Only after encryption, the receipient will know what kind of group event it is.

2. Minimal metadata leakage. Only receipient or group key are tagged. All other metadata are encrypted.

One obvious problem with gift wrap or similar approach is that authenticated relay might have a hard time.

Unless authenticated relays use a separate auth-token instead of pubkeys to identify users.