-
Notifications
You must be signed in to change notification settings - Fork 12
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
Need more docs #17
Comments
You just have someone from skype writing you a message. If configured correctly the puppet bridge will auto-create the room etc. |
Thank you. It is not working in my case. Only errors. But I think it should be placed at Readme. |
And another question. When somebody wrote to my skype puppet in skype. Skype puppet creates room, so there is skype puppet and this man. But what about real people:
|
You don't, you just wait for the skype user to message you and use that room
A ghost controlled by the puppet bridge |
So how I can use it? Case: I want to chat with somebody@skype using bridge
As I see in docs, now I can only initiate room creation from Skype side, and start chat from matrix side in Todo list. |
Just log in as skypebot user in Riot. Now I can see all rooms and invite people to that rooms. And chatting working correctly. |
That is where stuff already goes wrong! |
That's it. And it is really not obvious. Especially when you read #16 where you can see that bot working with many people simultaneously. You should write about it in documents. Yesterday I read this blog Maybe it is my misunderstanding but I thought that one bridge to 3rd party service should provide messaging for all users between two network. Not only one-to-one. |
I configured bridge using Readme.md
But what to do next?
You should describe how to use this bridge.
I've invited skype puppet to skype room and see a lot of error messages in matrix room
#skype_puppetStatusRoom
Also I see error messages using private chat with skype puppet.
Both error messages contains correct sender and text. And I see people adding to
#skype_puppetStatusRoom
The text was updated successfully, but these errors were encountered: