Similar to email, the client passes the message for the recipient in encrypted or plain text to its home server, which in turn contacts the recipient's home server and gives it the message for the recipient, and the recipient in turn gives the message to the recipient's client. This communication is TLS encrypted between servers (S2S) or between client and server (C2S), and may additionally be OMEMO, PGP or otherwise encrypted depending on the room. Audio and video connections are made directly from client to client (C2C), and are only switched by the servers (TURN). The order in the table is chronological and by duration. Connections that are already slightly longer rise up the table.
|220.127.116.11||telesto.hot-chilli.net.||( DE, Germany)|
|18.104.22.168||v2202101139504140605.quicksrv.de.||( AT, Austria)|
|22.214.171.124||mail.404.city.||( IS, Iceland)|
|126.96.36.199||panoramix.lagaule.org.||( FR, France)|
|188.8.131.52||unn-95-168-217-72.superhosting.cz.||( CZ, Czech Republic)|
|184.108.40.206||xmpp.conversations.im.||( DE, Germany)|
|220.127.116.11||snowden.jugendhacker.de.||( DE, Germany)|
|18.104.22.168||web01.cdom.de.||( DE, Germany)|
|22.214.171.124||meowr.ru.||( FR, France)|
|126.96.36.199||static.188.8.131.52.clients.your-server.de.||( DE, Germany)|
|184.108.40.206||v2202105144906152359.supersrv.de.||( DE, Germany)|
|220.127.116.11||www.poridge.club.||( RU, Russian Federation)|
|18.104.22.168||v220190910391897369.powersrv.de.||( DE, Germany)|
|22.214.171.124||-||( DE, Germany)|
|126.96.36.199||-||( DE, Germany)|
|188.8.131.52||yaxim.boerde.de.||( DE, Germany)|
|184.108.40.206||zeus.jabber.org.||( US, United States)|
|220.127.116.11||xmpp.chinwag.im.||( AU, Australia)|
|18.104.22.168||149-210-189-243.colo.transip.net.||( NL, Netherlands)|
|22.214.171.124||-||( SE, Sweden)|
|126.96.36.199||static.188.8.131.52.clients.your-server.de.||( FI, Finland)|
|184.108.40.206||die-li.ga.||( DE, Germany)|
|220.127.116.11||ahr.eifel.cloud.||( DE, Germany)|
|18.104.22.168||static.22.214.171.124.clients.your-server.de.||( DE, Germany)|
|126.96.36.199||cpe-74-140-234-251.cinci.res.rr.com.||( US, United States)|
|188.8.131.52||ec2-54-185-74-196.us-west-2.compute.amazonaws.com.||( US, United States)|
|184.108.40.206||fw1.650thz.de.||( DE, Germany)|
|220.127.116.11||mail.mail55.de.||( DE, Germany)|
|18.104.22.168||88.ip-51-75-23.eu.||( FR, France)|
|22.214.171.124||127-116-158-51.instances.scw.cloud.||( FR, France)|
|126.96.36.199||static.188.8.131.52.clients.your-server.de.||( DE, Germany)|
|184.108.40.206||pix-art.de.||( DE, Germany)|
|220.127.116.11||xmt.bkp.||( CH, Switzerland)|
|18.104.22.168||ec2-34-217-107-99.us-west-2.compute.amazonaws.com.||( US, United States)|
|22.214.171.124||-||( DE, Germany)|
|126.96.36.199||inspirenet.org.||( US, United States)|
|188.8.131.52||256.bz.||( RU, Russian Federation)|
|184.108.40.206||129-110-245-190.fibertel.com.ar.||( AR, Argentina)|
|220.127.116.11||magicbroccoli.de.||( DE, Germany)|
|18.104.22.168||anonym.im.||( DE, Germany)|
|22.214.171.124||185-125-111-65.static.intovps.com.||( RO, Romania)|
|126.96.36.199||xmpp.is.||( RO, Romania)|
|188.8.131.52||knopi.disroot.org.||( NL, Netherlands)|
|184.108.40.206||jabberfr.org.||( FR, France)|
|220.127.116.11||toofast.vip.||( CA, Canada)|
|18.104.22.168||dusk.jabber.ru.||( DE, Germany)|
|22.214.171.124||beijinglug.club.||( FR, France)|
|126.96.36.199||static.188.8.131.52.clients.your-server.de.||( DE, Germany)|
|184.108.40.206||poddery.com.||( DE, Germany)|
|220.127.116.11||dismail.de.||( DE, Germany)|
XEP stands for
XMPP Extension Protocol. It is a protocol used to extend the XMPP protocol.
Extensible Messaging and Presence Protocol) is an open source protocol used for real-time communication over the Internet. It was originally developed for instant messaging (IM) and online presence, but is now also used for voice over IP (VoIP), video transmission, file transfer, and other applications.
XEPs are official XMPP extensions developed and maintained by the XMPP Standards Foundation (XSF). XEPs define new features, protocols, formats, and behaviors that XMPP clients and servers can use to improve interoperability between different XMPP implementations. XEPs can be created and submitted by any interested party, but they go through a review and standardization process before they are officially published and implemented.
To log in you need an XMPP client. This should meet the following minimum requirements:
XEP-0077 is an XMPP Extension Protocol (XEP) called
in-band registration. It defines a method to create a new user account on an XMPP server by transmitting the registration information in the Jabber protocol itself.
Essentially, XEP-0077 allows a user to register themselves without the administrator of the XMPP server having to do so. The user can connect to the XMPP server, start the registration process, and transmit the required information (username, password, etc.) directly through the XMPP protocol.
Although XEP-0077 is a useful protocol, it also has some limitations. Some XMPP servers do not implement the protocol or do not allow it for security reasons. Therefore, users may need to use an alternative registration method, such as registering via a web application or manually creating an account by the XMPP server's administrator.
Overall, XEP-0077 is an important XMPP protocol that facilitates user account registration and makes the registration process more efficient and user-friendly for new users.
XEP-0163 is an XMPP Extension Protocol (XEP) called
Personal Eventing Protocol (PEP). It defines a method to exchange status updates and other events in real time between XMPP clients.
Essentially, PEP allows users to publish events that other users can subscribe to and view. For example, a user could publish their current status (
Away, etc.) or their current activities (
Making a call,
In a meeting, etc.), which can then be subscribed to and viewed by other users.
PEP is an important part of XMPP and is supported by many XMPP clients and services. It allows users to quickly and easily share real-time information and stay in touch with other users.
Some specific uses of PEP include:
Last seen status: PEP can be used to publish a user's
last seen status and show other users when they were last online.
Activity Updates: PEP can be used to publish a user's real-time activities, such as reading email or watching a video.
Location information: PEP can also be used to publish a user's location information, which can then be viewed by other users.
Overall, PEP is an important XMPP protocol that allows users to quickly and easily share real-time information and stay in touch with other users.
XEP-0191, also known as Simple Communications Blocking, is an XMPP Extension Protocol (XEP) that defines a method for blocking users on an XMPP network. It allows users to block certain other users from receiving messages from them.
XEP-0191 defines a simple protocol for blocking users based on a
block list. Each user can create a list of other users from whom they do not want to receive messages, and store this list on the XMPP server. When a user tries to send a message to another user on the block list, the message is rejected by the XMPP server and not forwarded to the blocked user.
Blocking users can be triggered in several ways, such as by direct user interaction or by evaluating rules or events. For example, users can block another user by clicking a
Block button in their XMPP client, or by a rule triggered based on keywords in messages or other criteria.
XEP-0191 is an important protocol because it allows users to block unwanted messages and thus have better control over their communications on XMPP networks. It is supported by many XMPP clients and services and helps create a more secure and user-friendly XMPP ecosystem.
XEP-0198 is an XMPP Extension Protocol (XEP) that defines a protocol for reliable data transport (stream management) between XMPP clients and servers. It allows users to maintain connections during a session, even if the connection between client and server is lost.
With XEP-0198, a client can maintain connection to the server while it is inactive without disconnecting. When the client becomes active again, it can reconnect without losing data. The protocol also defines a method for transferring data lost during disconnection.
XEP-0198 defines a stream management protocol that operates in a manner that minimizes latency and maximizes efficiency. When the client sends a message, the server acknowledges the message before the client sends the next message. This ensures that the server stays up to date and the client does not send unnecessary data.
XEP-0198 is important for XMPP applications that require a reliable and efficient connection, such as instant messaging, voice, video, or file transfer. It is supported by many XMPP clients and services and helps improve the stability and reliability of XMPP networks.
XEP-0215, also known as
External Service Discovery is an XMPP Extension Protocol (XEP) that defines a method for discovering services outside the XMPP network. It allows XMPP clients to discover external services without having to communicate directly with the service.
XEP-0215 defines a protocol in which an XMPP server acts as an intermediary that forwards the XMPP client's requests to external services and sends the responses back to the client. The client does not need to connect directly to the external service, which improves security and simplifies connection establishment.
The protocol also defines a method for authenticating and authorizing external services, which allows XMPP clients to access only services to which they are authorized. This helps improve the security of XMPP networks.
XEP-0215 is important for XMPP applications that use external services, such as voice, video, data exchange, or data analysis. It is supported by some XMPP clients and services and helps improve the interoperability and flexibility of XMPP networks.
XEP-0237, also known as
Roster Versioning is an XMPP Extension Protocol (XEP) that defines a method for synchronizing contact lists (rosters) between XMPP clients. It allows users to synchronize their contact lists across multiple devices without conflict or duplication.
XEP-0237 defines a protocol where each contact on the user's contact list is assigned a version number. When the user makes changes to their contact list, the version number increases and the server notifies all of the user's connected devices of the changes.
The synchronized contact list always contains the most recent version of the contact list, preventing duplicates and conflicts that might otherwise occur during synchronization. The protocol also defines a method for handling conflicts when two or more of the user's devices make simultaneous changes to the contact list.
XEP-0237 is important for XMPP applications that require a shared contact list, such as instant messaging or voice and video. It is supported by many XMPP clients and services and helps improve the interoperability and usability of XMPP networks.
These are by no means all clients, just a few that we have cursorily tested to see if they meet our minimum requirements. Monitoring all these clients to document their functions is a very time-consuming activity, and therefore we cannot guarantee that our information is always up-to-date. Be careful not to always install the very latest "nightlies", as they are often unstable, and can crash unexpectedly.
A: Basically nothing more than a chat server. A machine that transports text, image, link, audio and video messages from one computer to another in real time. You don't need a phone number or email address, birth dates or shoe size. Everything is incredibly simple.last edited:30.04.2021
A: No! When a JID is deleted, then a kind of thombstone is created for 36 months, which prevents the recreation of an identical JID. There are important reasons why this is so. A Thombstone is not created when an account is automatically deleted after 36 months due to lack of activity.
A: YesOn! When a MUC is deleted by an owner, it also creates a kind of thombstone that prevents the recreation of a MUC with the same name by someone other than the original owner. When the JID of the owner, including the Thombstone of the JID are gone, a MUC with the same name can be recreated. Not before.
A: Yes, it can. It is also possible to appoint more than one owner. For example, an owner can also assign, and a MUC can become ownerless. In this case, contact the server administrator.
A: Make sure that your client supports XEP-0191, then blocking will work fine. The server also supports XEP-0016 but experience shows that clients react differently.
A: Make sure that your client supports XEP-0077 then it will work fine.
A: This will only work if we know your email address, which is hopefully not the case. If you nevertheless write a real e-mail in your profile, and we can identify you with it, we may be able to reset the password. However, we would prefer not to have anything to do with this.
A: All clients we recommend (see list below) support inbound account creation. This means that you can (and should) create and modify your account yourself using the client, simply by selecting your new JID: (for example)
firstname.lastname@example.org and entering a password for the account. Pay attention to the domain
The clients all have this option
Create this account on the server [_] which you have to activate to create a new account...
The JID consists of the username:
username, the domainname
zp1.net, some clients ask for the hostname:
xmpp.zp1.net or the port:
Some clients also ask for encryption. This is:
A: Right now we are hosting 414 users, of which online at the moment are 132. It's a live place, a constant going and coming.last edited:26.03.2023
A: Unfortunately, we can't tell because we only see the IP that dials in to us, which doesn't mean anything because most users use VPNs, proxies, or the Tor network, which hide and obfuscate the source IP.
A: All. We have installed the complete list of living languages ISO-639. All languages, left to right, right to left, top to bottom and bottom to top. It's quite impressive how many languages there are in the world. Let's hope it stays that way.last edited:01.12.2019
A: This means that our visitors have no right to enter the server. For example, we reserve the right to exclude anyone without any justification, and the person cannot use any legal means against it. Spam, phishing, begging, threatening or other practices not mentioned here, for example, do not fall under "Free speech". There we are then very consistent.
A: We are planning a store with fan items, sometime in the far future. At the moment there is nothing to buy.
A: Anyone who feels like it. You just need to register on https://weblate.zp1.net and you can start right away. The project is here Just ask in the "welcome" Room if you don't know your way around.
A: Who feels able to do this. If you disagree with an existing translation, you can anonymously suggest a better translation.
A: The code of this page is located here in a Gitlab . Registration is also required here to push.
gpg --versionto check if the installation was successful.
File » New OpenPGP key pair .... If you already have a key pair (private and public key), please import them into Kleopatra.
Gajim » Pluginsor (Ctrl + E) so that
Gajim » Accounts » Profile » Modify » +Add Entry » Add Public Keyby opening it with an editor (e.g. Notepad) and inserting it. Finally save and we are done.