hatl
hatl
Thanks for the quick reply! Maybe the evsieve code can serve as a basis. It seems to work really well.
Maybe this can serve as the "official" image? https://github.com/borgmatic-collective/docker-borgmatic
http/2 is only expected to have a very small impact seems like the issue is caused by the DOM structure and the JS code  
I ran into the same issue. It occurs when using the "internal_id" instead of "id". see `curl -X GET -H "Content-Type: application/json" 'https://signal-api/v1/groups/+123456789'` to get the **id**
Would also be greate if you could add "c" for "archive card"
I can confirm the issue using the latest docker image. Unfortunately, there is no real "group" visible on the phone.
For now - as a workaround - I'd suggest to use a helper entity for the unlatch. I would need to think about how to add the 3rd option.
thanks for your contribution looks interesting from my point of view, the feature should be optional cloud be done via a config parameter - or like you suggested, a separate...
could you please update your branch to the lastest master version? i've added a CI build - thanks
it's nice to see your approvals :slightly_smiling_face: i still think that the feature should be optional