tigase / tigase-muc Goto Github PK

View Code? Open in Web Editor NEW

5.0 7.0 7.0 1.38 MB

Tigase Multi-User Chat Component

Home Page: https://tigase.net

License: GNU Affero General Public License v3.0

Batchfile 0.39% Shell 0.15% PLpgSQL 7.58% Groovy 3.16% Java 87.37% TSQL 0.72% Makefile 0.10% Python 0.52%

xmpp jabber muc multi-user-chat

tigase-muc's Introduction

The Multi-User Chat Componen for Tigase XMPP Server.

What it is

Tigase Multi-User Chat Component is XMPP component for Tigase XMPP Server providing support for XEP-0045: Multi-User Chat.

Features

It provides support to Tigase XMPP Server for following features:

XEP-0045: Multi-User Chat

Support

When looking for support, please first search for answers to your question in the available online channels:

Our online documentation: Tigase Docs
Our online forums: Tigase Forums
Our online Knowledge Base Tigase KB

If you didn't find an answer in the resources above, feel free to submit your question to either our community portal or open a support ticket.

Downloads

You can download distribution version of Tigase XMPP Server which contains Tigase Multi-User Chat Component directly from here.

If you wish to downloand SNAPSHOT build of the development version of Tigase XMPP Server which contains Tigase Multi-User Chat Component you can grab it from here.

Installation and usage

Documentation of the project is part of the Tigase XMPP Server distribution package and it is also available as part of Tigase XMPP Server documnetation page.

Compilation

Compilation of the project is very easy as it is typical Maven project. All you need to do is to execute

mvn package test

to compile the project and run unit tests.

License

Official Tigase repository is available at: https://github.com/tigase/tigase-muc/.

Licensed under AGPL License Version 3. Other licensing options available upon request.

tigase-muc's People

Contributors

Stargazers

Watchers

Forkers

whuaz partikmadan housongsong wrrgit stevenocean qianqianluo maranda

tigase-muc's Issues

tig_muc_room_affiliations Cannot persist

tig_muc_rooms can persist,but tig_muc_room_affiliations Cannot persist.muc config :

muc () {
 defaultRoomConfig {
   'muc#roomconfig_publicroom' = 'false'
   'muc#roomconfig_persistentroom' = 'true'
   'muc#roomconfig_membersonly' = 'true'
   }
   'muc-lock-new-room' = false
}

why?

Invalid MUC Presence

Describe the bug

<presence to="[email protected]/gajim.UMT9TQO0" from="[email protected]/xxx" id="65b66d5d-d646-4381-86d0-7e01c474992f" xml:lang="en">
   <c xmlns="http://jabber.org/protocol/caps" hash="sha-1" node="https://dino.im" ver="Wox05fElZ+gPYdJrEiHVC4oPlUw=" />
   <x xmlns="vcard-temp:x:update">
      <photo>22aa40b3050c4d295597d8fdedffc5f2e504de11</photo>
   </x>
   <x xmlns="http://jabber.org/protocol/muc#user">
      <item role="none" affiliation="none" nick="xxx" />
   </x>
</presence>

To Reproduce
Steps to reproduce the behavior:

join [email protected]
wait until you receive this stanza

Expected behavior
XEP0045 says role=none means the user is not present in the room. But this presence has no type=unavailable, so it contradicts the rule and this user is present in the room

vCard problem in MUC Rooms

Dear @tigase team, @woj-tek, @hantu85, @arturhefczyc,

This ticket in good place ^^

Linked to:

tigase/tigase-server#28

A this time, I have always the same base (but little change) instead of the XMPP client name/version/OS with or without time:

Using: Multi User Chat 2.2.0-b142/5761d16e / Linux-amd64-4.14.214-160.339.amzn2.x86_64, OpenJDK 64-Bit Server VM-17.0.6 Eclipse Adoptium

XEP-0045: Multi-User Chat

https://xmpp.org/extensions/xep-0045.html#changepres

jabber:iq:version
XEP-0092: Software Version

https://xmpp.org/extensions/xep-0092.html

urn:xmpp:time
XEP-0202: Entity Time

https://xmpp.org/extensions/xep-0202.html

vcard-temp:x:update
XEP-0153: vCard-Based Avatars

https://xmpp.org/extensions/xep-0153.html

xml:lang
XEP-0026: Internationalization (I18N)

https://xmpp.org/extensions/xep-0026.html

XEP-0071: XHTML-IM

https://xmpp.org/extensions/xep-0071.html

RFCs:

You can see the problem:

Tigase MUC Room:

<iq id="XXXXX-XXXX-XXXX" type="get" to="[email protected]/user">
<query xmlns="jabber:iq:version"/>
</iq>

<iq id="YYYYY-YYYY-YYYY" type="get" to="[email protected]/user">
<time xmlns="urn:xmpp:time"/>
</iq>

<iq id="ZZZZZ-ZZZZ-ZZZZ" type="get" to="[email protected]/user">
<vCard xmlns="vcard-temp"/>
</iq>

<iq from="[email protected]/user" xml:lang="en" id="XXXXX-XXXX-XXXX" type="result" to="[email protected]/xmppclient">
<query xmlns="jabber:iq:version">
<name>Multi User Chat</name>
<version>2.2.0-b142/5761d16e</version>
<os>Linux-amd64-4.14.214-160.339.amzn2.x86_64, OpenJDK 64-Bit Server VM-17.0.6 Eclipse Adoptium</os>
</query>
</iq>

<iq from="[email protected]/user" xml:lang="en" id="ZZZZZ-ZZZZ-ZZZZ" type="result" to="[email protected]/xmppclient">
<vCard xmlns="vcard-temp">
<PHOTO>
<BINVAL>BINVAL</BINVAL>
<TYPE>image/jpeg</TYPE>
</PHOTO>
</vCard>
</iq>

