I was no longer able to contribute to Kilikili due to academic stuff.
And jiehuan is struggling with the new releases.
Because there is a guy who exaggeratedly promoted his 3rd-party QQ (a IM like the green you-know-what[1] app) server for Windows Mobile which is more unsafe than the you-know-what[2] server, for that everyone who open his website will be able to control previous user's account.
The guy also made an app market which integrates Netease Cloud Music, Tiktok (Chinese ver.) and Bilibili player.
Nearly all his works were based on AI and were made in a short period of time which made jiehuan really frustrated.
It is obvious that WM development is much easier than that on J2ME. To design UI for WM apps, just drag controls like ComboBox and Buttons to the WinForm in the designer, while J2ME without and 3rd-party library requires the developer to declare the UI components with Java code. And C# on WM have encapsuled multiple useful tools, while you have to implement them by yourself on J2ME.
Kilikili is facing several severe difficulties including unfinished refactoring and API coupling. Online playback function is widely urged to be added, which requires codec convertion, while jiehuan's transcoding server has a small upload speed at ~10M, which made him concerning about the possibility to handle online playback with coreplayer via m3u files.
Endless concern and hopelessness are spinning in my mind, just because I am well aware of this all while I cannot make even a tiny bit of difference.
Promising future, 7 Aug 2025
----------------------------------------
[1] The word "WhatsApp" is banned in a specific telegram channel.
[2] WhatsApp Server (https://github.com/NovelProfessor/whatsapp-server) allows you to use WhatsApp on old phones. But those who have access to the server will have access to the users' accounts logged in on the server.