Post
3/
GreatApe update №2:
. @muhammadzaidali is doing a major refactor of the GreatApe front-end.
It is something we need to do to make future development of GreatApe better and faster.
(Once he is done, we will have to do a lot of testing to do to make sure everything went OK.)
2/
GreatApe update №1:
We have stopped calling what GreatApe does "live public conversations", as some people found that confusing.
We are now calling it a "Conference".
GreatApe has a concept of a 'stage' and an 'audience'. The people on the 'stage' can be seen and heard. The people in the 'audience' cannot (unless they come on the 'stage').
I updated most of the language in the GreatApe front-end to reflect that, but more to-do.
3/
GreatApe update №2:
. @muhammadzaidali is doing a major refactor of the GreatApe front-end.
It is something we need to do to make future development of GreatApe better and faster.
(Once he is done, we will have to do a lot of testing to do to make sure everything went OK.)
4/
GreatApe update №3:
. @benyamin0 is working on fixing a UX bug — where everyone who was on the 'stage' gets kicked off of the stage if the host temporarily gets disconnected.
He is going to make it so — even if the host gets disconnected for 60 seconds, the GreatApe conference will continue.
A space for Bonfire maintainers and contributors to communicate
