kolaente

Another contribution to the canon.
via @kolaente.de

matduggan.com/i-sold-out-f...

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.

Thanks!

Ohh Zellij looks nice, I'll have to try that!

For the use case you're describing, I found mosh very helpful.

Ha! That would be something.

🦙 Vikunja 1.0 is here!

After 8 years of development and 1,400+ commits of new features and fixes, this milestone release brings LDAP authentication, @user mentions, a completely rebuilt Gantt chart, and S3 storage support.

Check out the full release post to learn more:

vikunja.io/changelog/wh...

A GitHub commit message view showing "kolaente - chore: v1.0.0 release preparations"

this is not a drill

I've seen many Vikunja Forks that are all very AI-smelly since Claude Code exploded a few months ago. Also more contributions which were AI-generated, but not as much low-quality as you might expect.

A workspace overview, showing 6 workspaces each with multiple terminals open.

It's a little crazy how much my workflow has changed with Claude Code.

(I guess I should learn tmux?)

Sounds like it works as intended

GitHub PR view. The Pull requests tab says 2 open PRs, but the filters state "9 open PRs"

okay GitHub, riddle me this

Release v1.0.0-rc4 · go-vikunja/vikunja This is the 5th release candidate of v1.0.0. 272 commits have been made, most of them bug fixes and refactors but also many dependency updates. Some small new features as well, most notably: Valid...

🦙 And now, the 5th rc of the 1.0 release!

272 commits have been made, many bug fixes and a few new features sneaked in as well. I think this time, this was a release without any known bugs at release.

Please test as much as you can and report all the bugs!

github.com/go-vikunja/v...

"Test these new tools, with care, with weeks of work, not in a five minutes test where you can just reinforce your own beliefs."

More quotes:

"Whatever you believe about what the Right Thing should be, you can't control it by refusing what is happening right now. Skipping AI is not going to help you or your career."

Great take by antirez (from redis) about coding in the ai age:

"It does not matter if AI companies will not be able to get their money back and the stock market will crash. All that is irrelevant, in the long run."

antirez.com/news/158

Da habt ihr doch hoffentlich das Fahrgastrechteformular ausgefüllt?

Given how similar this is to Apple's App Store monopoly, I wonder what the DMA has to say about this.

I've switched git hosting providers once with @vikunja.io, and it sure is a lot of work. Git forges are easy to set up, but what really makes a migration difficult is the CI.

3. Because it is a great product, the industry standardized CI around GitHub Actions: The format, the runner, everything.
4. Now, no one can leave realistically and GitHub tightens the screws, leading them to extract more money from their B2B customers.

It really is the Enshittification of GitHub as Cory Doctorow laid it out in his book:

1. GitHub built a great product (GitHub Actions), attracting users of all kinds
2. It gave large parts of the product away for free on public repos which creates adoption - now, all open-source projects use it