New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The community group is now on Discourse (meetecho-janus will be archived) #3177
Comments
Is there a way to get postings in Discourse over email? So I don't have to check in there to see if there's any new items? Push instead of pull :-) |
I talked about this with Joshua Colp yesterday on Mastodon and he said
so my guess is that it should indeed possible. Not sure if this is something I have to enable somewhere in the Discourse settings, or if it's something as a registered user you can configure in your own preferences. If you find something please do share! |
I can live with logging in to open new topics, that's a push anyway. I'll look into the pull mechanisms. |
I have played with some settings - will report back if it works. |
Hello i am interested in this repo i want to work more with integrations to webapps so that we can expand our service please if some one can spare some time i need your help i want to integrate webrtc -janus-rtmp |
Hi all,
the meetecho-janus Google Group has served us well in this ~10 years, but it has started to become more and more unusable, unfortunately, especially to us who have to use it everyday. In the past couple of days, for instance, I have been completely unable to post any new topic for some unknown reason, and I know I wasn't the only one. As such, we decided to move to Discourse instead, which will give us a more modern and flexible discussion place, where we could for instance create different categories which was never possible here:
https://janus.discourse.group/
Please open new discussions there, as we'll slowly faze the old group out, and will eventually archive it. Unfortunately there was no way to migrate existing discussions there, but old posts will still remain accessible there for historic purposes.
Thanks,
Lorenzo
The text was updated successfully, but these errors were encountered: