I try not to look at GitHub at night because I tend to make more irregular comments, but lately work has been so, and then at this time (0:19 JST). And I end up saying some rather outrageous things. It would be good if there was some way to express priorities of issue opening. Anyway, I would love to see mates using the issue template, though.
I wrote a paper of peer-to-peer synchronisation without central signalling server (but using Nostr relay, you know P2P Replication of Self-hosted LiveSync). But I have quite afraid about an APC. Hence I shall post it as a poster on a study group of some SIG. I wish there were a discount for the individual researcher. (Now I am not on R&D, but backed on the System-Solution dept).
And, to be honest, I still have a bit of an aversion to English (especially chat-like-text-conversations), but no trials make no progress. I try to write something (really something). However, mobile-Grammarly had been quite bad after they discontinued the keyboard on Android.
Some issues suggest that the onboarding experience is quite bad. You know, this feature has been around since before QR Code setup existed, so it is rather unhelpful for subsequent devices. And I am so afraid that some people may not know that feature.
Therefore, I am completely rewriting this now!
Ah! Almost forgot!
Uint8Array.fromBase64/toBase64 has been promoted to Stage 4, therefore I have implemented it in Self-hosted LiveSync via octagonal-wheels!
Compared to previous implementations, it shows about 10x faster benchmark performance, and I think it seems that the likelihood of being caught by watchdog or OOM errors has decreased significantly.
๐.md
Now available; Self-hosted LiveSync v0.25.19!
