social.gl-como.it

Cerca

Elementi taggati con: federation

The rocky road to OMEMO by default



Daniel Gultsch, developer of Android XMPP client Conversations, writes,

Why it took us more than two years to enable End-to-End encryption by default: The first in a series of essays leading up to the release of Conversations 2.0



...
The other big hurdle we had to overcome was the adoption rate in clients. If you send OMEMO encrypted messages by default you should have a reasonable expectation that your contact will be able to decrypt the message. Reasonable expectation doesn’t mean that every single client out there has to support it—In an ecosystem with hundreds of small, badly maintained clients that’s just not feasible—but the major clients should at least have a plugin available.
In March 2018 we finally reached the point where every plattform has one or more clients with OMEMO support. Conversations and Zom on Android, ChatSecure on iOS, Psi and Gajim on the desktop. The up and coming desktop client Dino—despite not having had an initial release—already has support for OMEMO as well. And even the webclient JSXC has a plugin available.
Considering the complexity of OMEMO and the fact that most of these clients are developed by people in their spare time, this is actually quite an impressive adoption rate.
...
Moxie Marlinspike, in his 2016 propaganda piece ignorantly bashing XMPP, had one valid point: Enabling end-to-end encryption in a homogenous environment is easier than introducing it in a heterogenous one like Jabber. Nobody is denying that. However, if something is hard to achieve there are two possible approaches: Either try your best and don’t give up, or put your head in the sand and create yet another walled garden that is no different from other proprietary solutions.
Admittedly it has taken us a while to get to a point where we can enable end-to-end encryption by default, but it was worth the effort in that we ended up with something that is different from WhatsApp in more than just marketing.
#xmpp #omemo #conversations #psi #gajim #zom #chatsecure #dino #jsxc #federation #encryption
 

Slack's bait and switch



The developer of the beautiful Converse.js web browser XMPP client, JC Brand, writes:

On Federation



When we talk about "federation" in networks, we mean the ability to communicate between different service providers.
For example, email is federated. You can set up your own email server, and then send emails to people with their own email servers, or to people with Gmail or Yahoo! accounts.
You can email any other email address in the world, regardless of where that email address is hosted.
If email never existed, and a company like Slack today would come out with this brand new concept of "Electronic Mail", let's call it digimail, do you think they would standardise the digimail protocol and allow you to send messages to other digimail purveyors?
We all know the answer to that. They won't, and neither would Google, Microsoft or Facebook.
Heck, Facebook is actively trying to replace email since years.
The reason email is federated, is because it was developed before surveillance capitalism was a thing and because it was established and entrenched long before these companies came around.
There's a reason why your email address is still the de facto way to sign up for any service on the web (sometimes with one or two degrees of separation), and it's because of federation.
XMPP is designed to allow federation. Think about that. Instead of having to sign up to various different chat providers, all which try to lock you in and monetize your conversations, you could instead have one chat account, and use that to chat with anybody else, regardless of which chat provider they are using.
Alas, that's the dream, but because XMPP came much later to the scene, it didn't develop the critical mass as email has, and here we are. With dozens of chat apps, all non-interoperable and closed off.
#slack #xmpp #federation #surveillancecapitalism
 

On the demise of Slack's IRC / XMPP gateways



Say no to Slack.



Debian developer Gunnar Wolf writes:
I have grudgingly joined three Slack workspaces, due to me being part of proejects that use it as a communications center for their participants. Why grudgingly? Because there is very little that it adds to well-established communications standards that we have had for long ~~years~~ decades.
On this topic, I must refer you to the talk and article presented by Megan Squire, one of the clear highlights of my participation last year at the 13th International Conference on Open Source Systems (OSS2017): «Considering the Use of Walled Gardens for FLOSS Project Communication». Please do have a good read of this article.
Thing is, after several years of playing open with probably the best integration gateway I have seen, Slack is joining the Embrace, Extend and Extinguish">-minded companies. Of course, I strongly doubt they will manage to extinguish XMPP or IRC, but they want to strengthen the walls around their walled garden...
So, once they have established their presence among companies and developer groups alike, Slack is shutting down their gateways to XMPP and IRC, arguing it's impossible to achieve feature-parity via the gateway.
Of course, I guess all of us recognize and understand there has long not been feature parity. But that's a feature, not a bug! I expressly dislike the abuse of emojis and images inside what's supposed to be a work-enabling medium. Of course, connecting to Slack via IRC, I just don't see the content not meant for me.
The real motivation is they want to control the full user experience.
Well, they have lost me as a user. The day my IRC client fails to connect to Slack, I will delete my user account. They already had record of all of my interactions using their system. Maybe I won't be able to move any of the groups I am part of away from Slack – But many of us can help create a flood.
Say no to predatory tactics. Say no to Embrace, Extend and Extinguish. Say no to Slack.
See also @Carl Chenet, another Debian developer, post The Slack Threat.

