Beehaw
  • Communities
  • Create Post
  • search
    Search
  • Login
  • Sign Up
mozz ( mozz@mbin.grits.dev )  to Technology · 2 years ago

FireChat was a tool for revolution. Then it disappeared.

www.fromjason.xyz

external-link
message-square
16
link
fedilink
  • cross-posted to:
  • hackernews@lemmy.smeargle.fans
65
external-link

FireChat was a tool for revolution. Then it disappeared.

www.fromjason.xyz

mozz ( mozz@mbin.grits.dev )  to Technology · 2 years ago
message-square
16
link
fedilink
  • cross-posted to:
  • hackernews@lemmy.smeargle.fans
With FireChat, people were free to communicate and coordinate with each other without the message having to first filter through someone's data center. Why did the app shut down without notice?
alert-triangle
You must log in or # to comment.
  • perishthethought ( perishthethought@lemm.ee ) 
    link
    fedilink
    English
    arrow-up
    41
    ·
    2 years ago

    Should have been open sourced from day one.

    • Rentlar ( Rentlar@lemmy.ca ) 
      link
      fedilink
      arrow-up
      20
      ·
      2 years 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 ( webghost0101@sopuli.xyz ) 
        link
        fedilink
        arrow-up
        3
        ·
        2 years ago

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

  • ᗪᗩᗰᑎ ( KLISHDFSDF@lemmy.ml ) 
    link
    fedilink
    arrow-up
    39
    ·
    2 years 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 ( xnx@slrpnk.net ) 
      link
      fedilink
      arrow-up
      6
      ·
      2 years ago

      Android only sadly

      • flux ( flux@beehaw.org ) 
        link
        fedilink
        arrow-up
        6
        ·
        2 years 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 ( Kissaki@beehaw.org ) 
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 years 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).

      • Christoph Schmees ( PC_Fluesterer@social.tchncs.de ) 
        link
        fedilink
        arrow-up
        2
        ·
        2 years ago

        @xnx @KLISHDFSDF
        s/sadly/naturally/
        With Apple you get tracking and surveillance built-in. The Android world has clean custom-ROMS.
        https://www.aalto.fi/en/news/keeping-your-data-from-apple-is-harder-than-expected
        https://proton.me/blog/iphone-privacy
        https://krebsonsecurity.com/2022/10/accused-raccoon-malware-developer-fled-ukraine-after-russian-invasion/

      • 6jarjar6 ( 6jarjar6@lemmy.sdf.org ) 
        link
        fedilink
        arrow-up
        1
        ·
        2 years ago

        What about Session, the Signal fork?

        • The Cuuuuube ( Cube6392@beehaw.org ) 
          link
          fedilink
          English
          arrow-up
          2
          ·
          2 years ago

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

        • XNX ( xnx@slrpnk.net ) 
          link
          fedilink
          arrow-up
          2
          ·
          2 years ago

          That is meshnet based

          • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍 ( sxan@midwest.social ) 
            link
            fedilink
            arrow-up
            1
            ·
            2 years 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 ) 
              link
              fedilink
              arrow-up
              2
              ·
              2 years 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

            • XNX ( xnx@slrpnk.net ) 
              link
              fedilink
              arrow-up
              1
              ·
              2 years ago

              The point is being able to communicate when the internet is shut off

    • Kissaki ( Kissaki@beehaw.org ) 
      link
      fedilink
      English
      arrow-up
      4
      ·
      edit-2
      2 years 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 ( Kissaki@beehaw.org ) 
    link
    fedilink
    English
    arrow-up
    16
    ·
    2 years 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.”

Technology

technology

Subscribe from Remote Instance

Create a post
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !technology@beehaw.org

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:

  • Free and Open Source Software
  • Programming
  • Operating Systems

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

Visibility: Public
globe

This community can be federated to other instances and be posted/commented in by their users.

  • 73 users / day
  • 545 users / week
  • 1.9K users / month
  • 4.92K users / 6 months
  • 5.11K local subscribers
  • 43.7K subscribers
  • 6.44K Posts
  • 107K Comments
  • Modlog
  • mods:
  • Chris Remington ( remington@beehaw.org ) 
  • alyaza [they/she] ( alyaza@beehaw.org ) 
  • TheRtRevKaiser ( TheRtRevKaiser@beehaw.org ) 
  • gyrfalcon ( gyrfalcon@beehaw.org ) 
  • rs5th ( rs5th@beehaw.org ) 
  • coldredlight ( coldredlight@beehaw.org ) 
  • Leigh ( SemioticStandard@beehaw.org ) 
  • TheRtRevKaiser ( TheRtRevKaiser@kbin.social ) 
  • BE: 0.19.15
  • Modlog
  • Legal
  • Instances
  • Docs
  • Code