bbernhard/signal-cli-rest-api 0.100-pre

Version 0.100-pre

on GitHub

• updated signal-cli to v0.14.4.1

• the receive endpoint in the Swagger API now contains the correct schema (thanks to @Gara-Dorta)

• various improvements to the signal-cli-rest-api Github CI jobs (thanks to @Gara-Dorta and @arnehuang)

• fixed potential crash in base64 attachment parsing (thanks to @SAY-5)

• improved the plugin mechanism. (if you are using your own plugins, please consider migrating your plugin to the new plugin format).

• added possibility to persist all received messages into a sqlite3 database.

  This is a feature that was requested a few times over the past years, but I never wanted to implement, because:

  • coming up with a database schema which serves every purpose is hard (which data should be stored? just the messages? the attachments too? what about the events?)

  • it adds additional (unnecessary) dependencies to third party libraries (sqlite3, lua script, etc) which increase the potential attack vector. While adding dependencies is justifyable if you get something in return, it's bad for people who don't want to use that feature - which I guess will be the majority.

  By providing that functionality as a plugin, both of those points are considered. If you aren't happy with the database schema and/or which data is stored, you can easily adapt the lua script to your needs. Since all the additional dependencies are compiled into a dedicated shared object, which is only loaded if the plugins are explicitly enabled. I think that's a acceptable tradeoff.

  If you want to give this new plugin a try, have a look here,

This is a pre-release. If you want to give it a try, please use this version bbernhard/signal-cli-rest-api:0.202-dev

Rootless Image: bbernhard/signal-cli-rest-api:0.202-rootless-dev

If you want to know the difference between the main version and the rootless version, have a look at the release notes of the last release.

Important Information:
If no issues appear, I am planning to merge the rootless image into the main image with the next release. That means, beginning with next release there will only be one image. If you haven't tested the rootless image yet, I am encouraging you to give it a try and check if everything works for you. If not, please raise an issue!