You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Blinko: reconsider deferral — editor bug was fixed by merged PR #1892 #1924
The Blinko script was deferred in #1696 on June 5th with the comment "Nothing work." The core issue reported by @Virtualchronos ("impossible to write anything") was the editor/text input being completely missing.
The Fix
PR #1892 (merged June 4th — one day before the deferral) fixed this exact problem. The root cause: Blinko's Vditor editor expects its runtime assets (JS, CSS) to be served locally at /dist/js/... and /dist/css/..., but the install/update scripts never copied them from node_modules/vditor/dist/ to the public directory. The fix is two lines:
This is already in the deferred script at ct/deferred/blinko.sh.
My Experience
I've been running Blinko on this LXC script (with the fix) since June 4th — over 10 days now with zero issues:
Editor works perfectly (notes, todos, flash thoughts)
SSO/OIDC via Authentik works
MCP server integration works
Update function works
AI features (embeddings, chat) work
Request
Would you consider re-testing with the fix that's already merged in the deferred script? The deferral happened before anyone tested with PR #1892 applied. Happy to help verify or provide more details.
The script worked better before the PR than after it. Since the PR, it hasn't worked at all, and I've lost interest in the script. Fork the project, push the file, and fix it if you feel like it. It's not worth the effort to me—I easily put 12–16 hours into the tool. Nothing work - Login, Register, Dashboard. I dont understand your message "over 10 days now with zero issues"
The script worked better before the PR than after it. Since the PR, it hasn't worked at all, and I've lost interest in the script. Fork the project, push the file, and fix it if you feel like it. It's not worth the effort to me—I easily put 12–16 hours into the tool. Nothing work - Login, Register, Dashboard. I dont understand your message "over 10 days now with zero issues"
Activity
MickLesk commentedon Jun 15, 2026
The script worked better before the PR than after it. Since the PR, it hasn't worked at all, and I've lost interest in the script. Fork the project, push the file, and fix it if you feel like it. It's not worth the effort to me—I easily put 12–16 hours into the tool. Nothing work - Login, Register, Dashboard. I dont understand your message "over 10 days now with zero issues"