close
  • Be chevron_right

    Kaidan - A user-friendly XMPP client, and ATT - Automatic Trust Transfer

    debacle – pubsub.movim.eu / berlin-xmpp-meetup – Saturday, 2 March - 12:48 edit

Kaidan - A user-friendly XMPP client, and ATT - Automatic Trust Transfer

At this months Berlin XMPP meetup, we will probably

When? Wednesday, 2019-03-13 18:00 CET

Where?JWD: Takustraße 3, 14195 Berlin

#xmpp #meeting #meetup #berlin #jabber #kaidan #client #sprint #att #omemo #jwd

  • Mo chevron_right

    Some news regarding jappix.com and fr.movim.eu

    Timothée Jaussoin – pubsub.movim.eu / Movim – Monday, 25 February - 16:02 edit

Following our previous post. The owner of the French #server that was hosting the jappix.com XMPP server and fr.movim.eu pod is turning of his server at the end of the month.

The jappix.com server has just been merged with the movim.eu XMPP server (they are handled by the same ejabberd instance) and the fr.movim.eu pod will be turned off and redirected to nl.movim.eu for now.

#migration #movim #jappix #xmpp

  • favorite

    1 Like

    Tu

  • Be chevron_right

    Location Changed: Berlin XMPP Meetup: What happened at XMPP Summit 23 and FOSDEM 2019?

    debacle – pubsub.movim.eu / berlin-xmpp-meetup – Thursday, 7 February - 11:11 edit

Location Changed: Berlin XMPP Meetup: What happened at XMPP Summit 23 and FOSDEM 2019?

As always, we meet at the second Wednesday of every month on 18:00 hrs CE(S)T. Just come around and talk to us. We are actually nice.

This time, the three of us, who were at the XMPP summit and FOSDEM, will report.

And we will plan our sprint in March, see below.

Next Meeting

Wednesday, 2019-02-13 18:00 CET

DBJR

Mühlendamm 3

10178 Berlin

Visit our chat room: xmpp:berlin-meetup@conference.conversations.im?join

Breaking News: XMPP Sprint in Berlin

#berlin #xmpp #jabber #summit #fosdem #sprint #meeting #meetup

  • favorite

    1 Like

    Timothée Jaussoin

  • Op chevron_right

    Movim, FLOSS Alternative for Hangouts

    ericbuijs – news.movim.eu / open-source-software – Thursday, 31 January - 10:14

Looking for a FLOSS alternative for #Hangouts reignited my interest in #Movim. If only I can convince my friends to use Movim or any other #XMPP client. Anyway here is a short blog post of mine about Movim.

  • link

    Movim, FLOSS Alternative for Hangouts

    News is spreading that Google will replace classic Hangouts with Hangouts Chat and Hangouts Meet. Since Google had already decided to close G+ forcing me to look for an alternative this was a good moment replace Hangouts with a FLOSS alternative. I’m pretty happy with the Fediverse social networks as a replacement for G+ but … Continue reading "Movim, FLOSS Alternative for Hangouts"

  • Op chevron_right

    XMPP support on Nerdica.Net

    ericbuijs – news.movim.eu / open-source-software – Tuesday, 29 January - 13:12 edit

Recently all users of the Nerdica.Net, a #Friendica server, are able to use #XMPP. I hope that more Friendica servers will follow increasing the number of potential XMPP users.

  • link

    XMPP for all Nerdica.Net Users

    !Nerdica Forum As yesterday already pointed out, I worked on enabling XMPP for all Friendica.Net users. A short test showed that this was successful, at lea...

  • favorite

    1 Like

    Timothée Jaussoin

  • 2 Comments

  • 29 January Timothée Jaussoin

    Welcome to the XMPP party :) !

  • 1 February Adam

    I've had XMPP enabled for my users on social.isurf.ca since I started in last May. Until integrated chat functionality is sorted out in Friendica, though, it's a fringe feature.

  • chevron_right

    Dennis Schubert: ActivityPub - Final thoughts, one year later.

    debacle – Sunday, 13 January - 22:46 edit

Dennis Schubert: ActivityPub - Final thoughts, one year later.

Maybe Diaspora could be re-implemented using XMPP? :-)

I would like to hold XMPP up as an example, here. If you do not know XMPP, it is short for Extensible Messaging and Presence Protocol, a protocol for building distributed instant messaging applications. While extensibility was so important they even made it part of the protocol’s name, they did not want to end up with a runaway specification that depends on having implementers talk to each other to be working reliably.

Instead, they wrote a very strict base set of the absolute minimums required to build on XMPP, and pushed that through the IETF’s standards track, ending up with what is now RFC 6120. Acknowledging that they can never address all needs in such a strict specification document, they opened themselves for more flexibility:

