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

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.

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.

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.

We installed HPBE on a dedicated VPS and Nextcloud Talk is mostly ok for us now.

Simplex Chat is the best private messenger out there, that we have found. We'd love to run our own Simplex Server. Another app we are keeping our eye on is White Noise, which uses the Marmot protocol.

@Lanhild Interesting. I'll investigate more and see if I can turn the repo into a proxy app

Supporting Alby might help the Nostr community. It is a way to fund Zap to tip people on the Nostr network. @timconsidine this might be a candidate for the custom app installer...

@marcusquinn I tried similar approach - simplify to just Netbird and embedded Dex. But that wasn't enough. Will try again shortly with fresh brain.

Hello @luckow The updated PILOS package is located here: https://git.cloudron.io/playground/pilos Can be installed or updated with: # install cloudron install --location pilos --image brutalbirdie/pilosthm.cloudron.app:20260224-182149-388125f97 # update cloudron update --app $YOURPILOSAPP --image brutalbirdie/pilosthm.cloudron.app:20260224-182149-388125f97

This would be really nice to have, because it could replace a commercial option that you'd otherwise need to pay for.

Hello @jimmarek You could also build your own Docker image from the source. git clone git@github.com:KlausSchaefers/quant-ux.git cd quant-ux docker build -t quant-ux:latest If you are using the provided docker-compose.yaml setup from the GitHub repository, updating the docker images is as simple as running: docker-compose pull docker-compose restart