3 ms·
I got the impression from the code that this operates directly on whatever sqlite db iMessage actually uses. Is this right? If so, it's probably worth consideri
by pvg 6y ago
I got the impression from the code that this operates directly on whatever sqlite db iMessage actually uses. Is this right? If so, it's probably worth considering just making a copy, or including a script that makes the copy, when sudo'd. That way you don't need the permanent permission and there's no chance of accidentally messing up an important bit of user data. And paranoid people will probably feel better about not having a live local webserver that's poking around their personal messages.
- lxor677 6y agoTotally fair. I'll look into that for a v2. Since the operations are RO, I don't think there's much risk of messing up the data, but I think it makes sense from a context standpoint. The application certainly doesn't need permanent access. Although tbh, one of the reasons I had it was because I tried to orient the setup towards a non-technical audience, so I wanted a 'clickable' solution, like giving full disk access.
- 67868018 6y agoSQLite has write locking, it's not going to happen. And you're only reading anyway...