Refuses to bootstrap off Manyverse via LAN #95

New Issue

interfect · 2025-01-01T15:42:41-05:00

interfect commented

2025-01-01 15:42:41 -05:00

I set up TF 0.0.26, and ran Manyverse on the same machine and also on a phone on the network. Both Manyverse instances had data, but the TF instance had a fresh database.

In TF I could see and connect to the Manyverse clients. I followed the local Manyverse client's key in TF and the TF identity's key in Manyverse. I made room invites to a couple rooms from manyverse and TF joined them and could see the keys of the room peers.

But TF could not actually exchange feed data with Manyverse! I let it sit for an hour or so with no change; TF didn't get anything added to its database besides what was created on the TF instance.

Then I went into the TF settings and fiddled around, turning on peer exchange, turning off account registration, and setting a non-default room name and hostname for TF's built-in room, and then I started getting replication into TF from somewhere. I note that under my local-machine Manyverse instance in the TF connections screen I now see:

🟥 room.attendants 🟥 blobs.createWants 🟥 gossip.ping 🟥 ebt.replicate 🟩 blobs.createWants 🟩 blobs.get 108

Did I need to turn on peer exchange to get the local machine Manyverse peer to be able to talk to me? Why did it sit for hours not doing anything? What fixed it? The mystery continues...

I set up TF 0.0.26, and ran Manyverse on the same machine and also on a phone on the network. Both Manyverse instances had data, but the TF instance had a fresh database. In TF I could see and connect to the Manyverse clients. I followed the local Manyverse client's key in TF and the TF identity's key in Manyverse. I made room invites to a couple rooms from manyverse and TF joined them and could see the keys of the room peers. But TF could not actually exchange feed data with Manyverse! I let it sit for an hour or so with no change; TF didn't get anything added to its database besides what was created on the TF instance. Then I went into the TF settings and fiddled around, turning on peer exchange, turning off account registration, and setting a non-default room name and hostname for TF's built-in room, and then I started getting replication into TF from *somewhere*. I note that under my local-machine Manyverse instance in the TF connections screen I now see: ``` 🟥 room.attendants 🟥 blobs.createWants 🟥 gossip.ping 🟥 ebt.replicate 🟩 blobs.createWants 🟩 blobs.get 108 ``` Did I need to turn on peer exchange to get the *local machine* Manyverse peer to be able to talk to me? Why did it sit for hours not doing anything? What fixed it? The mystery continues...

cory commented

2025-01-03 21:08:41 -05:00

Just throwing this out there: the first obstacle I ran into was that I was able to connect Tilde Friends to Manyverse, but it would immediately disconnect. Digging through the Activities tab in Manyverse, I eventually found this:

I followed, and replication started flowing.

There might be other things if Manyverse connects to Tilde Friends first, but I need to juggle some things to be able to test that.

Just throwing this out there: the first obstacle I ran into was that I was able to connect Tilde Friends to Manyverse, but it would immediately disconnect. Digging through the Activities tab in Manyverse, I eventually found this: ![image](/attachments/8dad37a2-54fa-4b2d-94d1-22f25caebbd3) I followed, and replication started flowing. There might be other things if Manyverse connects to Tilde Friends first, but I need to juggle some things to be able to test that.

image.png

22 KiB

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cory/tildefriends#95