We're hardly the first people to complain about this, but it drives me nuts. I rarely delete messages (for better or worse), so I have an ever-growing iMessage database that is basically inaccessible to me. I don't know why I pay to back up 20 gigs of messages that I can't even access, but here we are. For instance, I wanted to figure out the exact date I met my partner. The only way to do this on iMessage is to scroll up...all the way up. With a few seconds of god-knows-what in between every page. The endeavor is usually futile, though; because when you get a ways back, the iMessage app will crash.
The worst part: if the person sends you a text while you're scrolled up it will jump all the way to present time.
Btw, if you double click to open a new window, that window won't have the new message jump
Re:Analyzing iMessage with SQL
by voltaireodactyl on Wednesday April 20, 2022 @05:01PM
(#31102949)
I recently figured out that iMazing allows you to export PDFs (among other formats) of all your text convos. It’s pretty perfect for my needs, which were precisely the same scenario (plus printing out a nice history)
Re:Analyzing iMessage with SQL
by foxbarrington on Wednesday April 20, 2022 @01:05PM
(#31099933)
I've always wondered about this, but it's not limited to Messages on macOS. WhatsApp is painful when you want to do the same thing. I don't know about other messaging apps, but I'm not sure why there isn't UI/UX where you can easily/quickly scrub through months/years.
But at least in WhatsApp I can scroll as fast as I want while the App never is stuck.
With iMessage it loads for seconds every 20 messages or so. I also really don't get it.
I've been tempted to cobble together a simple GUI that lets you search text, images, sender etc etc. But it would only be desktop since I doubt it would make it through approval for iOS.
Re:Analyzing iMessage with SQL
by upbeat_general on Wednesday April 20, 2022 @01:06PM
(#31099943)
To be fair it’s been this bad as far as I can remember with iMessage.
Incredibly frustrating and slow, but not new.
For me, when I scroll up to load historical data, it takes always multiple _seconds_. This is on the newest, highest specced m1 macbook. What the hell is it doing in that time? Multiple seconds to do read-only queries a <100MB sqlite DB (and sqlite can be incredibly fast), on an SSD with >5GB/s read speeds, with 64GB of ram (where the whole sqlite can/should be loaded into memory), to render a blue bubble with some text inside.
What is Messages doing, and why is it so bad and inefficient. I'm certain the local sqlite db has the data I need because the above bothered me so much i wrote some scripts to read my historical chats from the cli. Quality of Apple software is certainly not increasing but going downhill, you see that across many of their apps.