Btw. I never used Slack, but some people still try to drag me into it. I stay with XMPP, and in IRC by means of the biboumi XMPP-IRC gateway.

#xmpp #slack #irc #walledgarden #federation #biboumi #debian
 

Berlin XMPP meetup a.k.a. eXciting Monday Public Powwow



Monday, 2018-02-26, 19:00 CET



co.up, Adalbertstr. 7—8, 3rd floor, 10999 Berlin-Kreuzberg

Let's talk about Movim, and about the XMPP Summit!



This time, we will talk about Movim (the "kick ass social network"!), and about the latest XMPP Summit, which took place in Brussels a few weeks ago. Hope to see you all on Monday!
Language will probably be English or German. Or Volapük. Let's see.

#xmpp #jabber #summit #movim #berlin #federation #socialnetwork
 

Help translate Movim!



If you know English plus another language, this is for you! Please help with the translation of Movim at its translation page. At the moment German and French are almost complete, no help needed now. The following languages are nearing completion (≥¾), so this might be the perfect moment to achieve 100% without having to work much:

Russian, Norwegian Bokmål (Norway), Portuguese (Brazil), Chinese (China), Polish, Italian, Dutch, Spanish, and Danish.

Of course, all other languages are welcome, too! This is your chance to participate in free software, open source, and federation, without having to be a programmer :~)

(Btw. I never worked with transifex myself, so please do not ask me about it.)

What is Movim anyway? It is a free software, federated, social network, but very differerent from Diaspora, based on the XMPP standard. You can try it e.g. here or check the more or less up-to-date pod list.

#help #translation #movim #xmpp #federation #languages #freesoftware #i18n
 

The Jabber Spam Fighting Manifesto

Version 0.3, 2017-12-30

The Jabber network (a federated set of thousands of servers with many
tens or hundreds thousands of users) is under a continuous flood of spam
messages for multiple years. Similar to the open email relays of the
mid-1990s, public (and often abandoned) XMPP servers are being abused to
deliver those messages.

We, as the operators of public XMPP servers, commit to the following
Server Policies to fight spam on our servers, and we announce our intent
to block incoming communication from public servers that distribute spam
messages and do not adhere to the Server Policies. Furthermore, we
will inform other Public Server operators and the general public of
domains sending spam and not reacting to abuse reports.

Server Policies



A Public Server is an XMPP server that allows both the registration of
accounts by third parties (either via [In Band Registration][XEP-0077]
or by other means, like a web form), and federation to other XMPP
servers, making it possible for its users to reach out to other XMPP
domains.

The operators of a Public Server shall perform the following actions to
fight spam:

* Implement [XEP-0157: Contact Addresses for XMPP Services][XEP-0157] and
react to incoming abuse reports in a timely fashion.

* Limit the number of new user registrations per IP address and hour.

* Monitor or block registrations from IP addresses with bad reputation
(open proxy servers, Tor exit nodes), or enforce additional checks on
those users, like a CAPTCHA or a valid phone number.

* Throttle the traffic from local clients, especially unsolicited
subscription requests and messages.

[XEP-0077]: https://xmpp.org/extensions/xep-0077.html
[XEP-0157]: https://xmpp.org/extensions/xep-0157.html

Schedule



With our signature under this Manifesto, we assure that our servers are
already following the above stated Server Policies.

Starting with July 1st, 2018, we will start blocking incoming server
connections from Public Servers not following the Server Policies above,
if those are forwarding spam messages to our users. The blocking message
will contain a reference to this Manifesto.

