You’ve given me a clearer and more reasonable explanation of why chat might be necessary for Anytype’s sustainable future. Thank you.
Edit:
That’s not really my point. What I’m concerned about is that the maintenance burden is getting heavier with the addition of chat, which could further delay existing issues.
Chinese, Korean (and likely Japanese) users continue to face basic usability problems with their languages in Anytype. These issues rarely affect Western users, but Asian users encounter them constantly:
- When searching in Chinese within properties of type 'object', some objects cannot be found when only 1-2 characters are entered
- Link Underline Misaligned After Inserting Preceding Chinese Characters
- Commands in editors not working when using Mac using IME Chinese Changjie - #5 by Angelo
- Using WeType and there is an extra space after enter a number and then change the line
I don’t believe these input issues are tied to Editor 2.0 or AnyStore. They should be fixable without waiting for either of those projects. Yet all of them have been consistently underrated—even before chat was introduced—and will likely be pushed even further down the priority list by Editor 2.0 and chat.
Given the pervasive censorship and authoritarian environments in several Asian countries, I don’t understand why Anytype isn’t paying closer attention to the voices of Asian users. Asia has a massive population of sovereignty-aware audiences, and these users are exactly the ones who stand to benefit the most from what Anytype claims to offer.