<iq from="[email protected]/user" xml:lang="en" id="XXXXX-XXXX-XXXX" type="result" to="[email protected]/xmppclient">
<query xmlns="jabber:iq:version">
<name>CLIENTNAME</name>
<version>VERSION</version>
<os>OS</os>
</query>
</iq>

<iq from="[email protected]/user" xml:lang="en" id="YYYYY-YYYY-YYYY" type="result" to="[email protected]/xmppclient">
<time xmlns="urn:xmpp:time">
<utc>YYYY-MM-DDT00:00:00.000Z</utc>
<tzo>+00:00</tzo>
</time>
</iq>

Another XMPP Server:

<iq id="XXXXX-XXXX-XXXX" type="get" to="[email protected]/user">
<query xmlns="jabber:iq:version"/>
</iq>

<iq id="YYYYY-YYYY-YYYY" type="get" to="[email protected]/user">
<time xmlns="urn:xmpp:time"/>
</iq>

<iq id="ZZZZZ-ZZZZ-ZZZZ" type="get" to="[email protected]/user">
<vCard xmlns="vcard-temp"/>
</iq>

<iq from="[email protected]/reload" xml:lang="en" id="ZZZZZ-ZZZZ-ZZZZ" type="result" to="[email protected]/xmppclient">
<vCard xmlns="vcard-temp">
<PHOTO>
<BINVAL>BINVAL</BINVAL>
<TYPE>image/jpeg</TYPE>
</PHOTO>
</vCard>
</iq>

<iq from="[email protected]/user" xml:lang="en" id="XXXXX-XXXX-XXXX" type="result" to="[email protected]/xmppclient">
<query xmlns="jabber:iq:version">
<name>CLIENTNAME</name>
<version>VERSION</version>
<os>OS</os>
</query>
</iq>

<iq from="[email protected]/user" xml:lang="en" id="YYYYY-YYYY-YYYY" type="result" to="[email protected]/xmppclient">
<time xmlns="urn:xmpp:time">
<tzo>+00:00</tzo>
<utc>YYYY-MM-DDT00:00:00Z</utc>
</time>
</iq>

Can you solve it?

Thanks in advance.

Respect history preferences on MUC join

Describe the bug

history preferences are not respected on MUC joins

To Reproduce
Steps to reproduce the behavior:

join [email protected]

<presence xmlns="jabber:client" to="[email protected]/lovetox" id="5f6ce1f8-df8a-4b66-b340-082d6f4ff181" from="[email protected]/gajim.GLEU3VID">
<c xmlns="http://jabber.org/protocol/caps" hash="sha-1" node="http://gajim.org" ver="qxfoxERhMvHS+QzDA/Q5OlnOavU=" />
<x xmlns="http://jabber.org/protocol/muc">
<history maxchars="0" />
</x>
</presence>

Server still sends all MUC history

<!-- Incoming 05.10.2019 10:06:08 ([email protected]) -->
<message xmlns="jabber:client" xml:lang="de" to="[email protected]/gajim.GLEU3VID" from="[email protected]/Holger" type="groupchat" id="350594463731">
<delay xmlns="urn:xmpp:delay" from="[email protected]" stamp="2019-08-27T16:51:58.556Z" />
<body>patrik and me have seen issues with querying the OMEMO nodes of sure.im users.  But I didn't get to looking into details yet.  (Plus I was under the impression that the OMEMO code is still known not to be incomplete and wasn't sure whether bug reports are appreciated at this point.)</body>
</message>

<!-- Incoming 05.10.2019 10:06:08 ([email protected]) -->
<message xmlns="jabber:client" xml:lang="en" to="[email protected]/gajim.GLEU3VID" from="[email protected]/hse" type="groupchat" id="0a945a75-c962-4a01-8075-409c1417f2b7">
<origin-id xmlns="urn:xmpp:sid:0" id="0a945a75-c962-4a01-8075-409c1417f2b7" />
<delay xmlns="urn:xmpp:delay" from="[email protected]" stamp="2019-08-27T16:53:30.955Z" />
<body>...dismail.de is running Prosody</body>
</message>

<!-- Incoming 05.10.2019 10:06:08 ([email protected]) -->
<message xmlns="jabber:client" xml:lang="en" to="[email protected]/gajim.GLEU3VID" from="[email protected]/hse" type="groupchat" id="d84bc982-ff9d-4fa1-93bd-45f6b98a5be5">
<origin-id xmlns="urn:xmpp:sid:0" id="d84bc982-ff9d-4fa1-93bd-45f6b98a5be5" />
<delay xmlns="urn:xmpp:delay" from="[email protected]" stamp="2019-08-27T16:55:12.298Z" />
<body>I mean I read about Siskin to be OMEMO ready, so I startet some test. You know, IM is interessted for such Apple clients</body>
</message>

muc mam seems broken in sure.im

Describe the bug
This was noticed some time back and some discussion happened at xsf/xmpp-providers-website#66 (comment)

To Reproduce
Steps to reproduce the behavior:

Create an muc and invite someone
disable the account and ask other person to send messages while offline
enable account and check for offline messages
No offline message or unable to decrypt

Expected behavior
offline messages should be visible

Screenshots

Desktop (please complete the following information):

OS: Debian bookworm
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: Android
OS: Android 10
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context

Tried on both monocles chat and gajim (also some other people reported issues earlier)

tigase / tigase-muc Goto Github PK

tigase-muc's Introduction

What it is

Features

Support

Downloads

Installation and usage

Compilation

License

tigase-muc's People

Contributors

Stargazers

Watchers

Forkers

tigase-muc's Issues

Recommend Projects

Recommend Topics

Recommend Org