Committment



Signed,

Georg Lukas, yax.im (https://yaxim.org/yax.im/)

...
#xmpp #jabber #spam #spim #yaxim #draft #federation #abuse #server #s2s #manifesto
 

Gajim 1.0.0-alpha2 (= 0.98.2) now in Debian 9 stable (stretch-backports)



Just sudo apt install -t stretch-backports gajim gajim-pgp gajim-omemo gajim-httpupload gajim-urlimagepreview and start chatting.

#gajim #xmpp #jabber #freesoftware #release #omemo #pgp #chat #im #federation #debian #ubuntu
 

Gajim 1.0.0-alpha2 (= 0.98.2) now in Debian testing and Ubuntu bionic



Just sudo apt install gajim gajim-pgp gajim-omemo gajim-httpupload gajim-urlimagepreview and start chatting.

#gajim #xmpp #jabber #freesoftware #release #omemo #pgp #chat #im #federation #debian #ubuntu
 

Gajim 1.0.0-alpha1 (a.k.a 0.98.1) released



The developers have put a huge amount of work into this release:
* Ported to GTK3 / Python3
* Flatpak support
* Lots of refactoring
* New Emoji support
* New Chat Window design
* New StartChat Window (Ctrl+N)
* New ServerInfo Window
* AccountWindow Redesign
* Moved some encryption code out into Plugins (see PGP Plugin, Esessions Plugin)
* OTR Plugin was not ported, use OMEMO
* Added mam:1 and mam:2 support (mam:0 was removed)
* Added MAM for MUCs support
* Added support for showing XEP-0084 Avatars
* Added xmpp URI handling directly in Gajim
* Removed Gajim-Remote
* Removed XEP-0012 (Last Activity)
* Removed XEP-0136 (Message Archiving)
* Added XEP-0156 (Discovering Alternative XMPP Connection Methods)
* Added XEP-0319 (Last User Interaction in Presence)
* Added XEP-0380 (Explicit Message Encryption)
* Added Jingle FT:5 support
Congratulations!

Users of Debian unstable can already install the new version, as well as the plugins gajim-antispam, gajim-httpupload, gajim-omemo, gajim-pgp, gajim-rostertweaks, gajim-triggers, and gajim-urlimagepreview. Have fun!

#gajim #xmpp #jabber #freesoftware #release #omemo #pgp #otr #chat #im #federation #debian

https://dev.gajim.org/gajim/gajim/raw/gajim-1.0.0-alpha1/ChangeLog
 

Movim migrates its official server to ejabberd

Movim is a distributed social networking platform founded in 2010. It can be accessed using existing XMPP clients and Jabber accounts, and is a free and open source software licensed under the AGPL.

With version 0.12 released in October, Movim migrated its official server to ejabberd. Before, they were using Metronome, a Prosody fork. Today, we are chatting with Timothée Jaussoin, the founder of Movim, about this very complex migration.
...
We now have a proper packaging for our Linux distribution – Debian, which certainly makes it easier to maintain. There’s also an improved scalability and more stable CPU and memory consumption, which helps to predict hardware requirements.
...
Even if I see ejabberd more as a tool that needs integration and tuning to create a proper platform, ejabberd seems to be the more serious solution to build proper messaging systems using the XMPP protocol.
#movim #ejabberd #socialnetwork #federation #xmpp #agpl #prosody #debian #freesoftware
Movim migrates its official server to ejabberd
Today, we are chatting with Timothée Jaussoin, the founder of Movim, about this very complex migration.
 

Dino in Debian experimental



What is Dino?



Dino is a modern IM client using XMPP (Jabber) with support for both OpenPGP and OMEMO. It looks very nice and can already be used for chatting and group conversations. It is, however, not yet stable nor feature-complete. If you are looking for something like Conversations (Android XMPP client), but for the desktop, Dino is for you. If you like to have something more stable and feature-complete, try Gajim instead. I use both! :~)





Dino is written in C and Vala, uses the GTK+ UI toolkit and looks best in Gnome, XFCE, or other GTK+ based desktops. I heard about planned versions for Windows and MacOS, too, but don't hold your breath.

How to install Dino on Debian?



