𝕽𝖔𝖔𝖙𝖎𝖊𝖘𝖙

  • 0 Posts
  • 32 Comments
Joined 11 months ago
cake
Cake day: June 20th, 2023

help-circle
rss


  • I’m happy to pay to support them.

    If you’d rather not pay the Beeper Cloud service is free and all of the matrix bridges it uses are open source.

    The source code behind how Beeper Mini works is available as well but will require a client of some sort to be written since you can’t just use a matrix bridge and a matrix app.

    The guy who started Beeper also created the Pebble Watch and they have always maintained open source alternatives for their bridges.

    I’m just happy that a company with those ethics is the one to take up this fight against Apple, this could have been a $10/month app from a company who believes in closed source and pushing ads/tracking users’ data.

    Beeper is a good company that actually cares about privacy and security and that should be commended.











  • Working great for me.

    And from what I’ve looked through so far of the pypush code it seems pretty legit.

    IMessage being only for iPhones is officially over.

    This isn’t something Apple can just block or patch without also affecting every iPhone that doesn’t download the patch update beforehand. Any device that isn’t patched in advance will also lose access to iMessage.

    It’s actually quite impressive how it is done and it’s truly innovative. It’s very much a significant step forward compared to the implementations we have seen before.


  • Here’s a simple picture with minimal reading required.

    This is very different to the technology used in the free/wait-list Beeper Cloud app and all the other previous attempts at an iMessage for Android app.

    To summarize:

    All messages are sent directly between your device and Apple’s servers. You do not even need an AppleID. There is a cloud server involved but it’s only job is to send push notifications to Android so they app knows when to download new messages (securely with iMessage encryption) from Apple’s servers.

    No message contents are sent through the cloud server, it just notifies your device when there are new messages. This is necessary because Apple servers obviously do not support Android push notifications.


  • Sort of.

    All messages/etc are sent using iMessage encryption directly between your phone and Apple’s iMessage servers.

    But there is no Android push notifications from Apple’s servers.

    So in order to be notified about new messages in a timely manner without killing your battery/data plan a cloud server is required to trigger your phone that a message has arrived so your phone can then request the message from Apple’s servers.

    This is actually a really common implementation, many apps use Firebase or similar to handle push notifications that are only used to trigger a “pull” of a larger chunk of data.

    The push notifications being used here don’t contain any private data, they just tell your device when to collect that private data securely.




  • Notice how in the article they say “we’re not the middle man… Any more”? That’s because, up until now, Beeper has been working on a system where they operate as a middle man for your data.

    To be fair they never claimed otherwise and all of the code for the bridges are open-sourced and can be run on your own servers so that those servers you control (as opposed to Beeper-owned servers) act as a “middle man” and none of your messages need be trusted to a 3rd party.

    To put it simply: only the actual bridge on Beeper Cloud has access to unencrypted messages and you do have the option to run the bridge yourself while continuing to use the Beeper app. You can use as many or as few self-hosted bridges as you’d like.

    A few bridges are preconfigured for self-hosting with just a couple of clicks for free through fly.io here