Definitely going to look into this when I have the time. If it's not using your Apple ID for authentication (like the article says), what's to stop anyone from spoofing anyone else's phone number?

The pypush readme doesn't have a lot of details so I guess I'll just need to try it to see.

Edit: Looks like he's distributing "a framework from an old version of macOS, in order to call some obfuscated functions", which the script pulls from his GitHub. This is likely a copyright violation. If Beeper Mini is doing the same thing, I'd expect them to get sued into oblivion the second Apple takes notice.

It's not clear which version of macOS he pulled this from. There's always the risk that Apple will simply axe support for it. I don't recall them breaking support for older OSes with iMessage in the past but I haven't followed that closely so I'm not sure.

Update:

Just ran it on my desktop. It immediately prompts for a username and password, presumably for an Apple ID. I didn't continue because I don't want to use my real Apple ID. The article says Beeper Mini doesn't need an Apple ID at any point. After a little searching, it looks like iPhones actually don't need an Apple ID to use iMessage. I was not aware of that. So I guess Beeper is not using the exact same mechanism as pypush.

I think it's awesome that they paid the dev. More companies should do that for open source projects

In the future, we are planning to add Matrix network support back in, along with support for the 15 other chat networks in Beeper Cloud. Read more about our roadmap.

from the beepers own post instead of this reblog

Beeper Mini is also unfortunately closed source

Yes. Hopefully they'll continue to maintain the mautrix bridges they already have.

Also it's sad to see Beeper misusing the term open source for the source available SSPL [1]. Beeper is free not to use an open source license. But an open source "license must not restrict anyone from making use of the program in a specific field of endeavor" [2], so it's misleading to call their demo [3] open source.

I do believe supporting the different messaging services client side could be a better experience than relying on a server to translate between different protocols.

[1] https://blog.opensource.org/the-sspl-is-not-an-open-source-license/

[2] https://opensource.org/osd/

[3] https://github.com/JJTech0130/pypush

Stock pixel is giving me error.null when trying to sign in, I think the release is just bugged

I just want better upload limits which RCS gives us. So personally, I'm indifferent.

Upset about getting curved by the only Tinder match they'd had in months after she saw their green bubble

It basically copies the best of every other messaging platform. I was at my in-laws where everyone on my wife's side has an iPhone and we're talking about a LOT of the features.

• can tell if notifications are turned off on phone
• read receipts
• higher quality limit on video/pictures sent
• messaging that can be done in wifi-only areas (imagine having a few group threads/people you CANT talk to while at home because you live in a dead zone)

Any other big feature of any other messaging app I was able to think of (Signal/Whatsapp, discord, slack) is all there (except public chatrooms and private servers obvs), WITH OS integration

I still like my pixel, but I get it now.

Still holding out hope that Google allows for RCS features to come to Google voice.

It's not about the color, sms is an ancient and limited piece of tech

People care about the color of the bubble, even if you don't. A LOT of place's don't regularly use SMS.

No, its a new app! They built specifically for iMessage only. Learn more here: https://blog.beeper.com/p/introducing-beeper-mini-get-blue

I'm confused about this article because I have Beeper, but they make this statement:

"Beeper Mini is a new app from the folks behind Beeper, a unified chatting and inbox app that brings together the best chat apps under one roof."

I haven't heard about a mini version.