I am not able to connect to waku status peers at https://fleets.status.im/ in prod.
Am using the @status-im/js npm package with the node in prod
@fryorcraken have any ideas here?
Chatted with @feliciomununga on discord. Also raised a ticket
Would be ok to followup on either place. Thanks
On Discord: Discord (join https://discord.waku.org).
In summary:
- The package
@status-im/js
in the status-web monorep is deprecated. There is currently no maintained library of the Status chat protocols available in the web; - We are reviewing the current chat protocols, the latest on this subject can be found here: Discord
- There is no current intent to develop browser libraries for Status chat, but this can be changed, especially as we will write RFCs/specs for any new protocol
- To interact with Status applications, the recommend way is to use the
status-backend
binary one can build from the status-go repo; it exposes a REST API - There is no properly define “Chat SDK” at this point in time, but it is possible to use the status-go Golang library to integrate in other software; This will become easier by ~end of year as we are tidying up the chat part of the codebase (and extracting it, not yet committed to this)
Cool. Thanks for the replies here and on discord. The SDK would be super helpful for those wanting to integrate p2p chats in their dapps.
Well, I have a follow up question.
I do not find a utility function to convert profile key to public key
Inorder to use “chat_createOneToOneChat” il need to provide an ID, this is the public key of the recipient right?
UPDATE: I managed to get the one to one chat working, had some difficulty understanding chatId also missed out on sending “contentType” hence was facing issues and was not able to receive the msg at the other end.
All is good right now and its working fine. Will post further findings if any.