Since yesterday, the Dino IM client is available in the official Debian repositories, but so far only in the "experimental" distribution. To install it, Debian users have to:
$ echo deb https://deb.debian.org/debian/ experimental main | sudo tee /etc/apt/sources.list.d/experimental.list
$ sudo apt update
$ sudo apt -t experimental install dino-im


This should work on nine official and five unofficial architectures for at least unstable and testing. Not sure about stable. I'm pretty sure, that oldstable will not work.

Why the "-im" suffix for Dino in Debian?



There used to be another program, an "integrated MIDI piano roll editor and sequencer engine", by the same name in Debian. Many references to the old program still exist, so it would be problematic to recycle the name for a different purpose.

Happy chatting!



#xmpp #debian #dino #jabber #openpgp #omemo #im #federation #chat

Debian Package Tracker - dino-im

Debian Package Tracker - dino-im
 

Dino in Debian experimental



What is Dino?



Dino is a modern IM client using XMPP (Jabber) with support for both OpenPGP and OMEMO. It looks very nice and can already be used for chatting and group conversations. It is, however, not yet stable nor feature-complete. If you are looking for something like Conversations (Android XMPP client), but for the desktop, Dino is for you. If you like to have something more stable and feature-complete, try Gajim instead. I use both! :~)




Dino is written in C and Vala, uses the GTK+ UI toolkit and looks best in Gnome, XFCE, or other GTK+ based desktops. I heard about planned versions for Windows and MacOS, too, but don't hold your breath.

How to install Dino on Debian?



Since yesterday, the Dino IM client is available in the official Debian repositories, but so far only in the "experimental" distribution. To install it, Debian users have to:
$ echo deb https://deb.debian.org/debian/ experimental main | sudo tee /etc/apt/sources.list.d/experimental.list
$ sudo apt update
$ sudo apt -t experimental install dino-im


This should work on nine official and five unofficial architectures for at least unstable and testing. Not sure about stable. I'm pretty sure, that oldstable will not work.

Why the "-im" suffix for Dino in Debian?



There used to be another program, an "integrated MIDI piano roll editor and sequencer engine", by the same name in Debian. Many references to the old program still exist, so it would be problematic to recycle the name for a different purpose.

Happy chatting!



#xmpp #debian #dino #jabber #openpgp #omemo #im #federation #chat

Debian Package Tracker - dino-im

Debian Package Tracker - dino-im
 

Prosody 0.10.0 now in Debian unstable



Users of Debian unstable can now apt install prosody prosody-modules to get the latest version. I run the packages (so far without issues) on a Debian stable system. The "clean" way would be to wait for a backport, but at the moment, it is not strictly necessary.

#debian #prosody #xmpp #federation
 



You broke the Internet



Now let's build a GNU one



Details: Yellow is for projects in development while green is for those that are available. Red illustrates brands that lose their monopoly condition once the respective layers are fully operational whereas light red indicates faulty technologies that we must replace.

Strongly recommend checking out the source website: http://youbroketheinternet.org/

Some related tags: #internet #surveillance #freesoftware #gnu #linux #security #netsec #crypto #ipfs #gpg #pgp #encryption #cryptocat #mumble #GNS #guix #nix #bittorrent #faceboogle #tor #I2P #otr #librecmc #libreboot #fsf #eff #ccc #pirateparty #pirates #ricochet #gnunet #freenet #android #replicant #grothoff #signal #libresignal #taler #gnutaler #youbroketheinternet #selfhosting #decentralization #selfhosted #tox #xmpp #jitsi #pond #PSYC #Tahoe-LAFS #retroshare #cjdns #onionshare #cryptocat #briar #maidsafe #coreboot #tribler #axolotl #zeroqm #bitmessage #cloud #skype #twitter #microsoft #rhizome #rina #netsukuku #tails #debian #freedombox #freedombone #ethos #qubes #whonix #guixSD #gentoo #zyre #reproduciblebuilds #openwrt #BMX7 #net2o #ethereum #copperheadOS #federation #dns #smtp #dane #blackadder #globaleaks #redphone #2020 #mesh #pulse #heartbeat

#youbroketheinternet

#youbroketheinternet
 

Improve #federation on #Diaspora with relay servers



