You are reading content from Scuttlebutt
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@enkiv2 %zgWST83U613PQll4d0q4GMaORN0ys9hjLiAWmud6c4k=.sha256
Voted I created a new public SSB room with `go-ssb-room`: https://ssb-room.j-serv
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@cel %fJClQX/2o7RzacwOwuzlZDy4jBGvB3gfA4vrVWnhujQ=.sha256
Voted Hi [@The System](@7Y4nwfQmVtAilEzi5knXdS2gilW7cGKSHXdXoT086LM=.ed25519), pe
User has not chosen to be hosted publicly
@The System %JEc6k2wl0hBm/6lNODEMvxGUrb2ERxyh91W048xcP4k=.sha256
Re: %CrJhZDgh6

E: Thanks so much! That fixed it! Also figured out that I also had another problem, as the repo that the insert-user script was different from the one that the systemd service used, so it seems to be working now.

@The System %52ihXb+Kb8yRdB2Kcxmkwkiwl5d/CRnNgsnXK7l4P4w=.sha256
Voted Hi [@The System](@7Y4nwfQmVtAilEzi5knXdS2gilW7cGKSHXdXoT086LM=.ed25519), pe
User has chosen not to be hosted publicly
@The System %efDmhk3/ZIkPu41kqCLebbJkFUN5627IuTh/iLQPTko=.sha256
Re: %CrJhZDgh6

E: Hmm, so after looking into it more, it seems like go-ssb-room is unable to bind to 8008 because my synapse matrix server is running on there. Although in the config for it I've set it to bind to a different port with -lishttp localhost:8899. Does anyone know why it needs to use 8008, or how to change that? Thanks

User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@The System %nUO7iXNZAULr6QlO1reBOOBuoxi6L548Z2VohGQP12A=.sha256
Re: %CrJhZDgh6

Yes, I used my SSB ID as a username in inser-user, and tried to log in with it, but it didn't work. I'm pretty sure I typed in the password correctly, but just in case, just to test, is there any way to reset the user password?

@The System %IbrJ3kuxBFNmTaC9mbpzqkRr6w2/ENY6x6MU2Zn0yxw=.sha256
Voted Hi! I've managed to log in with my SSB ID (`@Wnc8G38UdGXlRijohy0hlvSiEEgYyQ
@The System %CrJhZDgh62/mLhKNDYR4pdoVycP/UWySzjwXMTMnap4=.sha256

Hi everyone. I'm trying to setup an ssb-rooms server, and has followed the documentation and got everything installed, and created an admin user. But when I try to sign in to the website, if I use password sign in, it says I have the wrong username/password. I don't exactly know what I'm supposed to use as the username though. I've tried my public key/scuttlebutt id thing, admin, everything, but it just doesn't work. And when I try the "Sign in with SSB" option, firefox just complains cause it can't understand the ssb:// part.

Does anyone know how I could go about figuring this out? Thanks.

