Jim Newsome @sporksmith@mastodon.social

I really need to skate switch more often

NAT Slipstreaming - technique for malicious sites to bypass your NAT and connect directly to internal services.

TLDR: you probably want to disable SIP ALG passthrough on your home router. https://news.ycombinator.com/item?id=24955891

Finally got around to finishing Celeste. Well, "finishing". Now to hunt down strawberries and hearts, play the b-sides, etc...

Pixel 3a running LineageOS is pretty smooth so far.

Biggest issue that led to pulling the trigger on another phone order: incoming text messages seem to be getting lost. Haven't investigated deeply yet, but I've only tried receiving from my wife's iphone. Maybe it uses MMS (known not to work) even for plain messages?

Close second is the battery life indicator being inaccurate, leading to the phone shutting down unexpectedly. This is especially problematic given the poor battery life (which is a known issue due to deep sleep not being enabled)

About a week ago the crack on my old phone got worse, making my old android almost completely useless. So my pinephone has been my primary phone since then.

Unfortunately it's really not ready for that yet (as everyone involved has explicitly warned). I've ordered a refurb'd pixel3a to put lineageos on as my primary.

I don't regret the pinephone purchase at all. I plan to keep poking at developing on it, and I'm excited about its future :)

Well, I seem to have a good long compile going. Guess I can try setting up an emulator on my desktop in the meantime and see which wins.

It looks like the supported way of cross-compiling packages for postmarketos is to compile in a qemu machine on an (emulated) aarch64 processor rather than doing a true cross-compile.

Not sure whether the performance would be worse on my desktop emulating aarch64, or natively on my phone. I do know that the latter is less work to set up though, and thankfully I sprung for the extra RAM and storage, so here we go...

TIL about lsof(8). Sure enough, even with gnome-contacts closed:

```
$ lsof | grep /home/user/.local/share/evolution
3398 /usr/libexec/evolution-addressbook-factory /home/user/.local/share/evolution/addressbook/system/contacts.db
```

Examining the strace output further, it doesn't appear to try to directly open the db at all... but *does* do a bunch of IPC.

There are some persistent /user/libexec/evolution-* processes, so most likely one of these is holding some kind of lock on the database.

I think it's back to the drawing-board here. Maybe I'll take a closer look at syncevolution...

I haven't bothered to actually populate the DB yet, so not actually that big of a deal...

Aaand now I get the same error if I try to save changes from my phone.

Double-checked and the file permissions look good. Also strace'd evolution and didn't see any errors opening the files.

I suspect it's a lock inside the db file itself. Tried closing the contacts app on my phone, ensuring syncthing had syncd, and trying again, but still no luck. Hmm.