It is not easy to enter federation with a small pod (with only few users), because your pod only receives posts from followed users and your post are sent only on pods where someone follows your pod users.

To improve exchange between your pod and others and I recommend to activate relay server in your config/diaspora.yml. It permits to receive posts from other pods even if you are not following any user on these pods (based on tags). It also publishes all your posts to the relay. To avoid to receive all posts, a good choice is to grab posts with pod user followed tags (see scope parameter).

Bigger pods are encouraged to publish their posts on relays to help small pods (outbound: send: true)

Just share this post with your #podmin to be sure #relay server is enabled on your #pod.

Here is a configuration sample extract from config/diaspora.yml :
<br> ## Settings related to relays<br> relay: ## Section<br> <br> ## Relays are applications that exist to push public posts around to<br> ## pods which want to subscribe to them but would not otherwise<br> ## receive them due to not having direct contact with the remote pods.<br> ##<br> ## See more regarding relays: https://wiki.diasporafoundation.org/Relay_servers_for_public_posts<br> <br> outbound: ## Section<br> ## Enable this setting to send out public posts from this pod to a relay<br> send: true<br> ## Change default remote relay url used for sending out here<br> url: 'https://relay.iliketoast.net/receive/public'<br> <br> inbound: ## Section<br> ## Enable this to receive public posts from relays<br> subscribe: true<br> <br> ## Scope is either 'all' or 'tags' (default).<br> ## - 'all', means this pod wants to receive all public posts from a relay<br> ## - 'tags', means this pod wants only posts tagged with certain tags<br> scope: tags<br> <br> ## If scope is 'tags', should we include tags that users on this pod follow?<br> ## These are added in addition to 'pod_tags', if set.<br> include_user_tags: true<br> <br> ## If scope is 'tags', a comma separated list of tags here can be set.<br> ## For example "linux,diaspora", to receive posts related to these tags<br> pod_tags: "diaspora, podmin"<br> <br>
Some clearer explanation here : https://wiki.diasporafoundation.org/Relay_servers_for_public_posts

Bad title - diaspora* project wiki

Bad title - diaspora* project wiki
 

Improve #federation on #Diaspora with relay servers



It is not easy to enter federation with a small pod (with only few users), because your pod only receives posts from followed users and your post are sent only on pods where someone follows your pod users.

To improve exchange between your pod and others and I recommend to activate relay server in your config/diaspora.yml. It permits to receive posts from other pods even if you are not following any user on these pods (based on tags). It also publishes all your posts to the relay. To avoid to receive all posts, a good choice is to grab posts with pod user followed tags (see scope parameter).

Bigger pods are encouraged to publish their posts on relays to help small pods (outbound: send: true)

Just share this post with your #podmin to be sure #relay server is enabled on your #pod.

Here is a configuration sample extract from config/diaspora.yml :
<br> ## Settings related to relays<br> relay: ## Section<br> <br> ## Relays are applications that exist to push public posts around to<br> ## pods which want to subscribe to them but would not otherwise<br> ## receive them due to not having direct contact with the remote pods.<br> ##<br> ## See more regarding relays: https://wiki.diasporafoundation.org/Relay_servers_for_public_posts<br> <br> outbound: ## Section<br> ## Enable this setting to send out public posts from this pod to a relay<br> send: true<br> ## Change default remote relay url used for sending out here<br> url: 'https://relay.iliketoast.net/receive/public'<br> <br> inbound: ## Section<br> ## Enable this to receive public posts from relays<br> subscribe: true<br> <br> ## Scope is either 'all' or 'tags' (default).<br> ## - 'all', means this pod wants to receive all public posts from a relay<br> ## - 'tags', means this pod wants only posts tagged with certain tags<br> scope: tags<br> <br> ## If scope is 'tags', should we include tags that users on this pod follow?<br> ## These are added in addition to 'pod_tags', if set.<br> include_user_tags: true<br> <br> ## If scope is 'tags', a comma separated list of tags here can be set.<br> ## For example "linux,diaspora", to receive posts related to these tags<br> pod_tags: "diaspora, podmin"<br> <br>
Some clearer explanation here : https://wiki.diasporafoundation.org/Relay_servers_for_public_posts

Bad title - diaspora* project wiki

