Our new OpenTalk test-instance
- Speedtest not yet implemented
Metrics not yet implemented (affects you in the sense of: to see whether it's annoying to you if i restart the service)
- Protocol PDF export only works from within the pad
- Recordings can't be made available yet (waiting for upstream), the menuentry will not work
- no proper Email support yet
- phone calls feature not addressed yet, but planned
Login / signup
OpenTalks authentication service (Keycloak) is connected to our authentication server (Zitadel). Please use the button mentioning Zitadel and go from there. The loginform above that button will NOT work. That's because having two independant auth providers feels ... wrong and Keycloak is required for OpenTalk.
About this instance
Due to the complexity of OpenTalk, this instance derivates off of their official “lite” Docker example. It adds a number of services, trying to reach an as complete as possible experience. As of the time of writing, this is still in progress and a few more restarts are to be expected in order to apply new settings and stuff.
Maintenance window: because it doesn't make sense to restart all the time while you are trying to give it a fair test, I will try to apply new settings only between 5-9pm CET. (see below)
This instance is categorized as “playground mode”. Its purpose is to evaluate whether it is feasable to keep it long-term. This also means that you still are more than welcome to use and test it, because software that is not used by anybody can't be tested/evaluated properly.
Playground mode window: This service will be evaluated until mid of June 2023
tba (irrational happy “Rust” noises)
How to contact me:
Follow me on Mastodon / More options on tchncs.de