Hmm so it's been more than 2 weeks now since I filed a bug about some internal crashes setting up a pub. From what I can tell, invite links are broken.

I guess I'm wondering whether there is much active collaboration around the SSB codebases these days. I notice Patchbay has not had any updates since the start of March, either.

Do we still have an active developer community helping to improve the core platform, or have most of the core contributors moved on into application-specific development?

Regardless of these questions, I'd quite like to be able to have a pub running so that I can increase my success inviting others on here 😉

@pospi

We're still here! I haven't been able to figure out the social boundaries around SSB-Server and have been unable to resolve that friction, so I've just made my own alternatives to SSB-Server that work better for me:

• SSB-Daemon
• SSB-CLI

FWIW, if you ran that command via SSB-CLI you'd see:

Error: You must provide positional arguments or --flag arguments, not both.

You set 1000 as a positional argument (no flag) and then used --host, but unfortunately they can't be mixed and matched. Try settings the use count with the --uses flag:

ssb-server invite.create --uses 1000 --external ssb.spadgos.com

More docs here: https://github.com/ssbc/ssb-invite#create-uses-note-external-modern-cberr-invite_code

Much appreciated @Christian Bundy that got me sorted!

Ended up sticking with ssb-server for now. Correction to the command issued above (host not external):

ssb-server invite.create --uses 1000 --host ssb.spadgos.com

I am, however, getting connection timeouts both when I try to hit that port in a browser and when I use it as an invite code in SSB (node reports connect ETIMEDOUT in the Patchwork terminal).

Any ideas if that is a known issue? I do believe the ports are open through the Docker firewall or I imagine I would be getting ECONNECT instead of ETIMEDOUT.

Failing that maybe I just scrap this config and go with SSB-Daemon/CLI. Any useful time-saver resources you might have on that (esp. WRT Docker) would be much appreciated!

I'm also under the assumption that all I need to do in order to leverage my pub is use its own invite code to join this account to it, and once that's done it will be syncing my content / followers and all new users joining the pub will get those too? No other configuration necessary?

Just wanted to check those assumptions here while I've got your attention 😉

@pospi I'm bot actively developing Patchbay at the moment. I'm saving energy for a new client, and getting some things in order which are more important - like private groups.

also, have a 6 week old baby!

Oh, looping back...

For anyone else who hits these problems and is using CloudFlare, DNS is probably your issue.

I had to add a specific A record in their control panel for the subdomain my pub is being served from, pointing directly to my origin server with "proxy status" set to "DNS only". This prevents the subdomain from redirecting to CloudFlare's servers and not actually hitting your pub directly.

Also switched over to ssb-daemon / ssb-cli (was only a couple of lines of config changes), seems to be working well!

Final issue is syncing profile data- doesn't seem to be working but I've probably done something silly.

• Used the pub's invite code myself and I now appear to be following.
• Ran this command, which seemed to succeed fine based on the output: ssb-cli publish --type about --about "@XRK+1O0EDeGEHP3hlfhLIR5C5FGFnxmMwBThI41TRZc=.ed25519" --name ssb.spadgos.com
• No change to what I can see in patchwork, doesn't seem to be updating its profile?

Oh! Looping back- this all seemed fine and to work as expected. I was presuming things would be more immediate given I am following the pub directly but it seemed like there was actually a few minutes delay in propagation.