Bad title - diaspora* project wiki
 

Improve #federation on #Diaspora with relay servers



It is not easy to enter federation with a small pod (with only few users), because your pod only receives posts from followed users and your post are sent only on pods where someone follows your pod users.

To improve exchange between your pod and others and I recommend to activate relay server in your config/diaspora.yml. It permits to receive posts from other pods even if you are not following any user on these pods (based on tags). It also publishes all your posts to the relay. To avoid to receive all posts, a good choice is to grab posts with pod user followed tags (see scope parameter).

Bigger pods are encouraged to publish their posts on relays to help small pods (outbound: send: true)

Just share this post with your #podmin to be sure #relay server is enabled on your #pod.

Here is a configuration sample extract from config/diaspora.yml :
<br> ## Settings related to relays<br> relay: ## Section<br> <br> ## Relays are applications that exist to push public posts around to<br> ## pods which want to subscribe to them but would not otherwise<br> ## receive them due to not having direct contact with the remote pods.<br> ##<br> ## See more regarding relays: https://wiki.diasporafoundation.org/Relay_servers_for_public_posts<br> <br> outbound: ## Section<br> ## Enable this setting to send out public posts from this pod to a relay<br> send: true<br> ## Change default remote relay url used for sending out here<br> url: 'https://relay.iliketoast.net/receive/public'<br> <br> inbound: ## Section<br> ## Enable this to receive public posts from relays<br> subscribe: true<br> <br> ## Scope is either 'all' or 'tags' (default).<br> ## - 'all', means this pod wants to receive all public posts from a relay<br> ## - 'tags', means this pod wants only posts tagged with certain tags<br> scope: tags<br> <br> ## If scope is 'tags', should we include tags that users on this pod follow?<br> ## These are added in addition to 'pod_tags', if set.<br> include_user_tags: true<br> <br> ## If scope is 'tags', a comma separated list of tags here can be set.<br> ## For example "linux,diaspora", to receive posts related to these tags<br> pod_tags: "diaspora, podmin"<br> <br>
Some clearer explanation here : https://wiki.diasporafoundation.org/Relay_servers_for_public_posts

Bad title - diaspora* project wiki

Bad title - diaspora* project wiki
 

Improve #federation on #Diaspora with relay servers



It is not easy to enter federation with a small pod (with only few users), because your pod only receives posts from followed users and your post are sent only on pods where someone follows your pod users.

To improve exchange between your pod and others and I recommend to activate relay server in your config/diaspora.yml. It permits to receive posts from other pods even if you are not following any user on these pods (based on tags). It also publishes all your posts to the relay. To avoid to receive all posts, a good choice is to grab posts with pod user followed tags (see scope parameter).

Bigger pods are encouraged to publish their posts on relays to help small pods (outbound: send: true)

Just share this post with your #podmin to be sure #relay server is enabled on your #pod.

Here is a configuration sample extract from config/diaspora.yml :
<br> ## Settings related to relays<br> relay: ## Section<br> <br> ## Relays are applications that exist to push public posts around to<br> ## pods which want to subscribe to them but would not otherwise<br> ## receive them due to not having direct contact with the remote pods.<br> ##<br> ## See more regarding relays: https://wiki.diasporafoundation.org/Relay_servers_for_public_posts<br> <br> outbound: ## Section<br> ## Enable this setting to send out public posts from this pod to a relay<br> send: true<br> ## Change default remote relay url used for sending out here<br> url: 'https://relay.iliketoast.net/receive/public'<br> <br> inbound: ## Section<br> ## Enable this to receive public posts from relays<br> subscribe: true<br> <br> ## Scope is either 'all' or 'tags' (default).<br> ## - 'all', means this pod wants to receive all public posts from a relay<br> ## - 'tags', means this pod wants only posts tagged with certain tags<br> scope: tags<br> <br> ## If scope is 'tags', should we include tags that users on this pod follow?<br> ## These are added in addition to 'pod_tags', if set.<br> include_user_tags: true<br> <br> ## If scope is 'tags', a comma separated list of tags here can be set.<br> ## For example "linux,diaspora", to receive posts related to these tags<br> pod_tags: "diaspora, podmin"<br> <br>
Some clearer explanation here : https://wiki.diasporafoundation.org/Relay_servers_for_public_posts

