Skip Navigation

Posts
98
Comments
761
Joined
3 yr. ago

  • Huh. Kinda wild to see the Collabora dude posting his own comics to try to defend their actions of ensuring Collabora keeps getting corporate contracts. Odd situation.

  • Removed Deleted

    Permanently Deleted

    Jump
  • I never used em dashes before, but I use the shit out of bullet points, it's too good at distinguishing stuff from the rest of a comment. I'd hate to have to give those up...

  • But if the flesh of a melon is squeezed and the liquid collected, it becomes watermelon juice.

    Water juice.

  • I feel a little ashamed that I can’t understand this…

    Nothin' to be ashamed of, we're all newbies to this at first. I had to learn it too :p

    Part 1: How XMPP servers differ from XMPP Clients

    Okay, so: Movim and Conversations are both clients that can be used to login to any XMPP account. Those two clients in particular are a little bit more confusing than normal, because they also offer free XMPP accounts on their own XMPP servers (which are independent of the client software).

    To try to liken it to something familiar, it'd be like if the Thunderbird email client (which you can login to any email account with) also happened to offer a separate email hosting service too, so you could login to your SomeReallyCoolUsername@thunderbird[.]com from the Thunderbird app.

    Or to liken it to how lemmy works, if you're familiar with the Photon front-end, it can access any lemmy account, even your blahaj account, as it's just an independent front-end, it's not actually hosting the lemmy server itself.

    Part 2: How it works in practice

    So in practice, if you create an XMPP account on Movim's server, you can login into that same account right from your Conversations App too. The same would apply if you'd created an XMPP account on the Conversations server; you could login to it right from the Movim client.

    One client can also communicate with any other. Let's say you had a friend using the Conversations client, and you were on the Movim client; you could talk to each other no problem through text, or even call each other 1 on 1 with audio or video.

    Part 3: The complication :(

    But, bit of extra complication; the Conversations client hasn't yet implemented some of the features Movim is capable of. Specifically, it cannot yet do group audio/video calls or screenshare. So if you're in a chat room with your friends, and everyone is on Movim except for one friend (who's using the conversations client on their phone), if you started a group call, that one friend won't be able to join it.

    However ('But' part 2); that limitation would only crop up if someone is using the Conversations client/mobile app itself.

    If that same friend happened to have a Conversations XMPP account, they could still open Movim in a browser tab on their PC or phone and login to the Movim client with their Conversations account, and then would be able to join the call no problem.

    And that's it! :D

    Sorry if I didn't do the best job explaining that. I'm very much looking forward to the day when Conversations gets those missing features and I only need to explain the first part about how clients and XMPP accounts are separate 😅

  • and now my life has been reduced from being perhaps the best engineer in the world

    Yeah... I think we dodged a bullet when Linus didn't let his filesystem in.

  • Yep :D

    It has full searchable room history, can upload memes (gifs from either links like giphy or directly uploaded), images, video files (playable within the chat), and audio messages.

    There's also a built in paint-like thing that lets you draw directly into the chat, or annotate documents, pictures, or memes.

  • I feel like this article was written for you, based on your last paragraph (the author definitely relates).

  • Fluxer plans federation in the future, and its AGPL licensed.

    However, it's still in beta, and the backend's ability to scale is currently unproven.

    For something that's more proven, we have Movim, which is already federated with the open standard XMPP protocol.

  • Movim. Though due to how recent it was implemented, you must use a chromium based browser to stream the application's audio too.

  • It's installable as a PWA. After it's loaded up in your preferred mobile browser, you should be able to open the browser menu (the 3 dots) and add it to your homescreen as its own app (on Firefox Mobile based browsers, it's the option 'Add app to Homescreen), so that it doesn't load the browser UI.

    There are native mobile XMPP apps too that you can use with the same account, such as Monocles (Android) or Monal (iPhone) but they're not yet quite as full featured as the Movim client (they can't yet do group calls or screenshare, but can do 1 on 1 video calls).

  • Just a heads up, Gamevox is proprietary and hosts their server with AWS. Root and Teamspeak 6 are also proprietary. None of them are federated.

    I'd suggest looking at this to see why a federated FLOSS option is imperative.

  • That comment was not a promotion of Discord, but a realistic assessment of its capabilities. Those same capabilities are being implemented in Movim (which I am promoting), which is FLOSS, and built on open standards from 1999 that would make an outside corporate takeover very difficult.

    Unless you mean that even full-featured FLOSS software that's difficult to re-create are equally capable of creating a captive audience/walled garden and should be avoided? In which case, wouldn't that include things like GIMP, Krita, or even the Linux kernel itself?

  • I'd recommend reading this in-depth article to better understand the current landscape of online community/chat platforms.

  • Discord replaced everything else because it had far more features than Teamspeak. Teamspeak can only do voice chats amongst small groups of people in invite-only rooms.

    Discord could do public facing discoverable communities with drop-in voice calls, group video calls, group screensharing to stream movies or gameplay to your friends or an entire community of hundreds, markdown enabled text chats. And each of those communities could have categorized collections of chat & drop-in voice rooms with granular permissions for different users, and more recently it added built-in forums as well.

    It's truly a kitchen-sink approach, but the end result was the ability to create both small and large communities, all of which only needed a single account, and all of it streamlined so non-techies could easily use it.

  • There are already a brazilian other messengers.

    That's true, and it's a bit of a mess, but if we're looking for a more permanent home that we won't need to escape from in a few years, XMPP is pretty much the best long-term option.

    I wouldn’t say that no phone number is an advantage, matrix does not use one and it’s a pain to discover people (compared to just using the number)

    Discord did not require a phone number, but finding communities was quite easy. Curious how you would use phone numbers to discover new people or communities, unless you mean just finding your own contacts that also joined the service? The use of phone numbers also immediately makes it impossible to be anonymous from the hosting service itself.

  • It combines a lot of features that otherwise require multiple other apps to achieve the same result, and thus requires you and your friends to create multiple accounts. Not insurmountable in theory, but people are primed for convenience, so it's good to have a truly federated FLOSS replacement for that, just as Lemmy/Piefed are federated FLOSS replacements for reddit.

  • Lemmyverse.net is a very useful site to find communities that may not have federated to your instance yet (at least 1 user on your instance must be subscribed to it for it to begin federating). Especially useful for smaller instances.