<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="color-scheme" content="dark light" />
<title>Blasta / xmpp</title>
<link rel="shortcut icon" href="/graphic/blasta.svg"/>
<link rel='icon' type='image/svg+xml' href='/graphic/blasta.svg'/>
<link rel='stylesheet' type='text/css' media='screen' href='/stylesheet/stylesheet.css'/>
</head>
<body>
<div id="container">
<div id="header" class="row">
<h1>
<img src="/graphic/blasta.svg"/>
<a href="/">Blasta</a> / <a href="/help">help</a> / <a href="/help/about">about</a> / xmpp
</h1>
<dl id="navigation">
<dd>
<img src="/graphic/blasta.svg"/>
</dd>
{% if jabber_id %}
<dd>
<a href="/save">Add</a>
</dd>
<dd>
<a href="/jid">Public</a>
</dd>
<dd>
<a href="/private">Private</a>
</dd>
<dd>
<a href="/read">Read</a>
</dd>
{% endif %}
<dd>
<a href="/search{% if jabber_id %}/jid/{{jabber_id}}{% endif %}">Search</a>
</dd>
<dd>
<a href="/popular">Popular</a>
</dd>
<dd>
<a href="/recent">Recent</a>
</dd>
<dd>
{% if jabber_id %}
<a href="/disconnect">Disconnect</a>
{% else %}
<a href="/connect">Connect</a>
{% endif %}
</dd>
</dl>
</div>
<div id="main" class="row">
<div id="content">
<h2> PubSub Bookmarks</h2>
<p>» The universal messaging standard; Tried and tested. Independent. Privacy-focused.</p>
<h3 id="overview">An Overview of XMPP</h3>
<p>
XMPP is the Extensible Messaging and Presence Protocol, a
set of open technologies for instant messaging, presence,
multi-party chat, voice and video calls, collaboration,
lightweight middleware, content syndication, and generalized
routing of XML data.
</p>
<p>
XMPP was originally developed in the Jabber open-source
community to provide an open, decentralized alternative to
the closed instant messaging services at that time. XMPP
offers several key advantages over such services:
</p>
<h4>Open</h4>
<p>
The XMPP protocols are free, open, public, and easily
understandable; in addition, multiple implementations exist
in the form of clients, servers, server components, and code
libraries.
</p>
<h4>Standard</h4>
<p>
The <a href="http://ietf.org">Internet Engineering Task
Force (IETF)</a> has formalized the core XML streaming
protocols as an approved instant messaging and presence
technology. The XMPP specifications were published as
<a href="https://xmpp.org/rfcs/#3920">RFC 3920</a> and
<a href="https://xmpp.org/rfcs/#3921">RFC 3921</a> in 2004,
and the XMPP Standards Foundation continues to publish many
<a href="https://xmpp.org/extensions/">XMPP Extension
Protocols</a>. In 2011 the core RFCs were revised, resulting
in the most up-to-date specifications (
<a href="https://xmpp.org/rfcs/#6120">RFC 6120</a>,
<a href="https://xmpp.org/rfcs/#6121">RFC 6121</a>, and
<a href="https://xmpp.org/rfcs/#7622">RFC 7622</a>).
</p>
<h4>Proven</h4>
<p>
The first Jabber/XMPP technologies were developed by Jeremie
Miller in 1998 and are now quite stable; hundreds of
developers are working on these technologies, there are tens
of thousands of XMPP servers running on the Internet today,
and millions of people use XMPP for instant messaging
through various public services and XMPP deployments at
organizations worldwide.
</p>
<h4>Decentralized</h4>
<p>
The architecture of the XMPP network is similar to email; as
a result, anyone can run their own XMPP server, enabling
individuals and organizations to take control of their
communications experience.
</p>
<h4>Secure</h4>
<p>
Any XMPP server may be isolated from the public network
(e.g., on a company intranet) and robust security using SASL
and TLS has been built into the core
<a href="https://xmpp.org/rfcs/">XMPP specifications</a>. In
addition, the XMPP developer community is actively working
on end-to-end encryption to raise the security bar even
further.
</p>
<h4>Extensible</h4>
<p>
Using the power of XML, anyone can build custom
functionality on top of the core protocols; to maintain
interoperability, common extensions are published in the
<a href="https://xmpp.org/extensions/">XEP series</a>, but
such publication is not required and organizations can
maintain their own private extensions if so desired.
</p>
<h4>Flexible</h4>
<p>
XMPP applications beyond IM include network management,
content syndication, collaboration tools, file sharing,
gaming, remote systems monitoring, internet services,
lightweight middleware, cloud computing, and much more.
</p>
<h4>Diverse</h4>
<p>
A wide range of companies and open-source projects use XMPP
to build and deploy real-time applications and services; you
will never get “locked in” when you use XMPP technologies.
</p>
<p>
Visit <a href="https://xmpp.org/about/technology-overview/">
this page</a> which provides an introduction to various XMPP
technologies, including links to specifications,
implementations, tutorials, and special-purpose discussion
venues.
</p>
<h4 id="conclusion">Conclusion</h4>
<p>
XMPP in general is an open and standardized protocol for
real time communication.
</p>
<p>
Anyone can host their own server and communicate freely with
each other, just like with email and just like email the
used addresses are of the form “name@domain.tld”.
</p>
<p>
People can use different apps and services, such as Monal,
from a single but also multiple accounts. This serves a
decentral and sovereign infrastructure and digital
communication on the internet but also offers many potential
for innovation.
</p>
<p>
Visit <a href="https://xmpp.org">xmpp.org</a> to learn more.
</p>
<br/>
<p class="quote bottom">
<!-- “Use XMPP, while it is still legal.” -->
“The open standard for messaging and presence.”
</p>
</div>
</div>
<div id="footer" class="row">
<dl>
<dd>
<img src="/graphic/blasta.svg" alt="logo"/>
<a href="/">blasta</a>
</dd>
<dd>
<a href="/help/about">about</a>
</dd>
<dd>
<a href="/help/about/xmpp">xmpp</a>
</dd>
<dd>
<a href="/help/about/xmpp/pubsub">pubsub</a>
</dd>
<dd>
<a href="{{journal}}">journal</a>
</dd>
<dd>
<a href="/help">help</a>
</dd>
<dd>
<a href="/help/policy">policy</a>
</dd>
<dd>
<a href="/help/feeds">rss</a>
</dd>
<dd>
<a href="/contact">contact</a>
</dd>
</dl>
</div>
</div>
</body>
</html>