Transparency trades "bugs found later by the wrong people" for "bugs found earlier by the right ones."
The full argument, including why Vikunja staying open is more than a personal promise: vikunja.io/changelog/vi...
Ok @kolaente.de shared the most perfect Claude skill with me (I think it’s even better than my /asshole skill): /caveman github.com/JuliusBrusse...
Grug brained me very appreciate caveman
Weirdly accurate
🦙 Vikunja 2.3.0 is out! 11 security fixes, a new plugin system, quick-entry window for the desktop app, Vikunja as an OAuth 2.0 provider, WeKan + CSV imports, and more across 277 commits. Updating soon is highly reccomended!
https://vikunja.io/changelog/whats-new-in-vikunja-2.3.0
Claude is always either "I've committed and force-pushed this change to main lol" or "hark, oh gracious and benevolent liege! Wouldst thou deign to cast thine noble gaze upon the orthography of this 'ere humble commit message, that it might be judged meet and proper in thine eyes?"
Seems like I'm not the only one who feels like that:
lwn.net/Articles/106...
I love how OpenAI has just today closed their largest round of funding EVER (maybe the largest round of funding in all of VC history?) yet no one seems to talk about it because Claude's source code was leaked 🙃
I just want to get back to building features and developing the product, but I keep spending a huge portion of my time fixing bugs and security issues. Important, but not as much fun as the other things.
Don't get me wrong, finding security issues is great. Having pentest-level reviews with much less effort is even better, because then you can do it all the time and catch vulnerabilities before the code lands in production.
I have a feeling that there are people out there building AI-powered automated security scanners and testing them on Vikunja's codebase - which is great, but a little more coordination would be welcome.
🔒 Vikunja 2.2.0 is out! 10 security fixes (update now!), plus task duplication, an improved Gantt chart with subtask hierarchy & dependency arrows, and user-level webhooks. 237 commits of goodness 🚀
vikunja.io/changelog/vi...
I have an open source software joke but it's critically under-resourced
I've been thinking of adding support for Vikunja as a storage layer to Beans - I feel like that would solve the UI part. Would you be open to exploring this?
PSA: The next Vikunja release will fix 10 (!) CVEs. If all goes well, later today or tomorrow.
The worst thing about AI is that all of social media is now entirely consumed by the discourse: one third people heralding machine Jesus, one third people uttering nonsense takes like "it's good, but not perfect; thus it's bad", and one third people wishing literal death upon you. I'm tired.
Well of course I'm not using any of that 🙃
I have recently configured e18e (of course without having spent any time configuring it) and it seems to get confused that I have a frontend and a desktop (electron) in the same repo that have some of the same dependencies - it always warns me about duplicates. Not sure what to do there?
One with customers who are using the thing and a full backlog 😅
Thanks! Happy to answer any questions about it.
I mean Vue is great
(and rewriting everything is not really something I want to do right now)
🎉 Just two days after the last release, Vikunja 2.1.0 is now released!
🔒 Fixes a security issue with password reset tokens and adds a nice touch: checklist indicators now turn green when all items are done!
Check out the full release post on the website: vikunja.io/changelog/vi...
PSA: Vikunja 1.2.0 will be released tomorrow or the day after. It will fix four (!) critical security vulnerabilities.
You can also force this by just telling it "use sub agents to split this up". Really useful if you're implementing a long plan that would otherwise fill up the context of the main agent quickly
Oh! I love it!
Mein Einstieg in den monatlichen #DigitalIndependenceDay: Ich habe Trello ersetzt durch Open-Source @vikunja.io (& automatisiert via @n8n.io), selbst gehostet auf einem kleinen gemieteten Server in 🇩🇪.
Hier geht's zur 🦙 Website vikunja.io/support/, und hier zum Macher: @kolaente.de.
#DIDit #diday
🚀 Vikunja 1.1.0 is out!
🔒 Includes a security fix! Also: 🆕 S3 signing config, webhook Basic Auth, smarter date parsing & more fixes.
Upgrade highly recommended!
vikunja.io/changelog/vi...
Vikunja has Kanban with cover images (and a bunch more but you disable it all and only use the Kanban board). There's a demo on the website that you can use without creating an account to see it in action!
Should I open an issue about a beans integration to discuss this more?
Check out @vikunja.io (Shameless plug, I'm building this). Happy to answer any questions!
I also thought about building a beans integration for it but haven't explored that idea more - if that's something you'd be open for, happy to talk more about it.
Generating code was never the goal. The goal was to solve problems. I tried my best to avoid writing code by leveraging existing solutions or reframing the problem.
Writing code was always a last resort and a liability. If I was going to write code, then I was going to do it right.