#loso — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #loso, aggregated by home.social.
-
This is how I am thinking about pointing to the GreatApe WebSocket API in the activity file.
The GreatApe WebSocket API — ActivitySocket ? — is sending ActivityPub activities over a WebSocket, along with some other stuff (such a queries, and commands).
Right now, I am using the "endpoints" field with the sub-field "inoutbox" to point to the WebSockets API end-point.
RE: https://mastodon.social/@reiver/114590677447681643
#ActivitySocket #GreatApe #Fediverse #FediDev #FediDevs #DeSo #FeSo #LoSo
-
2/
One thing that is interesting about the GreatApe WebSocket API is that —
Because the WebSocket can be both read from and written to — the WebSocket is in a sense both an ActivityPub outbox and an ActivityPub inbox at the same time.
RE: https://mastodon.social/@reiver/114585707207505158
#ActivitySocket #GreatApe #Fediverse #FediDev #FediDevs #DeSo #FeSo #LoSo
-
1/
GreatApe is a conferencing platform for the Fediverse and the Social Web — where an audience can listen & watch live, and can be invited to join the speakers on the stage.
GreatApe makes use of a WebSocket for communications.
I am working on turning the WebSocket API that @muhammadzaidali and @benyamin0 created into something more ActivityPub / ActivityStreams like.
Interestingly —
RE: https://mastodon.social/@reiver/114585707207505158
#ActivitySocket #GreatApe #Fediverse #FediDev #FediDevs #DeSo #FeSo #LoSo
-
6/
GreatApe update №5:
We are looking at adding OpenWebAuth support for logging into GreatApe.
So that people can log into GreatApe using any Fediverse software that supports OpenWebAuth — such as Hubzilla.
. @scott suggested we do this (and him and I are currently discussing it).
-
5/
GreatApe update №4:
I am working on making the WebSocket API (that @muhammadzaidali and @benyamin0 already created) look more ActivityPub / ActivityStreams like.
For example, sending ActivityPub / ActivityStreams events over the WebSocket.
Although, the WebSocket protocol needs to support a QUERY & QUERY-RESPONSE pattern, too. But, so far, the QUERY-RESPONSE has been a AP / AS `Announce` of some type of AP / AS 'Object'.
#ActivitySocket #DeSo #GreatApe #Fediverse #FeSo #LoSo #SocialWeb
-
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.
-
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.
-
1/
GreatApe is a conferencing platform for the Fediverse, and the Social Web — where an audience can listen & watch live, and can be invited to join the speakers on the stage.
Some updates —