@andrestaltz📱 that is OK, I thought Manyverse had the tcp server open. No worries, so, what would be the best way for me to detect if the current
.ssb folder is a migrated identity? As I understand, if Manyverse creates its own identity, it does it on a sandbox folder, but if you migrate an identity it keeps using the
.ssb folder. Is that so? How can I make sure I detect that it is a Manyverse-controlled identity so that I can avoid it and start a Patchfox-owned elsewhere?
I have a quick question for you fine folks. My plan for Patchfox Desktop default behaviour is to attempt to detect and connect to locally running servers before giving up and starting my own. That means that if:
- It find a
.ssbfolder, it reads the
secretand attempts to connect to the local server if it is up.
- If the server is not up, it stats its own server using that secret (unless configured differently in Patchfox settings).
I would also like to detect a Manyverse Desktop installation and read its secret and connect to its server. I won't try to start a server using a Manyverse secret/feed because I'm not using db2 on the Patchfox server, but I'd be happy to connect an SSB client to the Manyverse server when it is running.
Patchfox supports multiple identities so the user can have a window with a legacy identity and another window that is actually connected to Manyverse (in theory, but it works with Patchwork for example).
I'm aware that there are different indexes and different mux calls, but a lightweight client should work, right?
If not, maybe at least I can make sure I don't clobber or cause harm to a Manyverse installation if you tell me what to look for and what to avoid touching.
Show whole feed