Daniel Molkentin

## Criteria * Every frontend MUST be free to use its own dialin numbers * The backends MUST be able to disambiguate dialin and MUST NOT confuse them * Dial-in...

If a node does not have `b3scaleagent` installed, it will never truly go online. If it fails to report a heartbeat, the node will also be taken offline, but this...

When no visibility is specified for a recording, use a default visibility setting per frontend. This mimics the global default setting in Scalelite.

Implement handling meetings from `b3scalectl` including: - [x] summary listing - [x] displaying individual meeting details - [ ] stopping meetings. Requires: - [x] a fix to allow calling `GET...

Look into golangci-lint findings

1

Already fixed a couple of clear cases of deprecations / improvements. Some things are pedantry or plain out false positives, but generally, having a linter satisfied (or muted where necessary)...

Downtimeless upgrade: Allow upgrading the DB schema before upgrading

1

Right now the migrations happen after the fact. It would be preferable to apply run migrations before an upgrade happens so it can be performed without any downtime e.g. in...

Useful for allowing theming where the `userdata_` elements (e.g. for passing custom CSS) only be submitted during `join()`, not `create()`. This allows for features like theming to work per frontend.

feat: rewrite provied analytics-callback-url callback as well

1

This provides access to the meeting's event.xml.

Content-Length error in b3scale

1

From the b3scaled logs: ``` b3scaled[12178]: {"level":"error","error":"http: wrote more than the declared Content-Length","remote_ip":"2001:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx","host":"127.0.0.1:42352","method":"POST","uri":"/api/v1/agent/heartbeat","user_agent":"Go-http-client/2.0","status":200,"referer":"","latency":9.739293,"latency_human":"9.739293ms","time":"2024-10-23T19:43:13Z"} ```

fixes #238