You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i am running go-ssb as pub server, i think it worked fine with patchwork, but now i migrated to manyverse, and i have this strange issue:
manyverse shows 'Not connected' in connections "tab", but when open connections panel and click on the name of pub server, it opens a menu which suggests to disconnect from it.
i can also open profile and if i open i just see the ssb id of the server, which starts with @ sign and 'Loading...' on the bottom of the window infinitely...
the pub server had a message which it wrote months ago, but it doesn't seem to be shown in manyverse, when i open the profile of pub server.
when i am trying to 'disconnect and forget' the pub server - it doesn't seem to work as well.
i have this suspicion that if i add it by IP manyverse will maybe able to connect? or is it connected?
because when i run manyverse i have these in console:
[5582:1123/190610.649964:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[5582:1123/190610.650053:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
i don't know which bus is it. dbus has been started, if manyverse uses it, it doesn't help.
and then i have this
[5643:1123/190610.765792:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
Unknown type { type: 'DEFERRED', task: [Function (anonymous)] }
(node:5582) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(Use `manyverse --trace-deprecation ...` to show where the warning was created)
peer @id_of_my_pub_server=.ed25519 does not support RPC ebt.replicate
i tried with standard go-ssb and also with planetary's fork of it, which, i read could maybe fixed that.
also i don't understand why the pub server sometimes is visible with green dot near its 'avatar' and sometimes with yellow dot.
oh right now i noticed that it has a green dot, and 'not_connected' became 'too few connections'.
maybe this happened because i changed the go-ssb to planetary's version.
The text was updated successfully, but these errors were encountered:
i am running go-ssb as pub server, i think it worked fine with patchwork, but now i migrated to manyverse, and i have this strange issue:
manyverse shows 'Not connected' in connections "tab", but when open connections panel and click on the name of pub server, it opens a menu which suggests to disconnect from it.
i can also open profile and if i open i just see the ssb id of the server, which starts with @ sign and 'Loading...' on the bottom of the window infinitely...
the pub server had a message which it wrote months ago, but it doesn't seem to be shown in manyverse, when i open the profile of pub server.
when i am trying to 'disconnect and forget' the pub server - it doesn't seem to work as well.
i have this suspicion that if i add it by IP manyverse will maybe able to connect? or is it connected?
because when i run manyverse i have these in console:
i don't know which bus is it. dbus has been started, if manyverse uses it, it doesn't help.
and then i have this
i tried with standard go-ssb and also with planetary's fork of it, which, i read could maybe fixed that.
also i don't understand why the pub server sometimes is visible with green dot near its 'avatar' and sometimes with yellow dot.
oh right now i noticed that it has a green dot, and 'not_connected' became 'too few connections'.
maybe this happened because i changed the go-ssb to planetary's version.
The text was updated successfully, but these errors were encountered: