111–120 of 422 posts
Back in the day before the rise of Facebook, there was an open source service that combined all the popular messaging protocols - MSN, AoL, IRC, etc. It was called Pidgin[0], and it never got particularly big. I see the same thing here. While it's interesting, I'm failing to see what the use case is. What's the niche that needs this solved in a big way? [0] https://www.pidgin.im/
This is nicely timed. Brief history: when Hangouts was going away and Google Chat coming in, I pitched Matrix to my friends as a better alternative that didn't require unique phone numbers, awkward desktop limitations, and a better federated future. We stuck with Google Chat because inertia and networks suck that way. I revisited the instance I had setup and got the mautrix-googlechat bridge working. It's pretty nice…
Beeper implements Google Chat. I've been using it, it works really well. https://www.beeper.com/
Earlier quoted context omitted.
> I see the same thing here. While it's interesting, I'm failing to see what the use case is. What's the niche that needs this solved in a big way? I used Pidgin a lot. I always found it very convenient to have everything in one place and UI. Better one client than MSN + AOL + ICQ + IRC + Yahoo! + XMPP. In the last few years I haven't used it much, but that's because it just doesn't support the popular messaging apps…
Pidgin was extremely convenient. But it was commoditizing messaging platforms so of course it had to be shot in the head by them.
> It’s also worth noting that end-to-end encryption is necessarily broken as messages to (and from) WhatsApp, Signal and Telegram pass across the bridge(s). The bridge(s) operates in Element’s trusted EMS environment, with no content scanning or datamining, but currently bridged conversations are not stored end-to-end encrypted in Matrix (they will be in the future). As a Signal user, I kind of don't want this to tak…
Does anyone know what this product is based on? Is it just a ready-made image with all the bridges preconfigured (and prerequisites such as a small android vm for a viable whatsapp bridge), or has there been some evolution on the existing package? Is there documentation on what was done to achieve this? Purely on the content of the article: Given that the messages are not stored encrypted locally and that this servic…
I've been running the Signal bridge for a couple of months and it seems pretty unstable. Sometimes it stops delivering messages and I have to restart either signald or the bridge. At other times, it broke completely and started working again only after a couple of days, when I updated signald. I haven't tried the WhatsApp bridge yet because it needs to go through my phone or an Android VM. WhatsApp recently announced…
> It’s also worth noting that end-to-end encryption is necessarily broken as messages to (and from) WhatsApp, Signal and Telegram pass across the bridge(s). The bridge(s) operates in Element’s trusted EMS environment, with no content scanning or datamining, but currently bridged conversations are not stored end-to-end encrypted in Matrix (they will be in the future). As a Signal user, I kind of don't want this to tak…
I want this to take off. I'm tired of having to follow trends because people suddenly think there's a new shinyshinytrendy thing around: IRC to ICQ to MSN to Skype to Google Talk to Facebook Messenger to Whatsapp to Signal. Pidgin is good (I also miss the ancient Trillian, even though it was closed source), but limited to a local device. There are XMPP Transports as well for these (see https://git.eta.st/eta/whatsxmp…
> It’s also worth noting that end-to-end encryption is necessarily broken as messages to (and from) WhatsApp, Signal and Telegram pass across the bridge(s). The bridge(s) operates in Element’s trusted EMS environment, with no content scanning or datamining, but currently bridged conversations are not stored end-to-end encrypted in Matrix (they will be in the future). As a Signal user, I kind of don't want this to tak…
I want this to take off. I'm tired of having to follow trends because people suddenly think there's a new shinyshinytrendy thing around: IRC to ICQ to MSN to Skype to Google Talk to Facebook Messenger to Whatsapp to Signal. Pidgin is good (I also miss the ancient Trillian, even though it was closed source), but limited to a local device. There are XMPP Transports as well for these (see https://git.eta.st/eta/whatsxmp…
Even if we disregard that, I can honestly say that I don't think using four separate apps is a problem. I don't even think using ten different apps is a problem, because it's mostly transparent to the user anyway. You get (configurable) notifications from all of them when you need to care about something, and the "sharing" feature on both iOS and Android these days is normally smart enough to figure out who, or at least which app, you want to share something to -- so for me this "multi app confusion" is already pretty well solved on an OS level, at least on mobile.
> It’s also worth noting that end-to-end encryption is necessarily broken as messages to (and from) WhatsApp, Signal and Telegram pass across the bridge(s). The bridge(s) operates in Element’s trusted EMS environment, with no content scanning or datamining, but currently bridged conversations are not stored end-to-end encrypted in Matrix (they will be in the future). As a Signal user, I kind of don't want this to tak…
What you know is that unless their device is compromised, it is up to them to decide who can read the messages that you send to them.
Thus the situation with the bridge is not in reality different from the situation now.