Live data from Hacker News

It's virtually impossible to read old iMessages and they take up tons of storage

keydiscussions.com

201–210 of 276 posts

Re: It's virtually impossible to read old iMessages and they take up tons of storage

#202

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…

why the need to sign up with Google? I don't want Google to be associated with text messages.

Maybe they just added it, but there's also a "Prefer entering email instead?" link below, which I appreciated

Re: It's virtually impossible to read old iMessages and they take up tons of storage

#203

Earlier quoted context omitted.

That's an undocumented implementation detail. It might change without warning at any time. Are you seriously recommending this as a solution for users who want to be able to read past messages?

Your indignation is strange. Why would you not recommend it when there's no alternative?

[deleted]

Re: It's virtually impossible to read old iMessages and they take up tons of storage

#204

Earlier quoted context omitted.

Personally as a college student, all my friends use iPhones still. I have always wanted to switch to andriod, but one of the things that really holds me back is the fact iMessage still feels leagues above how SMS and texting works on andriod. Many subtle features of Imessage really make a difference with the overall texting experience on the iPhone over the long term. Most of my friends do not have whatsapp, and we a…

And I think the biggest of those subtle features is the blue coloured bubble, isn’t it?

For me it's the fact that you can generally see the other person typing in an iMessage, while you can't in normal SMS.

That tells me whether the person is replying right now, so it's worth keeping my phone out, or busy and therefore won't be getting back to me for a while.

The time savings add up.

Re: It's virtually impossible to read old iMessages and they take up tons of storage

#205
post #196

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…

> "Apple's chat.db has an esoteric schema" This is basically one taken out of microsoft's .doc format playbook. At first I thought Apple was slow and just didn't have time to get to some sort of export for iMessage chats. Mail had imap, calendar had caldav, address book had carddav. The original mac stuff did other standards like AIM and jabber. But over time I began to suspect, then later those internal emails expos…

You said it! Apple has been unethical from the get go and yet somehow the cult doesn’t care. I’m unhappy apple user but still on 6S and will be switching over to Android phones until pine phone (Linux OS) becomes better.

Re: It's virtually impossible to read old iMessages and they take up tons of storage

#207

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…

Looking over your site, I'm curious about a few things:

- The FAQ says you'll eventually open source your SDK. I admire that as a software engineer, but from a business perspective, isn't this risky? It seems like--if you don't pass messages through an intermediary service--your value-add is mostly in this SDK + your design. All of these elements are copy-able. - The jobs page includes a backend engineer, so what will go through your backend, if not any message data?

- Are there legal concerns about reverse-engineering these APIs and using them? Some of your supported chat services have open APIs, but others seem intentionally closed. (And a couple parent companies seem downright hostile to 3rd party use.)

Re: It's virtually impossible to read old iMessages and they take up tons of storage

#208

Earlier quoted context omitted.

"steve" was a collision from the start.

I could imagine Steve Wozniak offering to use surnames only as a joke - because that wouldn't work either.

It would probably work better for the two Steves than it would for many others. According to the below random site, there 218 Jobs and 10,602 Wozniaks. It claims 410,801 Steves.

http://howmanyofme.com/search/

Re: It's virtually impossible to read old iMessages and they take up tons of storage

#209

Earlier quoted context omitted.

Is texts.com a work around for sending live imessages on a PC?

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…

Agreed on intentional obfuscation. It even has booby traps. https://neosmart.net/blog/2018/imessage-for-windows/
Post reply on HN