@robi Yes! Or use a service with an "OpenAI compatible" API, e.g. https://gab.ai In any case, please add me to this growing list of "we want Karakeep" people. Thank you to @jagan too for so wholeheartedly recommending this application. I remember when somebody got me onto Shaarli! I was delighted. Then @timeconsidine tuned me onto Linkwarden, which was a bit more advanced. Hearing @jagan raving about how it helps tidy up your notes, well, I just want to try this. I hope we support it soon.

No, teams will be a separate package, which will still take a few weeks, but it will come!

@sock_check_foo said: "private, affordable, self hostable alternative to Notion" I'm holding out hope for Docs https://forum.cloudron.io/post/103461

Still wish there was a way to self-host an annotating the web solution.

@stalecontext very cool. How are you liking it apart from the sticks and glue?

So, feeling stupid (more than normal) for starting with ZNC (Zeronet Conservancy), ZNX (ZeronetX) is now packaged. Ignoring the vagaries of P2P and Tor, this does seem to be viable. Git repo : https://git.cloudron.io/timconsidine/cloudron-zeronet (same) has been refactored into 2 folders, ZNC just in case someone feels they want to take it over / use as a base, and ZNX. Docker image: tcmbp132021/cloudron-zeronet:v3.0.0 ZNX actually allows an ID to be created and ZNX-leaning sites seem to be alive. I absolutely see the value of Zeronet for different uses, including hiding in plain sight (for legitimate reasons), and it seems usable enough. Old/abandoned/un-peered sites can be ignored. Set up active sites. Haven't yet found a site to promote relocation of No.10 / Millbank PHQ to central Tehran, but I will keep looking.

@luckow well seems to me it is docker hub access issue, not an app issue. My ping was via cloudflare and IPV4 Yours seem ipv6 and direct. No idea why either difference would be a blocker. I’ll try some diagnosis

Hello @bitbound Thank you very much. I have added you to the group.

@timconsidine Don't love the templates. Love the Discard.

@girish nextcloud federates, too.

Looks great! +1 for this app

Maybe I am slow on the uptake, but I have only just realised the impact which AGENT.md and SOUL.md have on the behaviour of the bot. Well, I knew it in theory, but I did not do "2+2". Significant customisation possible, and because those files (and others) are deployed to /app/data/.nanobot/workspace, they are easily edited w/o container rebuild or app restart (just a runtime /app/data/restart-gateway). For my needs I have removed the puff and padding from responses, and just get the answer. In theory, the base personality in AGENT.md/SOUL.md can be overridden in a particular SKILL.md, but I have not yet played with that. I was initially "overwhelmed" by creating a skill, I think the docs and the available examples are pretty poor (IMHO), but now I have realised the scope of what is possible. Especially getting an agent to write the skill ! If you have not tried Nanobot, it's a functional lightweight bloat-free app with great potential. Might well be my first Community App once 9.1.x is stable.

Not sure anybody cares (which is fine, my itch is scratched), but ... BISQ API HEADLESS : updated API calls removed the SKILL (because I don't want to duplicate it and it sits more naturally in the Nanobot repository: the updated skill has been deployed there) [image: 1772822611359-screenshot-2026-03-06-at-17.25.12.png]

@LoudLemur said: it's in a "works up to the last mile" state. I've got a few of those, so understood @LoudLemur said: Would switching to base 5.0.0 and its native Node fix the indexing step too? I've found that the answer to that type of question is only ever discovered by trying it ! I have a few other projects on/behind, but I might take a look. But please don't let that stop anyone else doing so.

@james Quick update — I just shipped a full Cloudron-native refresh of ISOMan (v0.3.8). This version is now properly aligned with Cloudron expectations and based on a cleaner packaging approach. Key updates: • Cloudron packaging aligned for production: proxyAuth + LDAP addons, persistent /app/data, internal port 8080, and healthcheck at /api/health. • Added optional create-only protection for POST /api/isos with LDAP-first authentication (Basic fallback still supported). • Fixed frontend create-flow issues when auth challenges returned HTML/non-JSON responses. • Added credential prompt handling for create-only auth and improved dialog accessibility. • Updated app icon handling for Cloudron login compatibility (PNG). • Deployment docs refreshed and fully translated to English. Result: Global access control remains managed by Cloudron proxyAuth, while ISO creation can now be protected independently without breaking the normal read/list UX. 0084e5c9-7ebf-440e-8746-d338bd190680-image.jpeg

Hello @pathab worked perfectly.