Bad title - diaspora* project wiki

Bad title - diaspora* project wiki
 

Federated XMPP chat (and more) with Movim: A success story



Some fundamental information about the XMPP based movim social network.

#xmpp #jabber #movim #federation #freesoftware #socialnetwork #php

Federated XMPP chat (and more) with Movim: A success story

There are many reasons to be unhappy with current social media sites and chat applications. For a long time, there was no viable alternative, especially not, if you wanted usability and integration. Now there is hope, with Movim.
The downsides of OSNs
Online Social Networks, such as Facebook or Go
 

Federated XMPP chat (and more) with Movim: A success story



Some fundamental information about the XMPP based movim social network.

#xmpp #jabber #movim #federation #freesoftware #socialnetwork #php

Federated XMPP chat (and more) with Movim: A success story

There are many reasons to be unhappy with current social media sites and chat applications. For a long time, there was no viable alternative, especially not, if you wanted usability and integration. Now there is hope, with Movim.
The downsides of OSNs
Online Social Networks, such as Facebook or Go
 

Are decentralized services unable to innovate?



Talk by freelance journalist Hanno Böck (Golem, Süddeutsche, Zeit, taz) about the ongoing feature race between closed services, such as Signal, and federated ones, like XMPP.
While Signal technically is free software it doesn't feel like free software.

You can change it, but then you're no longer welcome in the Signal ecosystem and can't send messages to other Signal users.

#xmpp #jabber #signal #33c3 #freesoftware #federation

Are decentralized services unable to innovate?

 
Encrypted messengers: Why Riot (and not Signal) is the future

http://www.titus-stahl.de/blog/2016/12/21/encrypted-messengers-why-riot-and-not-signal-is-the-future/
But Riot has other advantages that make it, in some aspects, superior to Signal. Riot is based on the so-called Matrix protocol which is a federated protocol. That means that anyone who wants can run a Matrix server can do so and Riot users from all these servers can communicate with one another. There is no central instance that controls Matrix or Riot.

#privacy #encryption #messaging #federation

Encrypted messengers: Why Riot (and not Signal) is the future - Titus Stahl

As a response to the Snowden revelations, the number of messaging apps that promise security against surveillance has rapidly multiplied. There seems …
 

#Federation, #Privacy, and User Experience – Medium



#signal #XMPP #decentralization

https://medium.com/@dwdbah/federation-privacy-and-user-experience-c158547f07f5#.jo1wmapbm

Medium

Welcome to Medium, a place to read, write, and interact with the stories that matter most to you. Every day thousands of new voices share…
 

#Federation, #Privacy, and User Experience – Medium



#signal #XMPP #decentralization

https://medium.com/@dwdbah/federation-privacy-and-user-experience-c158547f07f5#.jo1wmapbm

Medium

Welcome to Medium, a place to read, write, and interact with the stories that matter most to you. Every day thousands of new voices share…
 

Decentralisation, federation and data export



In response to a recent announcement (https://diasp.eu/posts/4907563), when is full data export/import going to be possible? What is the priority level of this essential feature of de-centralisation?

#podmin #diaspora #bug #question #dataexport #decentralisation #federation

I'm sorry to announce that, after 3 years of service, I will close ...

I'm sorry to announce that, after 3 years of service, I will close this Pod on the 23rd of December.
The reason is that I lost interest in maintaining the Pod, and since I will move my other services to a cheaper server I figured that this might be a good time to put an end to this.
Please download all your data prior to this date, so you can maybe transfer them to a new Pod in the future (given the Account Migration Feature ever gets implemented).
Thanks for the great time and see you somewhere else maybe :)
#podmin #diaspora
 
#interesting #network #statistics of any #hub of the #federation... for all #hubs'n more clic #picture!

the federation - a statistics hub

Podlist and statistics for The Federation (diaspora*, Friendica, Hubzilla).
 

Poezio 0.10 released



This is another console based XMPP chat client, written in Python.

I'll stay with profanity for console jabbering for now, because it is already in Debian, while Poezio is being worked on. It is nice to have so many options for different needs and tastes with XMPP, while other IM systems do not offer anything for console users.

