![]() |
Bartosz Małkowski opened 4 years ago
|
![]() |
Also implemented, together with issue #42 |
|
Please provide code examples for the following:
@andrzej.wojcik if I block a JID, on one resource will I get a notification about this new blocked JID on other connected resources? |
|
@kobit As stated in XEP-0191:
This means that you will get notified. |
|
Great!, this is what I need. @bmalkow, please provide requested code examples. |
![]() |
You can also may listen for information about updates of blocked list:
But those events will be fired only when client previously retrieve list of blocked contacts (in other case, server do not push information):
|
|
Sevan will be taking over client implementation, so we need to have it documented in one place. @bmalkow please add this to our documentation for the Kangaroo project in the Kangaroo github repo. |
![]() |
Documentation to module is here: https://github.com/tigase/halcyon/blob/master/src/docs/asciidoc/text/modules/BlockingCommandModule.asciidoc Should I also add it to Kangaroo GitHub repo? If yes, then where exactly? |
|
Again assigned back to Sevan. @sevan.evans please review both documents and let us know if something is not clear yet. We can also talk about this during our Zoom session. |
![]() |
When using the The client will be prompted after that the user has been blocked. You can find blocked users in the contacts menu, or in the dedicated Blocked Contacts list. The reason that blocked JID's are not hidden from the client in the contact menu, is incase a blocked user is added into a chat that the client is also added into, therefore giving a reason that they are not able to see their chat messages. Unblocking works as expected (image after unblocking all contacts): |
Type |
New Feature
|
Priority |
Normal
|
Assignee | |
Spent time |
4h
|
XEP-0191: Blocking Command