← Feed

Posts

• Post #4309997

  In 2020 the EU's open-source strategy was an internal memo about the Commission's own code. Today's wants Europe to build open alternatives to US proprietary software, and treat them as industrial policy. Good, and long overdue. But it's non-binding, and ~€2B over 7 years is a rounding error next to the ~€264B Europe spends on proprietary software every year. The lever it keeps ignoring is its own procurement budget. https://vikunja.io/changelog/eu-open-source-...

• Post #4309996

  🦙 Vikunja 2.4.0 is out! Ten security fixes (please update soon), the first Vikunja Pro features, and a brand-new v2 API. Full rundown: https://vikunja.io/changelog/vikunja-2.4.0-pro-and-a-new-api

• Post #2650148

  📣 Vikunja now (finally) has help docs for end users! Check it out at the website and tell me what you think: https://vikunja.io/help

• Post #2650147

  PSA: Because of the great recent success, there will be ANOTHER release later today or tomorrow fixing 9 more security vulnerabilities.

• Post #2650146

  🔒 Vikunja 2.2.2 is out: nine security fixes including a critical chain that could expose instance-wide data. Also adds centralized SSRF protection and a few nice bug fixes. Please update soon! (2.2.1 has been released as well but did not fix the issues fully, therefore I went and pushed 2.2.2 right after) https://vikunja.io/changelog/vikunja-v2.2.2-was-released

• Post #1574822

  cal.com closed their source this week, citing AI bug-hunters as the reason. Every time a project does this, someone asks if Vikunja could too. Not easily. AGPL-3, no CLA, no investors, and anyone can fork today's code. More on why: https://vikunja.io/changelog/vikunja-stays-open/

• Post #1266810

  Cal.com announced they're going closed source. The stated reason: AI has made it too easy for attackers to find bugs in public code. I've been thinking about this for a bit. It's security-through-obscurity with a 2026 paint job, and I don't buy it. Kerckhoffs's principle is over a century old: a system should remain secure even when everything about it except the key is public. LLMs don't change the direction, only the speed. AI scans closed cod...

• Post #1099893

  🔒 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 🚀 https://vikunja.io/changelog/vikunja-v2.2.0-was-released

• Post #1099867

  PSA: there will be a release tomorrow (April 8th) or the day after that with a bunch of security fixes

• Post #1099866

  🦙 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

• Post #727329

  @pojntfx@mastodon.social @jonasfranz@gruene.social We have CalDAV support 👀 https://vikunja.io/help/caldav/

• Post #707448

  PSA: The next Vikunja release will fix 10 (!) CVEs. If all goes well, later today or tomorrow.

• Post #598312

  @LilithElina@norden.social @mailbox_org@social.mailbox.org das sollte mit Vikunja ganz gut funktionieren. Für Push-Nachrichten kann ich entweder die Vikunja-App oder die Synchronisation mit Tasks.org empfehlen

• Post #435994

  🎉 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: https://vikunja.io/changelog/vikunja-v2.1.0-was-released/

• Post #385599

  PSA: Vikunja 1.2.0 will be released tomorrow or the day after. It will fix four (!) critical security vulnerabilities.

• Post #249281

  🚀 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! https://vikunja.io/changelog/vikunja-v1.1.0-was-released