You are reading content from Scuttlebutt
@agentofuser %In9gsWIeqqj6LxILd8OSQSaz6sZqIflj2omvAF+U7MU=.sha256

Is there any problem in being both a user and a pub in the same sbot instance/process/id/keypair?

I'm running stand-alone sbot with the identity I originally created via Patchwork, and using Patchbay (without embedded sbot) as a client.

I'm also using the same sbot server to host a v3 onion service ("#hidden-services") #tor pub.

If there's no problem with this setup, I can hand out invitations to those who are interested in the added privacy.

@cryptix %iBTbXH9YsHS0hFDGpKJUNJ6dJhwiEyCyIbg975pN2aU=.sha256

Is there any problem in being both a user and a pub in the same sbot instance/process/id/keypair?

nope, That is perfectly fine. A pub is no different from other sbot servers - it's just reachable _pub_licly.

I've posted pub messages about myself with onion hosts in the past and other have as well. Same works for other vpns or overlay networks like cjdns.

The here be dragons territory starts when you copy the .ssb/secret to more than one machine and worse: post from multiple instances.

@agentofuser %c49R1uH5izaS30IdHJsqZOrKUE4yRbSWFuqkd+jKKco=.sha256

Cool! So the need for clearnet pubs is basically for NAT traversal?

It would be cool if the "user as onion service" usecase was better supported. #someoneshould maybe embed #tor along with #sbot on distributions like the downloadable Patchwork releases. Just having a stable name in a flat address space would already be worth it, let alone the added metadata resistance and stuff.

Ricochet does this and I find it an awesome design.

Join Scuttlebutt now