101–110 of 276 posts
After years of herding imessages i went ahead and deleted everything older than a year. i encourage othes to consider doing the same. its been great for me.
On your Mac, iMessages are stored in a SQLite database which you can inspect. https://spin.atomicobject.com/2020/05/22/search-imessage-sql...
And, yeah, it’s a total mess.
Apple's chat.db has an esoteric schema owing to the fact they never designed it from the ground up and instead kept adding new columns and tables with each macOS release. This makes their queries super complicated with multiple joins. Once you have the schema figured out, it's dead easy to build a third-party client that works better than the official one. Even search works great with a simple LIKE query but Apple re…
You also mention on your website that end-to-end only works when the platform "supports" it — does that include Windows with your currently always-on Mac solution?
I save them on the expectation that Apple will someday release a better tool for browsing them. Especially the texts between me and my wife, they are a story of our life from the very first one.
FWIW, it is fairly easy to dump them out of your iTunes backup.
arguably the worst part about imessage and scrolling is that even if you do manage to scroll up and find a previous message, you are automatically scrolled down to the bottom if a new message is received in that chat (on iphone)
Earlier quoted context omitted.
Yes, with a catch: it requires an always on Mac (which can be in the cloud) or a jailbroken iOS device. We plan to make it work without the catch. I've worked with 10+ messaging platforms so far and Apple's protocol is the most obfuscated and complicated to reverse engineer. Apple has invested millions of dollars to make the iMessage protocol super hard to reverse engineer. It's how they sell tons of iPhones after al…
> it requires an always on Mac (which can be in the cloud) That’s surprising. How come?
Earlier quoted context omitted.
Pulled it up on my phone just to see what they considered "large", looks like 4MB is the cutoff (nothing smaller than that shows up for me). But nearly everything I'm seeing is a video or a photo taken with my real (not phone) camera. And a random PDF I apparently sent over iMessages. However, deleting through this interface would be a pain. You select "Edit" and then each attachment is selected individually.
It seems to just show you the largest set (50? 100?). If you delete them, then you will eventually show smaller ones once you get through enough of them. Really wish there was a "delete all" or "select all".
Apple's chat.db has an esoteric schema owing to the fact they never designed it from the ground up and instead kept adding new columns and tables with each macOS release. This makes their queries super complicated with multiple joins. Once you have the schema figured out, it's dead easy to build a third-party client that works better than the official one. Even search works great with a simple LIKE query but Apple re…
https://github.com/CamHenlin/iMessageWebClient
I also have some other iMessage related git repos on my GitHub. Interesting stuff!
Earlier quoted context omitted.
Have you tried emailing Craig Federighi about this? I emailed him a bunch of times about several things and he's a really nice and responsive person. If you do, tell us about it here on HN.
I actually did try emailing Tim Cook a few months ago, but I got bounce backs. I tried tim@apple.com and timcook@apple.com but the mailer daemons said the addresses weren't registered. It sounds like a crazy thing to do, but I remembered how Steve Jobs would reply to users' emails and read an article where Tim said he set aside time to read users' emails.[0] [0] - https://www.inc.com/business-insider/tim-cook-wakes-u…
Also, be sure to file a bug report / enhancement at https://www.apple.com/feedback/iphone.html
Apple's chat.db has an esoteric schema owing to the fact they never designed it from the ground up and instead kept adding new columns and tables with each macOS release. This makes their queries super complicated with multiple joins. Once you have the schema figured out, it's dead easy to build a third-party client that works better than the official one. Even search works great with a simple LIKE query but Apple re…
Very eager to see how your app works when it opens up to the public. Are there ways to provide assurances for your end-to-end encryption which may be digested by experts? You also mention on your website that end-to-end only works when the platform "supports" it — does that include Windows with your currently always-on Mac solution?
We recommend using a simple MITM proxy or a firewall app like Little Snitch / LuLu to inspect the network traffic.
> You also mention on your website that end-to-end only works when the platform "supports" it — does that include Windows with your currently always-on Mac solution?
Yes – there's a peer-to-peer connection between the Windows and Mac devices.