@seeker I think there are firmly held opinions about this, but hosting at home is more properly called homelabbing, or, running a homelab. I think there is a big enough difference in what you need to keep in mind between running a server (whatever shape or form) at home vs running apps and services on a VPS or bare metal server, not the least of which is going to be network access and security. That article does make a nice point distinguishing "self-host" OSes from dashboard/docker management systems. I think voting for apps is based more on the fact that enough people have been paying for a commercial version of an app and know about and want to move to an open source alternative. I don't think anyone here is voting for apps they have no familiarity with. That said, seeing what gets suggested has sometimes led me to see which other platforms might already have it (I'm using affine on my runtipi VPS, for example) and I see what the fuss is about there. My curiosity has led me to install runtipi on my Dedirock VPS where I have affine, Obsidian LiveSync, GrampsWeb, FlightLog, and Write-freely. I'd switch them all to Cloudron if these were available here. I've tried almost all the alternatives, and I've stuck with runtipi the longest (despite the stupid name). The rest just always, and I mean ALWAYS, crap out eventually and either the forums or help have been very very weak, or actually non-existent (no one knows what went wrong and how to fix it). Forget them!

@luckow thanks for that, I never checked light mode on the keycloak template Should be fixed!

@robi Still shared plugins, but building on your idea... what if EmDash.mycloudron.com could access EmDashPlugin1.mycloudron.com, EmDashPlugin2.mycloudron.com as isolated Workers? If installing a Worker was as easy as perhaps a LAMP app, we might get isolation. Would need some header finagling to satisfy CORS. It might also be interesting to see if Cloudron could expose a "master" app like EmDash on the front-end, and access the plugin endpoints as API-like endpoints on the back-end.

Which filament did you use for the blue?

Sorry @nebulon, found it on Github. Thinking now it's more of a discussion topic, since we don't know which way you guys are leaning on Multi..

cross-linking: https://forum.cloudron.io/topic/15249/ai-devops-opencode-alternative-to-_claw-bots

New update making it even simpler to code for free. https://forum.cloudron.io/topic/15277/ai-devops-opencode-make-coding-free-with-zen-models-no-claude-openai-google

Thanks @joseph!

@humptydumpty This is a big problem. I was shocked to see that as of 2026, only 4 out of 50 states had passed the "right to repair". But if Chinese AI companies can used "distillation" to create new AI models, then perhaps the same approach could be used to create a digital twin of a tractor and then replace proprietary software with open source software.

@timconsidine what would be the right things to do from your perspective? The recently published Warm Homes Plan and Local Power Plan are both pretty decent IMHO (although still LOTS of room for improvement and not enough details about implementation yet). IMHO there is much MUCH more political corruption related to keeping us all hooked on fossil fuels than there likely ever will be with renewables (which by their very natures are inherently more distributed).

Just added another promising one: Hermes https://forum.cloudron.io/topic/15128/hermes-agent

@humptydumpty Nope, not kidding. You can if you boycot the business packaging that includes the bloat. When I used to game long ago, the games were way more stable and space efficient from 3rd party repacks who ripped out all the bloat making it playable on older hardware too.

@humptydumpty Googling this didn't return any definite answers other than this post and that generic AI response which suggests using N8N and webhooks to monitor such changes and then apply different labels. https://community.vikunja.io/t/auto-tagging-for-projects/1933

@robi good approach, but I suspect your neuro-plasticity far exceeds mine !

@joseph The SEC in America very unfairly blocked Odysee's crypto token from progressing, which basically sunk their business plan. The Free Software protocol behind the Odysee frontend was LBRY. Paid development of the LBRY project was sunk when the SEC made their ruling. The idea was that you could run a local instance of LBRY and that would act as part of the CDN for the frontend (which didn't have to be Odysee.com). The thinking was people would use a LBRY client to view their content and the client in turn would also be serving the same content to other. If you liked the content/supported the channel, by leaving the video on your machine, you would help seed it/improve the CDN. It was a great idea. In practice, most people weren't interested in running the LBRY client. Even politically censored people that Odysee would help most didn't bother with it, amazingly. It is a pity. Odysee Inc. split off from the original project and still goes today. The SEC were most unfair.

Happy New Year to all of you! Many thanks for the great community here and we are very much looking forward to a new year of building much requested features for all of you