#xmpp #console #freesoftware #federation #debian

Poezio 0.10

 

Resisting the centralization of network infrastructure



https://lwn.net/Articles/697398/ Keynote by Mr GnuPG Werner Koch at GUADEC 2016:
Today, the new attempt is Keybase.io, which many users like for its convenience (linking PGP keys to social media accounts). But it fundamentally violates the end-to-end privacy principle of PGP by binding keys to privacy-invading services. Periodically, he said, proposals pop up to implement "validating" PGP keyservers—but none of them work in a decentralized fashion. He urged users to stand up against all attempts to centralize PGP.

Finally, he looked at federation in general. Mail servers have more and more difficulty interoperating, he said, and XMPP has "lost its track" and is being replaced by centralized systems like WhatsApp and Signal. He encouraged developers to make federation a priority and to design for it from the beginning.

Note: If you are not subscribed to LWN, you cannot yet read the article, but it will be open in one week. Be patient, the article is worth it. Or subscribe to LWN, they deserve more subscribers!

#decentralization #federation #gnupg #openpgp #xmpp #signal #keybase #keybaseio

Subscription required [LWN.net]

 

Salut à Toi 0.6.1 arrived in Debian unstable!



https://tracker.debian.org/news/789255

Great news! This makes it easy to try out SàT before its next "big" release 0.7!

Unfortunately, the Libervia web interface is not yet packaged, because of its dependency of Pyjamas, which is currently not in Debian. Volunteers welcome.

#debian #salutatoi #xmpp #federation #freesoftware #socialnetwork #jabber

Debian Package Tracker

 

XMPP: Chat with a Future



https://netfuture.ch/2016/07/xmpp-chat-with-a-future/

Originally written as a response to a mail in which someone expressed their disappointment about the state of XMPP, Marcel Waldvogel, Professor of Computer and Information Science at University of Konstanz, wrote an enlightening article about extensibility, vendor-independence, and openness of XMPP, which he sees as both curse and blessing.

#xmpp #federation #chat #instantmessaging #jabber

XMPP: Chat with a Future | Netfuture

 

Easy XMPP



Georg Lukas writes:
in the last weeks we've seen that XMPP is too hard for the WhatsApp generation. Instead of blaming them for not understanding federation, we should make it as easy as possible to use XMPP (IM) in a secure fashion.

#xmpp #federation #im

[Standards]Easy XMPP

 

Do you trust it?



Got a software or service of dubious origin that you're not sure you can trust? Quick checklist:
  • If you can't see the code, you can't trust it.
  • If you can't host it, you can't trust it.
In short, go #freesoftware, go #P2P, go #decentralized or go home!

#federation #federated #saass #saas #services
 



You broke the Internet



Now let's build a GNU one



Details: Yellow is for projects in development while green is for those that are available. Red illustrates brands that lose their monopoly condition once the respective layers are fully operational whereas light red indicates faulty technologies that we must replace.

Strongly recommend checking out the source website: http://youbroketheinternet.org/

Some related tags: #internet #surveillance #freesoftware #gnu #linux #security #netsec #crypto #ipfs #gpg #pgp #encryption #cryptocat #mumble #GNS #guix #nix #bittorrent #faceboogle #tor #I2P #otr #librecmc #libreboot #fsf #eff #ccc #pirateparty #pirates #ricochet #gnunet #freenet #android #replicant #grothoff #signal #libresignal #taler #gnutaler #youbroketheinternet #selfhosting #decentralization #selfhosted #tox #xmpp #jitsi #pond #PSYC #Tahoe-LAFS #retroshare #cjdns #onionshare #cryptocat #briar #maidsafe #coreboot #tribler #axolotl #zeroqm #bitmessage #cloud #skype #twitter #microsoft #rhizome #rina #netsukuku #tails #debian #freedombox #freedombone #ethos #qubes #whonix #guixSD #gentoo #zyre #reproduciblebuilds #openwrt #BMX7 #net2o #ethereum #copperheadOS #federation #dns #smtp #dane #blackadder #globaleaks #redphone #2020 #mesh #pulse #heartbeat

#youbroketheinternet

#youbroketheinternet
 
nuovi vecchi