User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@mikey %aShg5B+/aw0fFTR6AKXKxxCuQ5szMVMLZXUKSkHqy8w=.sha256
Voted ... continuing ... That is the type of problem we've been trying to solve
@mikey %CcLz5HOoWxB4B9CCA7rIrPOHIkllznM+LLKOLx70sCA=.sha256
Voted Hey [@cel-desktop](@lOUVT+Phkvai9a/cCS/RKo+S9hnPAQdVixms/7ldpPA=.ed25519),
@mikey %JmHodV2YSKqBRbaioltym8YomDgoK30Jqfm2D+kM4JE=.sha256
Voted ## Concerns about identification of users and rooms I am concerned about u
User has not chosen to be hosted publicly
@cel %6tgF0kjehWRKXbZHd7NOuZaOz72JljTlZdOxmFwnhOI=.sha256
Voted i use `ssb-server` (:
@SoapDog (Macbook Air M1) %I9f//RFe+/KzPlE/fmWNXF4lhPI2jiTcgIl1STe/swI=.sha256
Voted patchfoo would benefit from Scuttle Shell, similarly to Patchfox
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@cel %s6mh6J4QFGnrmHXlbLATIsHQ+4gJmRcCS9jOaeaRcmI=.sha256
Re: %5y05HEjeH

patchfoo would benefit from Scuttle Shell, similarly to Patchfox

User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
@SoapDog (Macbook Air M1) %HKGtwe7ALzeqhjEiODbtv4w+vLbWHIIVXoSvyjj2Ma8=.sha256
Re: %5y05HEjeH

@andrestaltz the companion app for Patchfox is Scuttle Shell. The new funding request has it in the budget, maybe it should have a higher priority as it is is becoming clearer that simply relying on Patchwork server for the new features won't be possible.

This might also affect Patchfoo, I don't know which server most Patchfoo users are using but the binaries @cel ships don't include a server.

@andrestaltz %2Cd+LGcJ6e8OwLbATtPvi2lBeV61/ZRYmqVFE49ytAQ=.sha256
Re: %5y05HEjeH

@SoapDog (Macbook Air) It's unfortunate, but we need those new muxrpc APIs for those features to work. HTTP Invites worked because they are resolved entirely over HTTP.

As far as I understand how secret-stack works, the manifest is the same for local peer and remote peer, so if you want to call muxrpc foo() on another peer, your local SSB server needs to have foo in the manifest. So either you install a plugin that defines that manifest, or you manually modify the manifest somehow (some systems — maybe legacy sbot, can't remember — allow you to edit a config file, I think ~/.ssb/manifest.json). That would allow you to call room.registerAlias(), but you need to call it on the remote peer, not on the local peer. I don't know how ssb-client allows you to call remote RPCs, I don't think it allows? I think it only allows calling RPCs on the local SSB peer.

So it seems that if you can't update the code in the backend, the client-side SSB app is limited to what plugins currently are there installed.

I would really recommend making a simple backend tool as a companion to Patchfox. We are going to be using new RPCs also for our upcoming work with metafeeds.

User has not chosen to be hosted publicly
@SoapDog (Macbook Air M1) %5y05HEjeHSL73KwDyuzUnzl3mHoqc+McQ4QA9jhHXvs=.sha256

Need help with Rooms 2.0 for pure client-side work

At the moment, I can't get Patchfox to register aliases because ssb-room-client does not work on the client-side. That is happening because I can't load the tunnel plugin on the client-side.

It seems to me that to make Rooms 2.0 work on Patchfox, there needs to be some more muxrpc calls implemented allowing Patchfox just to forward requests to the running server. As mentioned in another thread, I got joining a room working, but I can't get aliases working.

At this point, I'm above my head trying to shoehorn backend plugins into the frontend. I'm lost regarding what is the path forward.

This kind of problem will affect any client that is not running it's own SSB server. At the moment I can see it affecting Patchfox and maybe Patchfoo.

User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
@cryptix %aTWoR9Uved4lRbxm0k0YUNS7SEIEPOi7KMbSsnuZePo=.sha256
Voted @andrestaltz thanks for responding and explaining the design/architectural
User has chosen not to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@cel-desktop %ez7qvpN+3+PeTfVaS1oP2OjH4XDtn9Z2UG5SxiHOZqM=.sha256
Re: %GHdg3975n

@andrestaltz thanks for responding and explaining the design/architectural decisions.

I appreciate your work and collaboration with the SSB community.

@cel-desktop %4brOAMnw5RUE5idvl+0cuGhSDvl/Qe3VCLdsE/NzJGY=.sha256
Voted ... continuing ... That is the type of problem we've been trying to solve
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@enkiv2 %Fptne5JJXwnMotqu4PcS2yBt8D7bucHvnF9etjIhrfY=.sha256
Voted > (1) would mean significant amount of work to be done on each of the SSB a
@enkiv2 %ax2MlanFrUOojyUGWMMD4fjPtpVZ91w2aO+OnYLmWCs=.sha256
Voted ... continuing ... That is the type of problem we've been trying to solve
@enkiv2 %/WcWuaDCj18FChkqJ7e0kg8HMaA4gF909HtboQHO1gQ=.sha256
Voted Hey [@cel-desktop](@lOUVT+Phkvai9a/cCS/RKo+S9hnPAQdVixms/7ldpPA=.ed25519),
@enkiv2 %rY7NOulDI0ohT1TlP7fBfIxOjHysnVNnGbtIefSAIho=.sha256
Voted ## Concerns about identification of users and rooms I am concerned about u
User has not chosen to be hosted publicly
@ओषधिः %N/pT1t5gAyQHT6l9wzuTKFn4nvakWbBLkXdlpCgx3+k=.sha256
Voted Hey [@cel-desktop](@lOUVT+Phkvai9a/cCS/RKo+S9hnPAQdVixms/7ldpPA=.ed25519),
@cryptix %71PywVKCHV37WII7r/bqR4CCtGoyEu75XwBYv8mPw8c=.sha256
Voted > (1) would mean significant amount of work to be done on each of the SSB a
@andrestaltz %jj62JmG/yqOvkVOY6kzsvFm2fZyG1fG0fKdJGafECJ4=.sha256
Voted > (1) would mean significant amount of work to be done on each of the SSB a
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@andrestaltz %2lzqOyNCXXeqsrfg3DAglgP+ksGzjX9GaJ/BR1hKQDA=.sha256
Re: %GHdg3975n

... continuing ...

That is the type of problem we've been trying to solve together with Wouter, and as you see, it's a connectivity/location issue, not an identification/authenticity issue. Wouter went to great lengths to test out all these codes, either multiserver address or SSB URI or mastodon style @staltz@room.com, in several common mobile apps, and he made it a priority that the code must be rendered correctly in those apps, because onboarding requires this "third-party communication medium", either another app or written/spoken transmission. You can see from UX research sprint 2 report (search for "alias") and sprint 3 report (page 28) that we had to rule out some of those options. The format staltz.room.com is Wouter's idea and I initially resisted it but over time learned that it's the best for user experience, it will make connection much simpler and universally useful (can be orally transmitted, can be written on paper or poster, can be shared in apps).

Associating domain names and/or URLs to SSB IDs may be useful. It is good that multiple aliases per user is supported.

Yes, and I must add that aliases are optional, as are many other aspects of SSB. A user can be a member of a room without registering an alias in that room. Or they may have one alias, or many aliases. They can even have multiple aliases on multiple distinct rooms. And the choice of having an alias belongs to the user, e.g. not to the room server. It's opt-in. Maybe this is clear for some people, but maybe not for others, so it had to be clarified.

If room aliases are hostnames, their use is susceptible to Man-in-the-Middle, DNS hijacking, or the room operator redirecting the alias.

These are possible under DNS and HTTPS, but I wouldn't see them as critical. There are many other websites we depend on for sensitive topics (banking, personal information, etc) that are built on top of DNS and HTTPS. The advantage with rooms is that the stakes are not that high: if the room is compromised, there is no user data hosted on it because the room does not replicate feeds, and tunneled connections are anyway onion-encrypted.

The redirection threat that you mentioned is possible, and would allow a room admin to impersonate Alice when Bob joins, only if Bob joins after the impersonation began, and only for initial onboarding. On another note, we already have a very similar possibility for impersonation in the SSB community that applies in all moments post-onboarding, which is just spoofing about name and about image. This is something that @cblgh did to me this month as April's Fool, and successfully tricked some people. The answer is always: check the SSB ID. So while it's a possibility with room aliases, it has to be put into context in relation to all the other impersonation methods currently available.

It is also possible to augment these features in the future to support Tor onion links for aliases (this is something we're already actively discussing) and other means. Like @Powersource (phone) said, it's entirely possible to support raw IP address too. And other means, I can imagine a bunch. Optionality in SSB is great. Again, nothing is without downsides, and Tor onion aliases would be for those who want to gain additional privacy at the cost of lower user friendliness.

I am concerned about use of HTTPS in relation to SSB, including for Invite links and for the Room Web Dashboard.
...
a stronger step would be to implement the UI locally, only interacting with the Room server via SHS/Muxrpc and/or SSB messages.

The goal we're optimizing for is "reduce the work needed for SSB apps (in the plural) to be compatible with these features". I didn't want rooms 2.0 to be a Manyverse-only thing, and I was considering 3 options:

  1. muxrpc APIs for each of these actions to configure the room
  2. private messages sent to the room, to configure it
  3. HTTPS configuration dashboard

(1) would mean significant amount of work to be done on each of the SSB apps. (2) would mean that the room would have to replicate feeds of its members which undermines the purpose of the room as a non-pub, and would still require each of the SSB apps to properly define what is a valid and invalid private message to configure the room. (3) meant a lot of new work, such as SSB HTTP Auth, but it would mean that many SSB apps could manage the state of the room.

Finally, one important assumption for rooms is that they are a point-of-trust for specific type of trust: confidence in administrating connectivity. You choose a room according to how much you trust the people behind to not: log your IP addresses, track your metadata, use weak TLS CAs susceptible to MITM etc. Note that the connections over DHT have serious connectivity-privacy issues, and while I built things like ssb-dht-invite in the past, I wouldn't use it anymore. I'm happy to change my own opinions in the future if an experiment turns out to be a net negative. Also it's not a great idea to connect to many servers (pubs or rooms) because then you're sprinkling your IP address and connectivity metadata to many places, and increasing the likelihood that one of them will abuse that metadata. The ideal scenario in which rooms should be used is: you are member of 2–4 rooms in total, thus only max 4 servers have your IP address, although you can tunnel-connect to countless others via those rooms. Also, I assume that ideally those rooms would be managed in a democratic manner and crowdfunded. See this other thread about democratically managing rooms.

🙏

@andrestaltz %ViMW+8tT+4m5UO7bfhKSpGXpIDDIMv5dVZyD3hYOgcg=.sha256
Re: %GHdg3975n

Hey @cel-desktop, thanks for the feedback, this is the kind of comment I was looking for when I was sketching rooms 2.0 last year.

As you said, it comes a bit too late in the process, so we won't be able to change much at this point. We're close to reaching the deadline with NGIp, and we have to focus on finishing the last bits. What I'll do with your feedback is incorporate it as Security Considerations in the rooms 2.0 spec, and I'll think of how to communicate in UI that aliases are not a substitute for cryptographic IDs. So it's still useful feedback.

Unfortunately grants work in a very waterfall process way where we have to define up front what we will do and in what timeline, so we just have to go forwards with it regardless of late feedback. This is a pattern with grants (from my experience with NGI Zero) and seems to also have affected Wouter's UX research grant, where some decisions just had to go forwards despite being suboptimal (e.g. the small sample size of the users interviewed was a problem, and this is a concern we raised in a manyverse team meeting that included David Gomez, Zelf, Nico Pace). We're trying to do our best with the money and time given. I much prefer the OpenCollective model of funding, where there is much more room for iterative feedback-rich processes.

I believe using cryptographic account identifiers is essential to how SSB supports user autonomy through decentralization.

Your work with DIDs is commendable, and have a different purpose than aliases have. I wouldn't call aliases identifiers, the SSB ID is still the identifier (whether it's @lOUVT+Phkvai9a/cCS/RKo+S9hnPAQdVixms/7ldpPA=.ed25519 or did:ssb:ed25519:lOUVT+Phkvai9a/cCS/RKo+S9hnPAQdVixms/7ldpPA= is just a matter of different standards). I also believe that nothing is without downsides, so there are downsides to SSB IDs and there are downsides to aliases. The downside of aliases is that it cannot function as a fully reliable identifier, even though it may look like an identifier to some users. The downside of SSB IDs is that they are not memorable and user friendly to exchange in oral ways or written ways.

Aliases are aimed at solving the user friendliness of locating a feed. SSB IDs identify a feed, but they don't tell how to connect with that feed. So we've seen many times people post their SSB IDs on other platforms like Twitter bio, thinking that it helps others locate them on SSB, but they don't, they just identify them on SSB. There are non-user-friendly ways of locating a user, such as posting a tuple of multiserver addresses (e.g. net:IPADDR:PORT~shs:ROOMID plus tunnel:ROOMID:USERID), but many apps and websites have a difficulty parsing and rendering multiserver addresses, e.g. Twitter DM picks the host in the multiserver address and wraps in a Twitter analytics redirector and thus breaks the rest of the multiserver code, rendering it useless if put in an SSB app, since the app will try to dial the Twitter analytics redirector. This is something I've often bumped into when inviting friends from other platforms to SSB.

... continues ...

@cryptix %mCfzn6SC41NMjM0nEd8MnHZI/RpYIWb7t0e71Pvzyao=.sha256
Re: %qEoPh5CpX

i'm actually contemplating some elixir experiments but reusing some of earlbutt from @moid for the heavy lifting of shs+murpc. There is way too much wheel to re-invent there IMHO and erlang<>elixir works great AFAIKT from my first experiments.

@cryptix %DzhilE2RI63nr4IHac0uX/Nn2bUI5ax4D6Q6LcAf/bU=.sha256
Voted [@cel-desktop](@lOUVT+Phkvai9a/cCS/RKo+S9hnPAQdVixms/7ldpPA=.ed25519) than
@cryptix %rrH98BTjWYh5V3EogYs09iZz8JipD0RxvUKhp0JGjfo=.sha256
Voted ## Concerns about identification of users and rooms I am concerned about u
@cryptix %DCPxb5iV0hyq0kXTB7Ndpnfdd5/LJg34CyH/ih2z0dU=.sha256
Voted we could do 2YVYXQclEJHVzCON5dsLRwf65b2S6HnvxpGS8.onion it's the default
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@cel-desktop %iyBwlbRgNGpGlhT71yGLY7MKuK6cndTtyN6ejGxt7bE=.sha256
Voted [@Powersource (phone)](@WuIiSwHyJS9v8EZ8RUL8Jgft9GSOPd02EvAaT+3U8oM=.ed2551
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
User has chosen not to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
@Daan %d8VuZoCJOvfDsrdNHRro0dD64QUmzU4G5Sv5UukM2SE=.sha256
Voted FWIW, I have removed Manyverse from my phone and life. I've semi-committed
User has not chosen to be hosted publicly
@ओषधिः %eSErn+8K1Nu7E6ySoisufLE+x7TOc3qE79fWnherPJc=.sha256
Voted ## Concerns about identification of users and rooms I am concerned about u
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
@Rabble %E2hjFZ1YoInEZEesgS5+a3pLUNcKIBvRYa1Hz9Sd0vQ=.sha256
Voted ## Concerns about identification of users and rooms I am concerned about u
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
@cel-desktop %GHdg3975nfBQ6MeqPfTXVjxECczB4erYKwwP7JfIZ9M=.sha256

Concerns about identification of users and rooms

I am concerned about use of domain names as user and room identifiers in SSB Rooms 2.0.

I believe using cryptographic account identifiers is essential to how SSB supports user autonomy through decentralization. While domain names may be fun to pick, they are still a hierarchical namespace, subject to authoritarianism and rent seeking.

Associating domain names and/or URLs to SSB IDs may be useful. It is good that multiple aliases per user is supported. But I am still concerned about the effects on security and user autonomy of using user identifiers without cryptographic material, including as part of onboarding.

If room aliases are hostnames, their use is susceptible to Man-in-the-Middle, DNS hijacking, or the room operator redirecting the alias.

An alias (also known as "room alias") is a string that identifies an internal user, designed to be short and human-friendly, similar to email addresses and Mastodon WebFinger addresses. The purpose of aliases is to improve the user experience of accurately (1) identifying the internal user and (2) locating the internal user at a room server for the purpose of establishing a connection with them.

The examples I have seen in the Manyverse UX research appear to use aliases as either clickable or copy-pastable links. Addresses do not seem to be required to be memorized or handwritten (except to make the paper prototype). So I posit that including cryptographic material, in particular the user's SSB feed ID, in invite links, would not harm usability. I believe it would help ensure security and decentralization (distribution of power to users) to use public keys as identifiers. If a hostname is needed for establishing an initial connection, the link can include hostnames, but these do not need to subsume the user's cryptographic account identifier.

I'm also concerned about connections to room servers using domain names instead of public keys for authentication and identification. With existing SSB Rooms, the connection to the room is authenticated and encrypted based on the room's public key which is in the invite code, using Secret Handshake. If a v2 room identified only be a domain name, anyone with control over DNS or of that hostname could gain control of the room. Control of a room means being able to reject or degrade incoming connections, associate incoming IP addresses with SSB IDs, block or degrade connections between peers internally (cf. "net neutrality") and capture metadata about the tunneled peer connections. Those are security and privacy considerations for Rooms in general, but if rooms are authenticated based only on domain names and/or HTTPS, it becomes more significant. Using a rooms v2 invite code is subject to man-in-the-middle since the invite code is in the URL, compared to traditional SSB pub or room invites codes which use the invite code as part of the secret-handshake.

I am concerned about use of HTTPS in relation to SSB, including for Invite links and for the Room Web Dashboard.
SSB provides for authenticated communication between peers, and can be used for interaction between SSB users, including for management of room membership. For onboarding, an HTTPS link may still be needed (More secure bootstrapping methods should be pursued) but in other cases I think it can be avoided. A Web Dashboard hosted by the room server may be an avenue for capture of SSB, as functionality is added to the room that local users do not have. I think this potential may be mitigated somewhat by using AGPL for the room server and dashboard, but a stronger step would be to implement the UI locally, only interacting with the Room server via SHS/Muxrpc and/or SSB messages.

I am sorry to raise these concerns when it seems that much work has been done already. Manyverse's UX Research is commendable and addressing important issues for SSB - but I only just learned about it, and it has also brought these issues with rooms2 into focus for me.

#ssb #ssbc #manyverse #security #decentralization #rooms

@entron %8rNRxNAF0xpfY7IKGg1jY4ohmtpMg8Z3DqquZWvyk0Q=.sha256
Re: %c2UsoJuX7

Then the warning "only join the room you trust" will not work here then... I am not sure whether its a feature or a bug to me though. Let me try it out.

@andrestaltz %SZ5yWPuxmIqut4gClqMS6cIrNjD2vv/omCjlTCi1veQ=.sha256
Re: %c2UsoJuX7

Yes Patchwork picks up on any address is finds and automatically joins them. Feature to some. Bug to others.

@entron %U8loQB5Y5dE8qVDpkXCAENWX5RKwr2VkwKDnEVsrnks=.sha256
Re: %c2UsoJuX7

I took a look of the conn.json file and found lots of rooms I never joined by myself?? Does ssb/patchwork search and join rooms automatically? @Daan

@entron %0CckrTi+KoD52qrk9qPg3QnV+8rrGCsdsh9kn2MwZHc=.sha256
Voted That would belong to the Patchwork FAQ. A *hammer* way of doing it is editi
@andrestaltz %NjR7wND0Tu+YxDrgtUWwf6cK2Fq4j6G1quBtEvlgPz8=.sha256
Re: %c2UsoJuX7

That would belong to the Patchwork FAQ. A hammer way of doing it is editing the JSON file ~/.ssb/conn.json to remove the key-value for the room server.

@entron %c2UsoJuX7YJ8v2gnhJNwcephPAXeJRGB7V0Uo1nXnRQ=.sha256

I searched the room FAQ and other places but could not find a way to quite a room in #patchwork once I have added it. Could someone guide me hint?

@andrestaltz , @Daan

@entron %j+0KOzhfjJm9mgyhBtw3ehCGIoggmtrlVzv2wp/EbG0=.sha256
Subscribed to channel #ssb-rooms
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@John Goerzen %u1tI3elsZO8DPz6PnOAgEEYuCckU+y5C6kWi9Hrs5G4=.sha256
Subscribed to channel #ssb-rooms
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@Daan %InxY8NnEPe9Yy3PHIcZ7g0o7vXH8LYnAnIk2Havzfqw=.sha256
Subscribed to channel #ssb-rooms
User has not chosen to be hosted publicly
@cryptix %vERwcmSQDSC63ch5655d1hkZu+heK64XQq0/SmFfBnI=.sha256
Voted [@andrestaltz_phone](@+UMKhpbzXAII+2/7ZlsgkJwIsxdfeFi36Z5Rk1gCfY0=.ed25519)
User has not chosen to be hosted publicly
@Rabble %TUT2enfsvgASbz/JLSCwoIW+CetrWVqYrUCphM6YoFY=.sha256
Voted I really like the concept of SSB-Rooms, but I feel they are too open. Anyo
User has not chosen to be hosted publicly
@Danie %FKovh28AuXrDxU052vaR9AS+jT0rMebvEEipNe78d/k=.sha256
Subscribed to channel #ssb-rooms
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@cryptix %uYRwRhdOmK1Qo28knoXNN/DxZlbbDrFQ/F36SRhpQOs=.sha256
Re: %Cq1XsaZdA

I also asked what the actual muxrpc calls are called and what part is forked exactly, so that I can make a server in go but need to allocate more time to it.

https://github.com/cryptoscope/ssb/issues/42

I’m wondering how it punches through our ISPs and stuff.

@SoapDog (SPX) it actually doesn't. The room server has to carry the whole traffic.

I briefly asked @paul how they do it in beaker. Apparently a DHT is enough as a signaling server to do some STUNish magic but I also need to follow up on that.

@cryptix %DflpCWKHeySeQMb7pkRLVP6m/vYB0FYe/IiT1ZdGigA=.sha256
Voted Are SSB Rooms related to `ssb-tunnel`? How does the pearing through a room
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@VictorBjelkholm (lasoa) %+ShYmqJ2d9tm3g/AxZZuFwFTX1sAckQlCrxsHDWeBQI=.sha256
Subscribed to channel #ssb-rooms
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
@lancew %noD13tdGtRh5tx71BM1XJ1KNVJk41hxglS1ZcwPSru0=.sha256
Subscribed to channel #ssb-rooms
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has not chosen to be hosted publicly
User has chosen not to be hosted publicly
User has not chosen to be hosted publicly
@Thomas Renkert %AgxE+54HmDN9r1OzVTQM/c1In4ItAnrIS4v3bAaijmA=.sha256
Subscribed to channel #ssb-rooms
Join Scuttlebutt now