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

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