Or maybe a "room server" is what I want? I don't really understand the difference. The FAQ makes it sound like "one stores content, one just forwards it".
@sam depends on your priorities, but you'll probably want a room server. your understanding is basically correct in that a pub server serves as a peer that will store the content it syncs from connected peers, whereas a room server only acts as a discovery mechanism between peers and doesn't store any content. can send you an invite to a room server in a bit :)
@andrew_chou Thanks! I guess I still don't understand the difference, what's the point of storing vs. not storing the data? Don't they both facilitate discovery, I just have to download the data from a different place?
@sam yes but keep in mind that joining a pub means that you follow it and it follows you (I think, I haven't used a pub in a while so could be wrong). this means that you'll sync data from anyone else that follows it, regardless of if you follow those other peers (or have them within your hops range). it's just another online peer in that sense
@sam the distinction with rooms is that they're purely a discovery mechanism - you still have to have someone within your hops range in order to sync their data and vice versa (done by explicitly following peers and/or configuring your hop distance). so a couple of people belonging to the same room doesn't necessarily mean that they will sync with each other
@andrew_chou ahh okay, so a pub server is kind of like following a group in more traditional social media and a room server is for discovering new contacts; got it! Thanks for the tutorial and the invite!
@sam no problem! will add one last note about pub servers: they can be configured to openly accept any peers without an invite code, which is somewhat undesirable since you'll be syncing data with completely unknown peers at a theoretically infinite scale in that case, hence why I usually avoid using them nowadays 😄
@andrew_chou Makes sense, thanks! I can't even get two of my own devices to connect though, so I may not make it as far as actually trying servers for now, sadly. Thanks again for all your help!
@sam hm, they're on the same wifi network right? it's been a while since I've tried to onboard new devices so can't remember if I also initially ran into problems with discovery 🤔 (don't think I did)
@andrew_chou yah, I can see one device from the other (some of the time, it's flickering on and offline constantly) but not the other way around and none of the connect/follow, etc. buttons seem to do anything. That's another question actually, what's the difference between "connect" and "follow"?
@sam hm I feel like I may have seen that in an issue on Gitlab. Re: your question on connecting vs following, connecting enables data flow between peers, whereas following indicates that you want to sync that peer's data. So you could connect to peer A as a means of getting data from peer B (who you follow or have within your hops range), where A has B's data. in that case, you wouldn't get A's data - just B's
@andrew_chou oh wow, that's extremely confusing, I'll have to think of the implications of this for a bit. I'm afraid this is all starting to sound too confusing for me, but I really appreciate the help. I won't give up on the experiment quite yet.
@sam yeah tbh, I had to ask Staltz (creator of Manyverse) about the difference since I didn't fully know it myself when you asked. lots of learning when it comes to SSB 😅
@andrew_chou What is SSB? (and in that case, sorry to make you do my research for me! Feel free to say "I don't know, go search for it yourself" and I'll happily do so; just figured that while I have an expert to chat with I'd take advantage of it :) )
A Fediverse instance for people interested in cooperative and collective projects.