matrix mautrix bridge mishaps#

continue investigating the discord-matrix bridge
- issue origin - a lot of older room, the bot (admin, creator ) is somehow no longer inside the room
- fix - POST /_synapse/admin/v1/rooms/<room_id_or_alias>/make_room_admin
- failed attempt - Should room creators always be able to give themselves power? (SPEC-369) · Issue #165 · GitHub
  - federated - very tough
- investigate in the database side, pull out a copy of _discord db to see the point to the room -
  - archieve in glacier
  - rclone copy s3:matrix-pg-backup/matrix_mautrix_discord-20231016.sql.gz ./
- looking at the schema and the db backup - as the one room-id somehow is connected in like 40 different tables.

sliding proxy#

issue upgrading: sliding proxy - requires new library, setup on webserver/well-known, new database,
- also with the implement it only worked with traefix setup so even harder
while the new android/desktop client is still rather disappointing in progress of dev
research time
find out how many percent in the public has on https://joinmatrix.org/servers/

for srv in servers:
	curl https://srv/.well-known/matrix/client -v
	run | jq ."org.matrix.msc3575.proxy"

stuck at this misconfig forever https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2543 https://github.com/spantaleev/matrix-docker-ansible-deploy/issues/2642
now the structure is
- caddy -> traefik -> nginx-companion -> nginx-proxy -> synapse.. genius

sql investigation#

# on host
docker run --rm --publish 1799:8080 --link matrix-postgres --net matrix adminer

# on client, proxy
ssh -L 1799:localhost:1799 arm
curl http://localhost:1799/ 

# retrive the credentials from /matrix/{synapse, mautrix-discord}/config

migrating s3 back#

expire policy, no need to use s3

paru -S aws-cli

aws configure

aws s3 sync --endpoint-url=https://s3.nl-ams.scw.cloud s3://bucket/ /home/rt/local-store

Matrix maintenance

matrix mautrix bridge mishaps#

sliding proxy#

sql investigation#

migrating s3 back#