This document specifies how clients connect to servers and specifies the basic semantics of XML stanzas. However, this document does not define the “payloads” of the XML stanzas that might be exchanged once a connection is successfully established; instead, those payloads are defined by various XMPP extensions. For example, [XMPP-IM] defines extensions for basic instant messaging and presence functionality. In addition, various specifications produced in the XSF’s XEP series [XEP-0001] define extensions for a wide range of applications.

They introduced XEPs, XMPP Extensions Protocols. The very first XEP ever published, XEP-0001, describes the process of getting a new XEP published to the world, and that process of that is not very hard to understand or tricky to follow. Everyone is invited to submit a proposal, you do not have to be a member of any organization, and in fact, you do not even need to maintain your own implementation. As long as your proposal follows the rules and matches the required format, it will be taken into consideration. After a proposal has been made, there is a specific chain of events, but it boils down to an open discussion on those proposals, and if there are no more doubts or things to improve, and if people agree that the proposal would be a useful thing to standardize, the proposal will eventually end up as an actual XEP.

At the time of writing, there are 151 active, draft, experimental, final, or proposed XEPs, and all of them can be found on the XMPP Standards Foundation’s website. Everyone interested in reading up on those topics, for example because they want to implement a client or a server, can find those documents there, and there is also a central infrastructure for asking questions and proposing improvements, which is open to everyone. This way, the XSF has ensured XMPP can be extended to all imaginable use cases, without ending up with watered-down or vague specifications.

If, for example, I wanted to implement an XMPP server or a client4, I could read the relevant RFCs as well as the XEPs that are relevant to my project. Some documents, like XEP-0387 for example, would even help me out deciding which XEPs are essential, by listing the things that are important when building a web client, or an advanced desktop client, or a mobile application, … There would be no need for me to talk to other XMPP server or client implementers for my implementation to work, and I could be very comfortable about the interoperability of my systems if I built them in accordance to the specifications. That is what specifications are meant to be.

#activitypub #diaspora #standards #xmpp #movim #salutatoi #xep

  • favorite

    1 Like

    Timothée Jaussoin

  • chevron_right

    Happy Birthday, XMPP! 20th Anniversary of 1st Jabber Server

    debacle – Thursday, 3 January - 21:37 edit

XMPP a.k.a. Jabber, a communication protocol for message-oriented middleware is probably the most mature technology for free and federated instant messaging. (IRC is far older, of course.) On 2019-01-04 we can celebrate the 20th anniversary of the first XMPP server release:

Jeremie Miller began working on the Jabber technology in 1998 and released the first version of the jabberd server on January 4, 1999.

In the last twenty years, we have seen protocols and services come and go, but XMPP, an IETF standard, is here to stay. It is backed by an international community of developers, does not depend on a single company, and is enhanced continuously by the XSF. Btw.: XMPP is not only used for chatting, but also for IoT, WebRTC, micro-blogging and social networks!

#xmpp #jabber #birthday #anniversary #jeremiemiller #federation

PS: ‎Ge0rG‎ pointed to the link to the original announcement on Slashdot. It reads:

Jeremie writes

"Jabber is a new project I recently started to create a complete open-source platform for Instant Messaging with transparent communication to other IM systems(ICQ, AIM, etc). Most of the initial design and protocol work is done, as well as a working server and a few test clients."

  • favorite

    3 Like

    Timothée Jaussoin , Dominik George , Simon Pepping

  • Be chevron_right

    The perfect ejabberd server setup using ansible

    debacle – pubsub.movim.eu / berlin-xmpp-meetup – Wednesday, 2 January - 11:35 edit

The perfect ejabberd server setup using ansible

After having heard about the theoretical part of a perfect XMPP server setup in Holger's talk, Linus will now show us how to do this in practice with ejabberd. For this purpose we're going to use the configuration management tool ansible, which will automate the setup process. This makes it much easier to move your setup to a different machine or reinstalling it. After having a look into how the ansible scripts work and what they do on the server, we'll also do a live demonstration.

The ansible scripts cover the setup of ejabberd, Let's Encrypt-certificates, an SQL database with MySQL/MariaDB or PostgreSQL, HTTP File Upload and ejabberd admin interface with reverse proxy using nginx and sslh for multiplexing XMPP/XMPPS/HTTPS on a single port (that can be useful if you're behind a firewall). You can also enable nextcloud authentication, but we won't go into many details on that topic.

When? Wednesday, 2019-01-09 18:00 CET

Where? DBJR, Mühlendamm 3, 10178 Berlin

#xmpp #ejabberd #meeting #meetup #berlin #jabber #ansible

  • favorite

    2 Like

    Timothée Jaussoin , reik