[–] atombender 18 hours ago
I found the topic fascinating, but eventually I started skimming and then gave up on it.
[–] yubblegum 10 hours ago
So my questions regarding security implications of running your code, my LLM friend reviewed the code and expressed possible concerns over (a) malicious browser extensions now get to see what they couldn't before; (b) you are not using https. There was bunch more but they can all be addressed on my end. Your thoughts?
[–] infwhispers 10 hours ago
[–] yubblegum 9 hours ago
That is certainly true, and it is equally true that that possibility places a responsibility on you to put that in a section in your readme.
So yeah, I may have a bad extension but that thing never had access to the possibly aptly named 'IntelligencePlatform' that's keeping tabs on my digital activities, until I ran your code. Correct?
[–] thomascountz 8 hours ago
[–] yubblegum 8 hours ago
My evil extension|browser may know what porn I watch or which sites I am visiting or possibly lift some bits it is not supposed to have. But it does not have access to Apple's comprehensive graph of my digital activities on their devices. Only Apple Inc. has that access.
So in fact the OP needs to put in the readme that "malicious browser extensions are a potential attack surface."
As a matter of fact, one could argue that a posting like this on Hackernews could potentially be a very sophisticated 'human engineering' effort by parties that have backdoors to browsers but have been defeated by Apple's security features.
[–] eks391 7 hours ago
This is akin to some medicine saying that if paired with another specific medicine, you won't get desired results, and you are upset that it doesn't include a warning against combining the medicine with cyanide because you might die. The pairing with cyanide is irrelevant to the medicine and is just a side effect of cyanide.
[–] thomascountz 7 hours ago
Also, small correction: any app with Full Disk Access can access this data.
[–] jdiff 16 hours ago
A lot of these statistics aren't very useful for mining insights from the graph, from a technical standpoint of how the graph works or from a personal standpoint of how the graph is interacting with my personal data.
[–] abandonliberty 8 hours ago
It's a shame because I really appreciate your work here. Could be resolved as trivially as providing a copy of your writing style and having it adapt to that.
[–] jamienk 13 hours ago
[–] jamienk 13 hours ago
The data I see from iKnow is a sloppy clusterfuck, I suspect from botched syncs and lazy bookkeeping on my part, and the fluctuating quality of Apple's "services" over the years. My Mac settings probably go back to the 1990s and Apple periodically did a bad job. Pain points I remember: Google contacts being separated and then with a new phone not syncing correctly, Mac address book burping on contact avatar images, importing lists of contacts from short-lived 3rd party apps, shared Photos fucking shit up, the iPhotos upgrade fiascos, transient contact info for my kids, moving onto/off of Gmail, etc.
If the FBI got ahold of my (and others'?) iKnow data, a lot of people might end up in a sloppy jail with a sloppy judge sloppily applying a sloppy law...
[–] mmooss 14 hours ago
(I hate that a discussion on the OP has been hijacked by a discussion on AI writing; the substantive questions are all at the bottom. I wish mods would 'detatch and move' the AI subthread.)
[–] asdfsa32 18 hours ago
[–] tkgally 18 hours ago
One example: "323 people, 122 events and other records, 200 employers and 1 stored group — as the store on this Mac links them. Read live just now. Colour is what each node is to you: the stored group in red, family and closeness by iKnow’s rules on the kinship scorecard. Size is how many rows in the store name it."
Claude etc. can be prompted to produce clearer explanations than that.
[–] wpm 7 hours ago
> Every node as a list — the graph is not the only way in
> Family, as the scorecard has it
> Reachable, exactly as stored
Oh good I was worried it was going to show me something altered
> WHY RESOLVABLE MATTERS
Oh fuck off. This isn't Axios! I hate these pathetic brainrot stupid phrases Why it matters What Happened What Changed, how patronizing. Instaclosed, instakilled python, what a fucking waste of my time and a waste of an article too
[–] coldpie 17 hours ago
[–] SoftTalker 11 hours ago
[–] coldpie 11 hours ago
That's actually exactly what does it for me. After the intro, it gives you way too much specific detail. No one cares about the exact file path or whether that path is TCC Full Disk Access protected. What does that even mean? Why is this important enough to be in the first sentence of the section? I don't care that there's 51 database files and 181 other things and 278 doodads. Who says stuff like "triple store?" It uses bizarre language with far too much detail, and like you said, your eyes start to glaze over because there's so much irrelevant information. No human would've chosen to write all that tedious detail in their post about something much more interesting. It's bad writing. It's slop.
A human would've said something like "It's a database in <Library/IntelligencePlatform> with three columns that contain..." and left all the rest of it out or maybe in some extreme details footnote.
[–] infwhispers 18 hours ago
[–] JoshTriplett 17 hours ago
Suggestion for next time: "Review my prose for accuracy, grammar, appropriate strength of claims, etc. Flag any issues for my attention. Do not provide text; this work should not contain any AI-written content." That'll turn it into a very good check that doesn't take your voice away.
[–] embedding-shape 18 hours ago
A defense would be "I just used it for spellchecking" not "I just used it for the meat and the important parts people care about, the rest is mine!"
[–] NewsaHackO 15 hours ago
[–] Hamuko 18 hours ago
[–] fatata123 17 hours ago
[–] sick_of_slop 17 hours ago
“Sure there was a turd in the punch bowl but I did my best to remove it, so you should be able to drink it.”
Nope.
And the technical parts are what matter, saying you did that with A.I. tells me “I don’t care about this part” so what the heck are we even doing here?
[–] rowanG077 15 hours ago
[–] amenhotep 14 hours ago
[–] InsideOutSanta 13 hours ago
LLMs fail at those things.
[–] asdff 14 hours ago
[–] burnte 9 hours ago
[–] n0on3 18 hours ago
Anyway, it’s a shame, this could have been excellent work. Instead, I find reading it unpleasant and part of my attention rots away wondering if you even checked what the LLM wrote for you. You probably did, and I could also do it myself, but still…
[–] ecto 15 hours ago
[–] ahartmetz 14 hours ago
[–] otterley 15 hours ago
[–] ProllyInfamous 15 hours ago
----
The research is jaw-dropping enough for the average reader to comprehend (e.g: I am not a techie, but a former IBEW datacenter wiretwister).
It could be covered in pube-sprinkled-turds and would still be worth reading.
To me the "slopLOL" crew is akin to people who'll take their time to correct others' their/they're/there usage:
Just read the fucking sentence (LLMs can and do and aren't so poopy-you-suck-for-being-human).
[–] otterley 14 hours ago
How news is delivered matters. If you don’t believe that, why would news outlets compete with each other? Even if the facts are the same, would you prefer to get them from a good or bad writer?
[–] ProllyInfamous 14 hours ago
I am smart enough to not need perfection. I just want the data. Write however tf you want, good'll'be read.
And so will LLMs.
I'll suggest adaptation.
>why would news outlets compete with each other?
Competition for the masses' con$umption$?
It seems to generally work; shouldn't have to obfuscate the `man` pages for this always-running daemon... how many people even know what `man`pages are (obviously not here)? how to access them? why they would even want to?
[–] pjscott 7 hours ago
This is completely tangential to your point, but I'd bet that this daemon isn't always running. Apple is fond of putting as much system functionality as possible into daemons that (a) can be spun up quickly when needed in response to Mach IPC messages, (b) can be killed safely at any time to free up memory, including with SIGKILL if necessary, and most importantly (c) operate in the tightest, most locked-down sandbox they could devise.
For background computational tasks like this one, it can also be helpful for getting thread prioritization right. If some computation doesn't need to happen quickly, a daemon can easily make sure that it gets assigned to efficiency-optimized CPU cores, tell the OS scheduler to give priority to more important stuff, reduce precision of timers to coalesce wakeups, and make sure that any thermal throttling affects the background stuff before it slows down anything the user will notice. It's a pretty slick system.
[–] otterley 14 hours ago
> I am smart enough
Knock yourself down a peg, kid.