mstdn.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A general-purpose Mastodon server with a 500 character limit. All languages are welcome.

Administered by:

Server stats:

16K
active users

Having lots of fun using Delta Chat. I've set up two accounts on my mail server, one for myself and one for my husband. We're both surprised at how fast it is compared to more traditional centralised chat apps like Signal. It's so cool to be able to self-host this and not rely on centralised infrastructure that is outside of my control.

Now I just need to convince everyone I know it's really cool :)

@delta

@gmc great and welcome :) did you try out the v86 app in a chat yet? It allows to run 32bit iso images, and if you configure eth0 on multiple devices the chat members will have an end-to-end encrypted private lan (using #webxdc realtime channels). Telnet/netcat/ping etc works. This virtual Ethernet even degrades in performance if too many devices do traffic :) tip: try it better on a desktop not mobile (although should also work)

@delta @gmc Do you have an article about this on your site somewhere? I'm not quite sure I grok what you mean.

@RandamuMaki @gmc no bigger write up, but if you have a desktop:

Go to message input, attach-app and select "v86 emu" app and start it.

Inside v86 app "Choose file", select an iso (download for example dl-cdn.alpinelinux.org/alpine/) and hit "Start" button. Login as "Root", no password.

@delta @gmc Weirdly enough that seems to be missing from the .deb version or I'm just ignorant. XD It's fine. It's enough to know it exists for some. :)

@delta @gmc That one broke on Debian 12.9 (Bookworm). I can't quite figure out why.

@RandamuMaki @delta what cpu architecture do you have?
does the file at `resources/app.asar.unpacked/node_modules/@deltachat/stdio-rpc-server-linux-<your architecture>/deltachat-rpc-server` exist?

@treefit @delta I'm using the flatpak right now on amd64.

@RandamuMaki @delta great that this works, though @liaizon opened an issue on the desktop repo with your report and I would like to help getting it solved/closed.

Could you try to download and run github.com/chatmail/core/relea ? that't the dc core binary that desktop failed to load/find in your screenshot.

If it doesn't work it would be interesting to know any clues to why and wether the newest core from github.com/chatmail/core/relea still has the problem.

@RandamuMaki @delta @liaizon

I'd appreciate your help in this as @rtn wasn't able to reproduce the issue.

@treefit @delta @liaizon @rtn Most likely because they already have the server installed, I would imagine? Edit: I was obviously wrong on this assumption as the server component is included in the deb.

@RandamuMaki @delta @liaizon @rtn the rpc server is not a speperate package, but just a file included in the dc-desktop Debian package, that is for some reason not found on your system.

AFAIK @rtn started with a fresh Debian VM.

@treefit @delta @liaizon @rtn You are correct, I just used gdebi-gtk to see whether the deb contained it and ls -l to see whether the permissions are okay.

@treefit @delta @liaizon @rtn Trying to just run the deltachat-rpc-server from that folder gives `ERROR deltachat_rpc_server: Fatal error: failed to create folder: Permission denied (os error 13).` Any debug I could run from terminal to give you output to work with?

@RandamuMaki @delta @liaizon @rtn you need to supply the env var "DC_ACCOUNTS_PATH" to a path that you allowed to write in so it can create the accounts folder

Maki

@treefit @delta @liaizon @rtn So run DC_ACCOUNTS_PATH="location" bash -c './deltachat-rpc-server' then? Giving it a random temporary folder outputs `2025-03-21T13:59:13.470948Z ERROR deltachat_rpc_server: Fatal error: "/temporaryfolder/accounts.toml" does not exist.` so the server itself is at least not building the file tree it needs. Doing the same to the main executable leads to the same error I had before.

@RandamuMaki @delta @liaizon @rtn if the folder is not empty/exists already it assumes it is an account directory, so you would need to try sth. like "/tmp/dc-accounts-test"

@treefit @delta @liaizon @rtn That might be why it errors out on the already-existing ~/.config/DeltaChat

@RandamuMaki @delta

the path it tries to find accounts in is actually:
~/.config/DeltaChat/accounts

and when that folder exists it looks for ~/.config/DeltaChat/accounts/accounts.toml

in your case it found sth, so it started migration from an older format, is there sth in the accounts_old folder?

about the permissions, I have the same thing, permissions only for the owner, tough permissions in the account folder are "drwxr-xr-x".

@treefit @delta The accounts_old folder exists within ~/.config/DeltaChat/ but is empty. There is no accounts.toml within any of the subfolders of ~/.config/DeltaChat/ . It looks like the Flatpak didn't create that either but that version just works without it.

@treefit @delta I'm wondering if perhaps the code should keep this kind of a situation into account so it creates the file it requires within an already existing folder structure? Just check if the necessary file exists and create it if it doesn't? What's the use of it just crashing without giving the user enough information to sort out a broken folder/file setup? It's just a bit confusing for an end user.

@RandamuMaki @treefit @delta We're getting somewhere. Nice! So it's about installing DeltaChat on a system where there's already an existing folder structure? Then any upgrade would have this issue but that's not the case right?

@rtn @treefit @delta I am unsure. I happen to have the folders previously mentioned on the system. I could temporarily move that out to a temporary location to see whether that solves it for me, but that will have to wait until tomorrow at the earliest and would not solve the problem on installations with an incomplete folder/file setup like mine if that is what the problem is.

@RandamuMaki @treefit @delta There's no stress with this at all. We're very happy that you take any time to help us find the issue. I'm pretty sure this is an edge case.

@rtn @treefit @delta I was home a bit earlier than expected. When renaming the ~/.config/DeltaChat folder to something else, DeltaChat makes the folder anew and populates it as such. So the issue clearly is with it finding an existing ~/.config/DeltaChat folder and files therein, which it seems unable to work with.

@RandamuMaki @treefit @delta What happens if you `diff` the folders? I.e. the renamed folder and the newly created one.

@rtn @treefit @delta Results as follows, with some obfuscations for personal privacy.

@RandamuMaki @treefit @delta Am I correct in that the `~/.config/DeltaChat_old/accounts_old` is an empty folder? Would it be possible to get the original log file where you got the crash? I'm thinking that something has gone wrong during a migration from an older version of DeltaChat. Very difficult to reproduce if I don't know which version was used before this version was installed on top.

@rtn @treefit @delta accounts_old is empty, yes. This is the oldest log I can find in the old folder. ~/ refers to the active user's home folder. As far as I know I did not have DeltaChat on my system before this but I might have at some point in the past installed it to try out and then removed it without purging the config folders properly?

@RandamuMaki @treefit @delta This makes sense. We're getting closer. Something is getting borked when migrating from older setups.