I go sick of messages to Habitat's database thread taking too long to reach the front of the queue so I made a second table in the database for SSB messages to go as they arrive: they go there first now and get transferred to the original table with all the indexed columns one by one - the fewer other things that thread is doing the more frequently.

#dev-diary

Spotted in my SSB blobs folder

My family are going to be in the (Wellington) city centre for the next 4 Saturday afternoons. Maybe a crab meet could be arranged!

Got room tunnel connections working! Next p: have it requst connections via rooms rather than just wait for others to connect to us.

#dev-diary

I seem to have fixed the validation errors. Note to self: just because some official looking documentation for JSON.stringify says \t means vertical tab does not mean that's actually the case!

#dev-diary

Today I merged and deleted the internet git branch into main which means these things have happened already this week:

• I got the list of peers in the "Network settings" GUI window to stay in sync with the one in the internal application object.
• I got the application object to persist the list of peers to disk and read it again when starting up.
• I got Habitat to automatically connect to peers on the list.
• I got it to detect when a connection has failed and reconnect.

Now I no longer have to use the Haiku IPC mechanism to get Habitat connecting to peers outside my LAN!. Tomorrow I'll be back into multiple active branches mode: on one branch I'll be adding timestamps to the list of criteria the Habitat can use in database queries, and in another branch I'll be adding support for room server tunnels.

#dev-diary

The past few days while manually prompting Manyverse on my phone to connect to Habitat I've been consistently noticing room participants who are outside my replication range. I'm taking it as a sign that the Scuttlebutt mainnet has not dwindled to the extent I had feared!