You are reading content from Scuttlebutt
@runKleisli
Voted ## What happens if I duplicate my ~/.ssb on another device? Basic question
@runKleisli
Voted [@corlock](@sHFNLAao6phQ5AN17ecYNUbszDa4Qf6DhyQsjtQfdmY=.ed25519) My unders
@cel
Voted Okay, so I was able to publish this fix as scuttlebot@11.3.4 ``` npm info
@Hugo
Subscribed to channel #scuttlebot
@Schizo
Subscribed to channel #scuttlebot
@kravietz
Voted [@mixmix](@ye+QM09iPcDJD6YvQYjoQc7sLF/IFhmNbEqgdzQo3lQ=.ed25519), [@matt](@
@mix
Re: %PPE5iDelJ

wouldn't be surprised if you're having a bumpy time @SoapDog , there have been quite a few changes. Personally I'm going to be working on getting patchbay stable and installers working on ssb-server@13 first I think. Then I'm going to try upgrading to 14

I've seeb problems with the CLI too on 13, like sbot whoami tells me there's so server running when there for sure is. This is annoying but I just don't have time to fuck around with the CLI at the moment (I already spent a bunch of time getting ssb-config playing friendly with bin.js ... what a mess)

@DavidW
Re: %PPE5iDelJ

I ran into that a few times @SoapDog , and it looks like it was just the heavy duty initial sync in my case. In each case I left for a while and when I came back my cpu load was back to normal and I could talk to sbot again. Hopefully its worked itself out by now

@CrypticWyrm
Re: %PPE5iDelJ

@SoapDog I had the same issue a couple of days ago until I reinstalled ssb-server with npm i -g ssb-server@latest which some SSB projects on Github mention in their readme as the way to install it (I found at least half a dozen ways to install it in the documentation, tutorials and readme's on Github that all resulted in a server that I could start but not connect to), then I could suddenly connect just fine to the server. Not sure what the @latest does, I don't use npm often, so maybe that wasn't the issue and it was just coincidence that it worked after adding that, but I'm pretty sure I didn't do anything else, I didn't have to edit any config file.

@Giarc
Re: %PPE5iDelJ

Try placing "host": "localhost" in your config for net connections.
With the default "host": "" ssb-server config I've had problems with ssb-server listening on my yggdrasil IPv6 in preference to my IPv4. Then ssb-server commands try to connect to localhost:8008 but ssb-server isn't listening there. I'm thinking it's an OS net ordering issue, but also that perhaps ssb-server should to be told to try ::1 if localhost fails? I need to figure out how to change my default net to be my IPv4 link but for now I have the following in my config for IPv4 and IPv6

"net": [
        {
          "host": "localhost",
          "port": 8008,
          "scope": "public",
          "transform": "shs"
        },
        {
          "host": "::1",
          "port": 8008,
          "scope": "public",
          "transform": "shs"
        }
      ]

Show whole feed
Join Scuttlebutt now