Changement de compte diaspora*
CNT 31 · Friday, 8 October, 2021 - 18:40
Do you like it?
debacle · Sunday, 24 January, 2021 - 13:24 edit · 1 minute
I'm referring to postings only, not chat.
Social networks are all getting high by the alternation of Adrenaline and Dopamine, intensified by the occasional dose rate of Caffeine, when geting #likes.
- On Movim, I can get information about recent likes in the notifications, but I would like to have an overview about all likes I ever got.
- Also, I'm missing an overview about all postings, that I liked at some point.
- In social networks one can find like-minded people. How about notifying me, when posting I liked or commented on, get more likes or comments by others? #Diaspora does this.
- Movim only allows for a like, but not for any other reaction. Message Reactions OTOH, allow for multiple, different #reactions, which I find more interesting.
- If a network becomes larger, fraud and abuse will be quick to follow. I'll post "vi is great", wait for some likes, and the correct the post to "Emacs is great". My likers will not even get a notification, nor is there a change history. Diaspora "solves" this by not allowing changes of posts, which is horrible - I can't even fix my typos. #Mastodon seems to replace the orginal post with a complete new one on change - losing answers and likes (favourites). Therefore:
- Likers must be notified, if a posting they liked has been altered, so that they can decide to remove their reaction.
- A change history should be visible.
- When talking about fraud and abuse: At some point, it should be possible to digitally sign postings, e.g. using #OX, so that everybody can verify the authenticity of a posting. This is esp. important in a federated network, where fake sites might appear. Likewise, reactions should be optionally signed, too.
Ruslan · Sunday, 29 December, 2019 - 18:53
Dennis Schubert: ActivityPub - Final thoughts, one year later.
debacle · Sunday, 13 January, 2019 - 22:46 edit · 2 minutes
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.
Movim 0.14 - Scotty - Anniversary Edition
Timothée Jaussoin · pubsub.movim.eu / Movim · Sunday, 18 November, 2018 - 09:17 edit · 5 minutes
Movim is 10 years old and it's with a lot of satisfaction that we are bringing this version 0.14 after 9 long months of development.
Ou goal is to bring everything you need to communicate with your community, classroom, company or friend circle in one simple application. Movim can easily be deployed on a server and rely on the XMPP protocol to federate them. Therefore Movim can, by design, already communicate with many XMPP/Jabber clients and doesn't need you to create a new account if you already have an XMPP one 😋.
This new #release is coming with several core changes that greatly improved the stability and performances of the project but it also brings many design and navigation improvements to always provide you with the best experience regarding publication of content and messaging.
Movim and PHP 7.3
Movim is currently having technical issues to run on the upcoming version of PHP 7.3.
This is a known and documented issue that is caused by some incompatibilities with one of the official dependencies of PHP, php-zmq, that is used at several places in the core of the daemon.
A ticket has been open to track and give updates about this issue: Movim is not working with PHP 7.3.
Before presenting the improvements and new features let's talk a bit about what was done under the hood.
The biggest change in this version is certainly the complete replacement of the database layer from the historical, Movim specific, Modl library to the widely used Eloquent.
This work has been detailed in a previous article: From Modl to Eloquent, or how to change a social network database engine. To sum it up, it brought coherence in the database of the project and a huge performance boost on all the pages.
Without any cache involved, Movim is now loading pages in only a few hundred milliseconds.
The new database structure is also keeping good performances with a huge amount of data (millions of messages, thousands of articles on our official pods a this moment).
With Eloquent, Movim is compatible with #MySQL, #PostgreSQL but also, since this version, with #SQLite which can greatly simplify the deployment of small instances. Thanks to JKingweb for his awesome work on this port.
Packaging and dependencies
Scotty will be the first version to be packaged for the #Debian project. Big improvements were made in the dependencies of the project thanks to the work of our contributors mirabilos and nik. Several were fully removed and some are replaced with more stable and reliable ones (like the SASL library, used for the authentication). This package will come a bit later regarding the issue that we have with PHP 7.3.
Movim 0.14 is also the first version to drop the support of PHP5 (now deprecated) to focus on PHP7+.
After being a bit boring with those technical changes let's have a look at what you will find as a user in this new version.
The publication of articles is now simpler than ever and has been fully redesigned. You can quickly publish a link or upload a picture directly from the home page or you can still switch to the more complete form to write long articles (like this one 😉).
When sharing a link that contains several pictures you can now pick the one that you would like to include in your publication (or no picture at all).
The publication visibility toggle has been redesigned to be clearer as well.
The cards containing the preview of the articles were fully redesigned to be more compact and adaptable to smaller screens.
The news page, contact publications and communities are now paginated allowing simpler navigation.
If you receive articles containing NSFW content and you asked to not display them in the configuration, Movim will now display a spoiler overlay on top of them.
The search feature has been improved and now supports searching in tags as well.
The loading performances of the articles and comments were also greatly improved. Navigating between the articles feels like a breeze.
All the notifications are now grouped in a panel easily available from the main menu both on desktop and on mobile. Thanks to XMPP all those notifications are received and synchronized in real time 😀.
Those notifications contain likes, comments and invitations that you received.
Several message synchronisation issues were fixed allowing Movim to handle properly the receival and read acknowledgement of the sent messages.
The chatrooms were slightly redesigned, the moderators messages are now shown with a specific color. The messages addressed to you are also displayed with a colored border.
You can now also publish Stickers and emojis in your favorite chatrooms.
You can now use Movim to authenticate to third party websites using your XMPP account. On the websites that implement that feature, you just have to give your XMPP account and a notification will be displayed in Movim.
You just have to accept it and you'll be automatically authenticated to the external website. How easy is it?
More information there Journal of a Bot - Authentication with XMPP.
Several small bugs were also fixed in the Video Conference feature. Movim is now clearer about the state of the video session and is giving proper feedbacks if the contact hung-up.
The pictures can be directly previewed within Movim before going to the external link.
Around the project
The new redesigned version of the official website will now present more clearly what the project is about and all the exciting features that you can use within Movim.
You will also find there all the apps for your desktop (Windows, macOS, Linux) and your Android phone.
We are not done yet! There is already some plans for the upcoming release.
The 0.15 will focus on the integration of the OMEMO end to end encryption protocol. The related ticket has been reopened with more proper explanations. This will be a big risky project.
Some improvements will also be done on the suggestions of the chatrooms and communities to allow Movim users to explore and discover content more easily.
In the meantime we all invite you to try out this new version on our official instances or deploy it on your server. You will find everything to do so on the official website.
That's all folks!
Celt-Rock-Radio (sur TuneIn)
Bigou · Monday, 3 September, 2018 - 11:03 edit
Je me suis dit que je devrais, à mon tour, la partager avec vous. ;)