bitlbee VS pypush

ah didn't realize it had gone away. its successor appears to be [0]

now I'm reliving the chaos of the late-00s/early-10s instant messaging apocalypse when AOL sunsetted AIM. Clients like Trillian were absolutely necessary before AIM shut down. Everybuddy was a good linux-friendly client. When I still spent time on IRC, I really really liked Bitlbee [1] with ERC [2].

(I'm not saying that there's a connection there, but rather that all the chat protocols started getting used less around the same time for the same reason, which was smartphones becoming commonplace in late-00s.)

[0] https://en.wikipedia.org/wiki/Ayttm

[1] https://www.bitlbee.org/

[2] https://www.gnu.org/software/emacs/erc.html

I use purple-discord (libpurple/Pidgin plugin) + BItlBee (IRC chat gateway, libpurple variant) + Quassel (distribued IRC client, like a bouncer) on a home server, and use Quasseldroid to connect on mobile. I would eventually like to simplify this setup.

I used to have a similar setup to use IRC for everything using https://www.bitlbee.org. Fun times!

Another approach to this is to use bitlbee's twitter support and your favorite Emacs IRC client to access that. This is especially nice if you are using bitlbee anyway.

It’s written in Go and hasn’t been opened yet but it’s heavily based around this project: https://github.com/JJTech0130/pypush

neither this nor search is very much a hard problem as it’s been solved many times over already. The harder part is that beeper never reverse engineered anything, they bought the POC from a high school kid that did it as a project: https://github.com/JJTech0130/pypush meaning they never had the ability to do it in the first place

This should have been obvious to anyone who saw the code where it simply contained the raw literal string `FAIRPLAY_PRIVATE_KEY = b64decode(“…”)`. I suppose now we’ll see how accurate the commenter’s claim “if this becomes a problem, I know how to generate new keys” is.

https://github.com/JJTech0130/pypush/blob/main/albert.py#L16

I had copied it from JJ’s official GitHub website https://github.com/JJTech0130/pypush

Beeper open-sourced their reverse engineering effort, which means that there will now be a significant ongoing community effort to maintain the solution. It would be very difficult to stop the Beeper solution from working without also breaking iMessage clients running on older versions of MacOS or iOS. Apple may be able to keep new iMessage features locked up, but it would probably only be a matter of time before the community manages to reverse engineer those features, as well.

Here's the code that Beeper bought for this: https://github.com/JJTech0130/pypush

He also has to fake being an apple device using real device identifiers. https://github.com/JJTech0130/pypush/blob/main/emulated/data.plist