close
  • chevron_right

    News is spreading that Google will replace classic Hangouts with Hangouts Chat and Hangouts Meet.

    ericbuijs – Sunday, 27 January - 15:57 edit

I've used #Hangouts for a considerable amount of time but this is a good incentive to try something else, something FLOSS rather. While I'm pretty happy with the Fediverse social networks I haven't been able to find a chat service in the Fediverse. Perhaps the social networks protocols of the Fediverse aren't very suitable for chat. Earlier I had some good experience setting up a #chat with Movim so the coming period I'll start evaluating #Movim as a replacement for Hangouts.

  • favorite

    2 Like

    debacle , Timothée Jaussoin

  • 1 Comments

  • 2 February debacle

    Note, that I tried 1:1 video phone calls via the Movim web interface successfully. Not so bad.

  • chevron_right

    Free and open source software to create a forum or a community

    Timothée Jaussoin – Friday, 25 January - 16:28 edit

Happy so see some feedback on #Movim and a little overview of #community management with #FLOSS.


  • share chevron-right

    Free and open source software to create a forum or a community

    I wrote a blog post about #FLOSS software to create and maintain a community or a forum. It's an extended version of my earlier post on this topic.

    group_work open-source-software 25 January

  • favorite

    4 Like

    Marzanna , Guillaume CHILLOUX , Mike , Michał "phoe" Herda

  • 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

  • person chevron_right

    bronfida – Wednesday, 9 January - 01:21 edit

    Omg, I just discovered #movim and I think it's the best thing since sliced bread

  • favorite

    4 Like

    Timothée Jaussoin , User , annataure , argy

  • Op chevron_right

    FLOSS software for forums or communities

    ericbuijs – news.movim.eu / open-source-software – Thursday, 3 January - 10:32 edit

Introduction

With the demise of G+ a lot of community owners are suddenly looking for a new home. Since a lot of G+ users despise FaceBook (and rightfully so) other social networks are mentioned. The problem with a lot of these networks is that they are centralized and proprietary making the users depending on the whims of the owner of the network. Below I summerize the FLOSS options for people interested in setting up a community. This is not an exhaustive list. I encountered these options after discussions often on G+ and I experimented with some of these options during the last couple of months.

Self-hosted or not

An important decisions is whether or not to host the forum or community yourself. If you want to host it yourself you'll keep full control of the server however the maintenance is considerably more than with a non-selfhosted solution. You also need to install the software on a server and configure it.

Friendica, Osada (self hosting possible)

Both are macroblogging social media networks that offer the possibility to create a forum. I found the Osada forum particularly easy to set-up and maintain. The UI of both doesn't look very modern but the functionality needed to use and maintain a forum is all there.

Movim (self hosting possible)

Movim is social platform that let you share and chat. But it's also possible once you've created an account to create a community. The UI looks modern but some forum admin features are missing (or I couldn't find them). As an example as an owner I couldn't ban someone from the community.

Flarum (only self hosting)

Open source forum software that is currently in beta. Nice, modern UI. I've read some concerns about the beta status and the stability of Flarum.

NodeBB (self hosting possible)

Open source forum software with a modern UI. You can either self host for free or use a NodeBB hosting plan that comes with a price tag.

#Friendica #Osada #Movim #Flarum #NodeBB #social

  • chevron_right

    Contact publication

    Thomas – Thursday, 6 December - 12:56 edit

Hallo Movim! Ich teste Dich mal unter de.movim.eu, eingeloggt mit einem XMPP-Account auf meinem privaten XMPP-Server (prosody 0.11.0). Ich verstehe noch nicht so ganz, wo welche Daten gespeichert werden, aber Deine Oberfläche gefällt mir schon ziemlich gut!
#xmpp #movim #prosody #neuHier
  • favorite

    3 Like

    Udo Rader , Kristian , Timothée Jaussoin

  • 1 Comments

  • person

    7 December Kristian

    Bekannte Avatare. Hallo hier. ;)