

This isn’t a docker issue but an issue of running a non-deterministic process on the host system. If you must run an LLM run it inside a docker container.
#nobot #noindex


This isn’t a docker issue but an issue of running a non-deterministic process on the host system. If you must run an LLM run it inside a docker container.


Its setup by crypto bros


FluffyChat support MatrixRTC now.


Then why did they have a model A and B? Couldn’t they have a C or BE (extended)


Couldn’t they have made the board a bit bigger? Even throwing in older ram would have been a win if it meant keeping prices down and total ram size.


Do you have an alternative? critique without alternatives is not helpful.


I’m using Continuwuity you’re using synapse


Cinny calls an old matrix endpoint that returns 403 I’m surprised more people aren’t getting their home ip fail2banned.
/_matrix/media/v3/config for those who are interested.


Let their lawsuits be long and their lawyers slow and costly.


services:
sable:
image: git.sable.moe/sableclient/sable-next:latest
ports:
- '127.0.0.1:8080:8080'
volumes:
- ./config.json:/app/config.json:ro
restart: unless-stopped
Looks pretty simple to selfhost the web client too
https://github.com/SableClient/sable-next/blob/main/Caddyfile
Edit~~: I couldn’t get it working, moved to selfhosting cinny~~
Edit2: I got it working 🤘
Use this config file as a base https://git.sable.moe/SableClient/sable-next/raw/branch/main/static/config.json


The smp and xftp servers look pretty simple to get running with docker compose.


You just linked to a list of relays
here is the correct link: https://chatmail.at/doc/relay/getting_started.html#minimal-requirements-and-prerequisites


Have you considered piefed servers?


You must be the first person I’ve heard that actually selfhosts a delta chat server


Thanks, and fixed my spelling mistake


It looks promising, the UI looks much better. Other than the absence of a built in p2p livestream option, and an explicit no to federation.


https://github.com/shadowflee3/fluxer-selfhost
As comparison fluxer which I was much more interested in (polyproto federation, better UX mobile and web, hype) needs 4 containers (ex. proxy & certbot) needs 80 443 7700 7880 7881 3478 50000-50100 ports & two configuration files that needs edits to connect them.


For lifekit to work it needs direct https access, if you’re running caddy server that means connecting the tls certs to livekit somehow then opening up a hole range of ports.


Turns out the piefed tags don’t federate with lemmy, if you want proof I wasn’t acting in bad faith look at the post from my server.
https://piefed.nl/c/selfhosted@lemmy.world/p/226603/haven-discord-alternative-discussion-on-p2p-mediasoup-livekit
The trick is to run caddy on the host system no containment, then reverse proxy your wordpress containers through 8080+. Letting fail2ban and crowdsec interact with caddy through docker is too much hassle.