Marcel Hellkamp

I want to be careful about the 'How to not appear on Fediwall' part. That's a very sensitive topic. The phrase "That's a shame" may already be enough to trigger...

You can disable the messages (by running `bottle.py --quiet ...` or calling `bottle.run(quiet=True, ...)`) and then print your own message.

Oh, there is no `bottle.py --quiet` parameter, I could have sworn... but the `bottle.run(quiet=True, ...)` way still works.

I reviewed the PR, made a change suggestion, and the nothing happened so I forgot about it. In other projects a stale-bot would have long closed this issue due to...

If you are maintaining a module or tool affected by this, there is a workaround: Move the `from __future__ import ...` line above your own module docstring. It must be...

If the important APIs are implemented, then pixelfed sources should already work. Nothing to do here. If not, then it would make sense to ask the pixelfed devs to add...

Feel free to file a new issue if there is something to do on Fediwall side. As far as I know, this should already work.

LiveKit API secrets are just random strings, we can generate those ourselves (e.g. using `{{ ('livekit' + bbb_host_seed) | hash('sha256') }}`) and just replace the ones generated by [livekit-server generate-keys](https://github.com/livekit/livekit/blob/aee34ffefad89f135378bf11b8461e866d83e01b/cmd/server/commands.go#L39)...

Oh and we may need systemd overrides for `livekit-server` and `livekit-sip` to disable `CPUSchedulingPolicy` if `bbb_container_compat` is true. See [[email protected]](https://github.com/ebbba-org/ansible-role-bigbluebutton/blob/master/templates/systemd-overrides/bbb-html5-backend%40.j2) for example

Looks good to me! I'll try to give it a spin later this week on our infra and the merge :)