50
submitted 6 months ago by mozz@mbin.grits.dev to c/technology@beehaw.org
top 15 comments
sorted by: hot top controversial new old
[-] perishthethought@lemm.ee 32 points 6 months ago

Should have been open sourced from day one.

[-] Rentlar@lemmy.ca 13 points 6 months ago

Agreed. Work on capitalist principles and you end up becoming beholden to capitalist principles.

If it could be made once, could it be done again? Main thing is adoption I think, not unlike Lemmy.

[-] webghost0101@sopuli.xyz 3 points 6 months ago

This briarproject in the other comment looks similar and open source.

[-] KLISHDFSDF@lemmy.ml 26 points 6 months ago

What's wrong with Briar? https://briarproject.org/

Censorship-resistant peer-to-peer messaging that bypasses centralized servers. Connect via Bluetooth, Wi-Fi or Tor, with privacy built-in.

I think the reason these apps don't take off is the compromises they make in order to work the way they do. When you do need them, you best hope you're able to get them and get others to use them as well.

[-] xnx@slrpnk.net 5 points 6 months ago
[-] flux@beehaw.org 5 points 6 months ago

As I understand it, these kind of applications depend on being able to perform activities in the background, which is highly limited in iOS for battery efficiency reasons--and maybe for privacy.

Many years ago I was working on a project that shared connectivity details over wifi/bt, and iOS was troublesome also due to the application not being aware of the local bluetooth address.

Possibly similar issues impact other mesh networking applications on the platform.

[-] Kissaki@beehaw.org 3 points 6 months ago

https://code.briarproject.org/briar/briar/-/wikis/FAQ#will-there-be-an-ios-version-of-briar

We're looking into whether an iOS version is feasible.

A typical iOS messaging app would use a push notification to wake the app when a message is received, but this exposes metadata to Apple's push notification service and the app developer's push gateway

If we don't use push notifications then the best Apple allows us to do is wake up every 15 minutes and check for messages. But maybe the sender won't be online when we check (their 15 minute intervals might not be aligned with ours - clocks aren't perfect).

[-] 6jarjar6@lemmy.sdf.org 1 points 6 months ago

What about Session, the Signal fork?

[-] xnx@slrpnk.net 2 points 6 months ago
[-] sxan@midwest.social 0 points 6 months ago

And? It works on iOS.

I'm missing the point. Was it that systems like Briar can't work in iOS because they aren't mesh net? If so, why not choose one that does, like Session?

[-] KLISHDFSDF@lemmy.ml 2 points 6 months ago

For anyone considering Session messenger:


The Session developers dropped Perfect Forward Secrecy because it would be hard to work around it.

First things first, let’s talk about what we’re leaving behind: Perfect Forward Secrecy (PFS) and deniability.

Source: https://getsession.org/session-protocol-explained

In plain English, they dropped a security feature for their convenience to the detriment of their users' security.

For anyone unsure what PFS provides:

The value of forward secrecy is that it protects past communication.

Source: https://en.wikipedia.org/wiki/Forward_secrecy

The Session devs also claim:

Session provides protections against these types of threats in other ways — through fully anonymous account creation, onion routing, and metadata minimisation, for example.

Reading between the lines, we can interpret that as introducing security through obscurity, which is generally considered bad practice - https://cwe.mitre.org/data/definitions/656.html

[-] Cube6392@beehaw.org 2 points 6 months ago

Session has made some insecure solution surrounding important design elements like forward secrecy

[-] Kissaki@beehaw.org 1 points 6 months ago* (last edited 6 months ago)

I'm a bit confused by the app and Mailbox app for being able to receive messages while offline separation. The normal app only supports live communication between two online participants? /edit: Looks like that is indeed the case.

[-] Kissaki@beehaw.org 4 points 6 months ago

access to FireChat was completely cut off without explanation.

After establishing that FireChat establishes its own, independent mesh network, I would have at least expected more details on how it was cut off? Did it simply became unavailable on the publishers distribution? The followup text seems to indicate otherwise. Did Google and Apple as app publishers actively revoke access to already installed apps? Did the Open Garden publisher have a disabling functionality in place? Did they publish an update to disable it?

Without any information, it's hard to say why FireChat disappeared. […]

FireChat is gone because FireChat was a threat to the systems it circumvented.

"Nobody knows anything, but let me claim this anyway."

this post was submitted on 30 Apr 2024
50 points (100.0% liked)

Technology

37702 readers
409 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS