Today #Owncast released v0.0.8 focusing on chat. It lays ground work to allow us, and 3rd parties (including you!), to add more features going forward. Now users have persistent identity, allowing you to build much cooler things. It also means you can ban people.
Take a look at our release notes at https://owncast.online/releases/owncast-0.0.8/ to learn more.
Also, our next Owncast call is Thursday, the 19th, 1PM Pacific, so mark your calendar, and I'll send more details later.
What I would love to see eventually would be a flow like this:
1. When an Owncast user starts casting it's autoposted to the #Fediverse where it can be viewed embedded.
2. People can follow the user from the fedi client
3. Comments posted on the Owncast cast show up as replies on the toot, replies from fedi show as stream comments
Tomorrow #owncast will have its periodic sync-up call and you're invited. 10am Pacific time, you can find your local time here: https://www.worldtimebuddy.com/?qm=1&lid=100,8,12,5&h=100&date=2021-4-28&sln=17-18&hf=1
We'll bee meeting up on Jitsi, so feel free to drop by if you're curious, have suggestions, or generally want to become more involved in the project. https://meet.jit.si/owncast-discovery-meeting
Just to throw this out there, IndieAuth is a very small addition to OAuth 2.0 which adds identity into the system in a much lighter weight way than OpenID Connect. Mastodon could easily add this extension to return the user ID of the user who just authenticated. The login form on OwnCast would ask the user to enter their server name, and do discovery on the server to send the user there to log in.
I did a talk about how Mastodon/ActivityPub apps can use IndieAuth to accomplish this kind of thing. The video is available -- of course -- on my website: https://aaronparecki.com/2020/09/22/25/activitypub-oauth-2-1