FireChat was a tool for revolution. Then it disappeared.
Content warning: FireChat was a tool for revolution. Then it disappeared. #technology #privacy #firechat #mesh
like this
Content warning: FireChat was a tool for revolution. Then it disappeared. #technology #privacy #firechat #mesh
like this
perishthethought
in reply to mozz • • •Rentlar
in reply to perishthethought • • •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
in reply to Rentlar • • •ᗪᗩᗰᑎ
in reply to mozz • • •What's wrong with Briar? https://briarproject.org/
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.
Secure messaging, anywhere - Briar
briarproject.orgXNX
in reply to ᗪᗩᗰᑎ • • •6jarjar6
in reply to XNX • • •XNX
in reply to 6jarjar6 • • •𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍
in reply to XNX • • •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?
XNX
in reply to 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 • • •ᗪᗩᗰᑎ
in reply to 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 • • •For anyone considering Session messenger:
The Session developers dropped Perfect Forward Secrecy because it would be hard to work around it.
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:
Source: https://en.wikipedia.org/wiki/Forward_secrecy
The Session devs also claim:
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
The Session Protocol: What’s changing — and why - Session Private Messenger
SessionThe Cuuuuube
in reply to 6jarjar6 • • •flux
in reply to XNX • • •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
in reply to XNX • • •https://code.briarproject.org/briar/briar/-/wikis/FAQ#will-there-be-an-ios-version-of-briar
FAQ · Wiki · briar / briar · GitLab
GitLabKissaki
in reply to ᗪᗩᗰᑎ • • •Kissaki
in reply to mozz • • •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?
"Nobody knows anything, but let me claim this anyway."