Apple

17497 readers

93 users here now

Welcome

to the largest Apple community on Lemmy. This is the place where we talk about everything Apple, from iOS to the exciting upcoming Apple Vision Pro. Feel free to join the discussion!

Rules:

No NSFW Content
No Hate Speech or Personal Attacks
No Ads / Spamming
Self promotion is only allowed in the pinned monthly thread

Lemmy Code of Conduct

Communities of Interest:

Apple Hardware
Apple TV
Apple Watch
iPad
iPhone
Mac
Vintage Apple

Apple Software
iOS
iPadOS
macOS
tvOS
watchOS
Shortcuts
Xcode

Community banner courtesy of u/Antsomnia.

founded 1 year ago

MODERATORS

[email protected]

Beeper's next iMessage for Android fix requires access to a Mac (9to5google.com)

submitted 11 months ago by [email protected] to c/[email protected]

37 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 11 months ago* (last edited 11 months ago) (1 children)

If they weren’t charging for it I might feel differently.

I don't think they ever charged anybody, they suspended that idea after the first outage.

Also, they were using their own fleet of Macs, hence why Apple was able to isolate them easily if they're all centrally located.

[–] [email protected] 8 points 11 months ago* (last edited 11 months ago)

My understanding of it (and I could be wrong I’m not that invested in this) is that the first iteration used their Mac fleet, while the second iteration was spoofing IDs. This would be the third iteration.

It was a few days ago I read this, I’d have to look up the source again

I have no problem with this third iteration. There’s plenty of Mac users with android phones. If you’re using your own machine ID, have at ‘er.