I made an easy-to-deploy Pub server. https://github.com/staltz/easy-ssb-pub

Hopefully helps with Patchwork adoption

This looks rad @andrestaltz !

Anyone out there tried this yet ?
Would love to get feedback so we can start recommending this to people.

In the meantime I've thrown a mention in the handbook under applications :
https://www.scuttlebutt.nz/
git@github.com:ssbc/ssb-handbook.git
ssb://%lJsDWwnF4bDxHWYuSjw/bW37xg+saF8WtPZYZsefKj0=.sha256 (are you on git-ssb yet?)

We tend to publish ssb related tools on git-ssb (and backups on github). Because if you're going de-cent, why not go all the way?

wow that was beautiful @andrestaltz !
thanks @don

Now to make a way to use invite in patchbay ... or find one that was already written

Sure, I'll start using git-ssb too. It's just a matter of letting go some habits :)

Also, this easy server has pretty loose rules for invites. It gives out free invites for anyone who asks, even spammers. So it's not useful forever, but it's certainly useful for the time being, when SSB is still small :)

Is this how you do it? %XE0CHVu...

@andrestaltzs yes, except the repo message is encrypted, while the push message is not. this is unusual, but i'm able to clone it anyway. what command did you use to create the repo?

i like the design of easy-ssb-pub. another idea for giving out invites in a more trust-friendly way could be to ask for an email address or other contact info before giving out the invite. maybe also ask questions like "how did you find this", "why do you want to join". then have it go into a queue to be manually approved. or just send it by email, thus confirming the address. then there is more of a connection with the new person

I did git ssb create ssb easy-ssb-pub then git push ssb master.

another idea for giving out invites in a more trust-friendly way could be to ask for an email address or other contact info before giving out the invite. maybe also ask questions like "how did you find this", "why do you want to join". then have it go into a queue to be manually approved. or just send it by email, thus confirming the address. then there is more of a connection with the new person

Agree. However, I'd do that for a v2.0. For now, I think it's more important to provide the quickest possible experience to join as a user.

git ssb create ssb easy-ssb-pub then git push ssb master

Found the bug. Fixed in git-ssb v2.3.2. I recommend deleting the remote and then re-running those commands after updating git-ssb, so that the repo is compatible with clients.

For now, I think it's more important to provide the quickest possible experience to join as a user

Agreed.

Okay, I updated and re-ran. Let's try this: %M1M+D5+... working?