mirror of
https://github.com/airmessage/airmessage-server.git
synced 2026-04-25 16:55:50 +03:00
[GH-ISSUE #43] AirMessage dead? #40
Labels
No labels
bug
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/airmessage-server#40
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kerta1n on GitHub (Nov 11, 2023).
Original GitHub issue: https://github.com/airmessage/airmessage-server/issues/43
Has anyone talked to Cole about the future of this project or is this too exhausting for the devs?
(Wondering about FaceTime in specific as BlueBubbles added integration to DETECT calls, but it seems AM has actually been able to MAKE a call)
@mkitchingh commented on GitHub (Nov 11, 2023):
I tried to get a response from him on Reddit a few times, but he seems to have gone offline. I moved to Blue bubbles, because I assume the Google cloud portion of this will cease to function at some point.
@kerta1n commented on GitHub (Nov 11, 2023):
Oh ok. I do know he has an X (Twitter whatever) and has been active on that, maybe someone can DM him there?
@tagavari commented on GitHub (Nov 11, 2023):
@kerta1n Thank you for asking. I'll explain why it's been difficult for me to work on AirMessage, and where AirMessage could go from here. It mostly boils down to these two reasons:
That being said, I personally really enjoy working on AirMessage, and I like the community that's formed around it and BlueBubbles. I would love to see a world where AirMessage can continue to exist.
Here's the world where AirMessage continues. I need help: to maintain apps, fix bugs, and bring in new features, as well as non-technical help, like documenting parts of macOS, or donations for server costs.
Without this, mkitchingh is correct in that I'll have to shut down the servers.
I haven't been very communicative about anything on AirMessage recently, and I apologize for that. Managing a project is not my strong suit.
I hope that explaining my situation and what AirMessage needs to move forward will kick-start the process. If you or anyone else would like to help or know people who would, please reach out :) My active communication channels are here on GitHub, on X / Twitter, or hello@airmessage.org.
@kerta1n commented on GitHub (Nov 11, 2023):
@tagavari on behalf of all of AM's end users, thank YOU. I completely understand why you've been slowing down, I know that the owner of Omegle had a situation similar to yours as well. I am not that well of a developer, but I definitely plan on using and supporting AirMessage for the coming future.
Edit: I think that maybe a collab or partial merge between BlueBubbles would save AM based on what you've said, or focusing on FaceTime more would definitely make AM more appealing for more people. But like I said, I'm just another end user, so I have no idea how much effort is put into developing those types of solutions, but I will stand by whatever AM's plans are for the future.
@aia832003 commented on GitHub (Jan 7, 2024):
Another end user here, and thanks for all the dev time on this service. I'd love to support a Patreon or alternative subscription model. I like BB and AM, but find AirMessage has a much better design and onboarding. As a former Beeper user, I'd love to see this app and server continue, since Apple seems determined to sabotage that team now. I think that leaves a world where AM is valuable.
@cloopadoop commented on GitHub (Dec 10, 2025):
I'd pay for it too--every alternative I've tried doesn't compare.