imessage VS OSX-KVM

The nothing website claims:

> Nothing Chats is built on Sunbird's platform and all Chats messages are end-to-end encrypted, meaning neither we nor Sunbird can access the messages you're sending and receiving.

> Nothing is powered by Sunbird, and Sunbird's architecture provides a system to deliver a message from one user to another without ever storing it at any point in its journey. Messages are not stored on Sunbird's servers and are only live on your device – once a message is delivered, it can only be recovered locally from your personal device.

From: https://us.nothing.tech/pages/nothing-chats

The Verge claims:

> Marques Brownlee has also had a preview of Nothing Chats. He confirmed with Nothing that, similar to how other iMessage-to-Android bridge services have worked before, “...it’s literally signing in on some Mac Mini in a server farm somewhere, and that Mac Mini will then do all of the routing for you to make this happen.”

From: https://www.theverge.com/2023/11/14/23960516/nothing-chats-i...

It seems to me like if they are doing the typical thing of using a bridge like https://github.com/mautrix/imessage then that isn't really E2EE, the messages are being stored, and could be accessed by Sunbird. I don't really see how their claims could be true. Does anyone know? Am I missing something?

If you're willing to dive deep into self-hosting, the open source chat protocol Matrix.org has support for an in-development iMessage bridge. Once you get it to work, there's a Matrix.org client on KaiOS devices called Chooj (sideloading guide) made by Farooq that you can use to access the chat.

iMessage bridge

The disadvantage of not offering an API for iMessage is that there is no easy way to block clients. Apps like Bluebubbles have to work by being installed on an actual Mac and scraping messages from iMessage and Beeper uses a similar architecture[0]. Presumably they have a data centre full of actual macs (or VMs).

[0] https://github.com/mautrix/imessage

I have an old Mac Mini rotting on a shelf in my cupboard which is my bridge to the world of Apple shit. It primarily runs two bits of software: OpenHaystack, which I used to run my own object trackers over the Apple Find My network and Mautrix iMessage which I used to access iMessage via Matrix on my Android and Windows devices.

I've switched from iPhone to a de-googled Android device, and am generally trying to extract myself from google and apple ecosystem lock-in. The last piece for me is trying to find a reasonable bridge for iMessages - but the baseline requirement is to have a Mac PC running 24x7 to act as a bridge for matrix or airmessage. Here's my question: the hardware and software requirements for iMessages are pretty minimal. MacOS Big Sur implemented a few messaging bits like inline replies which I'd like to keep, so that's my OS baseline. Has anyone managed to strip down a hackintosh hardware installation to absolutely minimal proxmox hardware demands (e.g. ram/cores)? If so, got a recommendation on an efficient build process?

I know how crazy it is in America, but I think at leat the HN crowd wouldn't be participating in that madness.

If you are disparate enough, you can use a matrix bridge to get blue bubbles from anywhere

https://github.com/mautrix/imessage

Yes, tulir works for beeper. But I think they stopped doing that iPhone thing, and if you use iOS there are less features available: https://github.com/mautrix/imessage/blob/master/ROADMAP.md

I have an Android phone and if you're desperate you can buy an old Mac Mini and set up an iMessage bridge over Matrix (https://github.com/mautrix/imessage) or BlueBubbles to work around this. I do not recommend it though as it locks you into a facet of the Apple ecosystem.

Yes, I recently had to compile some stuff on Windows (I'm on an AMD Linux host) and VirtualBox just wouldn't start Microsoft's Windows dev VM (the one they provide for free for Virtualbox). I ended up learning how to use qemu and it works great...and as a bonus I was able to run a hackintosh (via https://github.com/kholia/OSX-KVM) and it works near flawlessly, which was something I was never able to accomplish with Virtualbox (granted I haven't tried in a few years).

I'm pretty happy with Qemu now, even if it's jsut a CLI interface. I was tempted to try the virt-* stuff, but honestly it seems like one more thing to learn so I'm going to hold off until I need something like copy/paste between VMs and can't figure it out in qemu direct.

Working on a patch to include it as a flake input instead of vendoring it in the repo, so this should no longer be true. I use the QCOW2s for OpenCore from osx-kvm that I have not figured out how to reproduce yet https://github.com/kholia/OSX-KVM/blob/master/OpenCore/OpenCore.qcow2

For almost a year, I have been coding a little project in Python intended to piggyback on the framework of kholia's OSX-KVM project, known as ultimate-macOS-KVM, or ULTMOS.

I just researched a bit, mac os x guest vm with pcie passthrough seems possible on linux.

Dropping the links below:

https://github.com/kholia/OSX-KVM

https://github.com/yoonsikp/macOS-KVM-PCI-Passthrough

VirGL is definitely an interesting project, but all one has to do to get GPU passthrough working (from a Linux QEMU host to any guest OS) is: 1.) research a cheap, secondary GPU that is natively supported by the guest OS, 2.) plug such a secondary GPU into a PCIe slot on the host and hook it up to the primary monitor with a secondary cable (D-Sub vs. DVI, etc.), 3.) setup Linux to ignore the secondary GPU at boot and configure a QEMU VM for the GPU passthrough. The whole process takes perhaps one or two hours and as works flawlessly, with no stability issues. (Switching across the two GPU cables can be accomplished in software by using Display Data Channel /DDC/ utilities and switching keyboard/mouse can be accomplished by using evdev /event device/ passthrough.) More information: https://github.com/kholia/OSX-KVM/blob/master/notes.md#gpu-p...

I get "verification failed" error when using https://github.com/kholia/OSX-KVM

I also see there is KVM-OSX which looks to be actively maintained, but I haven't heard anything about it.

You can use qemu/libvirt/kvm on any Linux host to run macOS pretty easily these days[1]. I run Ventura on unraid with nvidea gpu passthrough and it’s been fairly painless.

You can also run macOS in docker, but it’s ultimately running through qemu/kvm as well[2]

1. https://github.com/kholia/OSX-KVM

2. https://github.com/sickcodes/Docker-OSX

I think this could be of some use to you https://github.com/kholia/OSX-KVM

i cloned that repository