Tim van der Molen

sigtop should now be able to decrypt the database key on Windows. No extra steps are needed.

Here are provisional instructions for Linux. If you are using GNOME or any other desktop that uses GNOME Keyring, use `secret-tool` to fetch the encryption password. For example: ``` secret-tool...

sigtop should now be able to get the encryption key from the keychain on macOS. You no longer have to run the `security` command and provide a `passfile`. @sylasabdullahnguyen, or...

@flatz Great, thanks very much! @stefanputz The database key is encrypted with the encryption key in the file `Local State` in your Signal directory. The encryption key, in turn, is...

I'm not sure why you're seeing this. There have been several attachment-related changes recently; it's possible I overlooked something. As a first step, could you look up these attachments in...

So if I understand you correctly, the attachments aren't available in Signal Desktop either? It would be nice to know why they aren't available. Could you run the following command...

Could you paste the output of the following command as well please: ``` sigtop query "select rowid, messages.type, messages.json -> 'errors', json_extract(json_each.value, '$.error', '$.wasTooBig'), length(json_each.value ->> 'data') from messages, json_each(messages.json,...

I'm baffled. Is sigtop able to export at least some attachments? I don't have any other ideas right now, so I would like to see the full JSON data of...

> Yes, some have extensions. Others don't This might be a different problem. Could you look up a few of the attachments without extensions in Signal and tell me what...

Please download the latest sigtop.exe and export your attachments again. You will now also see warnings like these: ``` attachment without content type (sent: ...) no filename extension for content...