Sorry but let me say goodbye MinIO. You were a icon of the freedom. Now I shutdown it and lanched RustFS to testing Bucket Sync.
Oh my goodness, That's strange English. I'm posting on my X or an another Nostr Japanese account, you see.
If this English account isn't gaining traction, the Japanese account is posting on X.
The Japanese account is here.
npub1azzj0dzw8evwtgyjeucyfz5cs8k0eg7rd0x4qvggcg3s7lx0dmaqv9sfka
Now that I've finally started my year-end holiday, I think it's about time I got on with various things.
There is no particular significance to it, but I have switched the address for the Wallet of Satoshi to one under self-custody.
https://pouchdb.com/errors.html#event_emitter_limit
Possibly in design?
https://github.com/pouchdb/pouchdb/issues/3848
Maybe related.
Hmmm... very deep...
I have realised that Openvibe only posts to a single relay in while. Move to Nostur temporary.
Hopefully, there is a web client that is easy to use with multiple accounts and easy to use on iOS.
Come to think of it, I have set up a job on my server to periodically fetch posts from Nostr and dump them into a file. Might just put this on my site. That way, release note announcements and such would be accessible to everyone via HTTP.
Though you will probably get some pointless ramblings thrown in too.
Now I am going to reply to issues on GitHub because I have a bit of free time.
I realised that my family has already departed. Do not worry, I will catch them in the afternoons.
Of course, I am going to continue to study for the next exam. Day by day.
I suppose I was in a mildly manic state, I thought to myself.
Right now, I AM feeling rather humble.
As the pain from failing the exam gradually sank in, I went and released a quite large Self-hosted LiveSync update.
This is an UI refabuish update. And P2P sync get more robust, several bigs were fixed. Well done.
I have been worried about it lately; the Professional Engineer (JP) exam I took this summer. I have been given another chance to sit it next year (in other words...)
I must not let it go to waste again -- I shall have to knuckle down!
Work commitments mean I have not quite been able to fully commit to OSS yet, but I expect to be back up and running again soon. Thank you all for waiting.
Besides, this knowledge and experience will not go to waste.
I am now waiting for the results of the second-level exam for the (JP) Professional Engineer... I took the exam this summer. And finally, we will get the results of the 4th, Nov. Soooo long time.
And if I have passed this, the final trial; the Oral Exam will be held within a month. So hard exam but I think that it has a value and worth.
Self-hosted LiveSync 0.25.23.beta1 has been released!
https://github.com/vrtmrz/obsidian-livesync/releases/tag/0.25.23.beta1
New screens will be ready in a few days!
I planned to do a bit task today, but to sleepy. I am going to go to bed.
The thing is, the end of the first half has not been finalised this year.
Just another half-day's work and the onboarding for Self-hosted LiveSync will be significantly improved. Rebuilds and such should also become much clearer. Stay tuned!
The problem is, I just can't find that half-day.
Possibly, it is dependent on that I am not completely lived in the Web scene. That because I made content viewer, control panels, and embedded UI, even though I made a web service now this days. May this real is kept in mind of them. The server side framework must be completely optional and should be chosen by users.
I was deeply impressed by Svelte 5 rune mode, in its compiled codes. Very efficient. And I am also loving its design — the compiler. SolidJS is another awesome solutions, but Svelte 5 is a good balanced ‘compiler’ with by explicit signal control. I think that Svelte’s website should completely separate the SvelteKit from Svelte in site level. We still need the pure UI framework.
Beyond the onboarding experience of Self-hostef LiveSync, I'm also rebuilding Fetch and Rebuild, as they're overly method-focused and the purpose isn't clear.
In other words, simply select your situation and methods will be suggested.
By the way, I'm cross-posting to Mastodon and Nostr, but everyone needs both of these, right?
Perhaps my daily posts are a nuisance? Should I tag releases with #releasesls?
I am taking it seriously, you know.
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.
Hnn... Should I fix the setting dialogue? Especially P2P Sync. I would love to enhance and improve this feature.
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).