Public community, private community, or a mix? (context: migrating from Facebook)

In moving a community from a private group on Facebook to Discourse, I’m wondering if there is an opportunity to open up parts of it and make them public. With the move, the community is going to gain structure (see Structuring an active support community migrating from Facebook). The community that “inspired” the one on Facebook is partially public, and I am a big believer in “keep it public unless there is a good reason to make it private”. Public content is more findable, more visible, can help more people, and it also can lower the barrier to joining if you get to actually see what you are joining.

What is making me hesitate is the migration context (see Migrating from Facebook: specific challenges, and some thoughts) – if I were starting from scratch I would certainly be thinking differently, but there, the hope is to manage to “win over” a large chunk of the existing community, and I fear that being “in the open on the internets” will have a chilling effect regarding participation for my community.

I’m toying with leaving certain parts public, but not all. Maybe the welcome area? the “supply closet” space where people can give/sell material they don’t need anymore? how about questions about food, is that really an issue if it’s public? But then, I’m thinking that a community of not very technologically sophisticated users might have a hard time with “oh, here’s it’s public, but there it’s private”.

I guess I should go “all private” for simplicity’s sake, but it hurts my “open web” heart a bit. Perhaps I also need to accept that 2026 is not 2006 anymore, and the internet has changed a lot.

Does anybody else have thoughts to share regarding how to deal with private/public in medical/paramedical (even though here it’s “animal medical”) support communities?

And when migrating, how much should one try to preserve the current community culture, versus change/influence it with the move?

Don’t over-think it.

Do you want new organically acquired new members gained via search? Or invite only. That will answer your question.

3 likes

New members will have to find the community – that is what happens now on facebook. Their cat gets a diabetes diagnosis, the sky falls on their head and they search for “cat diabetes” on Facebook and find our group (it’s the “strongest” one on the platform). Sometimes, rarely, they google, and find the facebook group through the website. There are also cases where they post in another cat-related facebook group and somebody points them to us. Sometimes their veterinarian sends them.

Whatever choices we make on the Discourse side, the “acquisition” part of the ecosystem is going to be altered. I intend to find a way to keep the facebook group alive (low-maintenance) to funnel facebook users to the community on Discourse, but I’m also hoping that with a better web presence people will find us that way too. Our documentation will be moved from Google Docs to public pages on Discourse, so that should be indexed (I’m assuming?) and I’ve also been thinking about revamping the website on the TLD for better visibility.

Members often discuss private/personal issues: lack of support from loved ones and even spouses, disagreements/dissatisfaction with their veterinarian (we pay close attention to keeping it civil), information on their work schedules and finances, etc. I don’t see them talking about that in public the way they do now in private, and they are necessary issues to cover in our support group.

However, there are other aspects which would be viable in public. Also, if you have a public community, there might be more of a trend towards nicknames rather than real names, as is the case on Facebook.

Promised, I’m doing my best not to over-think it :sweat_smile:

1 like

Sounds like you want it to be public. A split approach is good then. This also encourages people to sign up if they know they will see more “stuff” :face_with_monocle::+1:t3:

1 like

Don’t you think there might be a “chilling effect” for non-technical users to have some of what they would have previously discussed in private now be in public? That’s what I’m concerned about (in addition to figuring out what remains private and what we make public). I’m worried it will add another layer of confusion/complexity for them… maybe worrying too much? (possible, when I see some of the public groups on Facebook :sweat_smile:)

What about

? Would it address some of your concerns (despite the small warning in the description)?

Or perhaps

?

2 likes

You’ve got valid concerns - I’ve grappled with this ever since my Discourse journey began 7 years ago.

I remember hearing the advice “chose either open or closed, not both!” early on, which I have largely ignored. However, it is useful advice!

The biggest issue is in fact that users seem to really struggle with the fact that a site can be both open and closed at the same time. Discourse is primarily designed as an open discussion space, and the private spaces are quite discreet really. It also works quite nicely as a fully private service too. But users get confused when this boundary is traversed.

Now, the fundamental problem is that there are very strong practical reasons for wanting both on the same site - a single, easily maintainable, user list and a single site to maintain are the primary ones. And somethings are great in public, and others need levels of discretion. Community will always be thus!

Discoverability (which seems very important to you) is indeed vital. I have had many users over the years who simply can’t find our site (despite using it a lot). A google search is often their route back. An open site makes this easy.

To overcome / work around this situation I am currently doing this:

  1. Having the private spaces being primarily Messages and Group Messages

  2. Having the public spaces being conventional forum Categories

  3. Having occasional private Categories for specific purposes, but usually only for the the most Discourse-savvy users.

I’d love to have this specific problem addressed by the Discourse design team, as it is both curly and prevalent.

3 likes

ooooh those are super interesting, yes! Bookmarking this. It might be a solution.

Yeah, this is exactly my feeling.

I see the idea but that would work for my community, because we definitely want people posting topics in categories and not using private/group messages. But it’s nice because it’s “understandable”.

In my case, I was toying with the idea of having the welcome/general questions area public, and maybe all the rest private (why not using one or the other solution @Canapin points to above, to help some degree of visibility).

For example, I’m not certain that having the grief support part of the community public would be a good idea – people will want to be able to express themselves “safely”.
Maybe that is the key, actually. Our community on Facebook is very much perceived as a “safe space” by our members, where they can talk about stuff without fear of being judged, and I think the fact it is private plays a big role in that. I’m going to go and look at my structure again with this “safe space” criteria, that might do it.
And that would also be an “easy” way to communicate the nuance between public and private to our members: some of the categories are “safe spaces” in the sense that they are protected, others are not (or less so).

Thanks!!

2 likes

You kind of answered your own question right there. You’ve already made a decision that at least some portion of the site will be publicly viewable, now it is just a matter of how much. Your circumstances are a little unique but I think I would want at least some portion to be open. A landing area, basic info and FAQ. Some folks are nervous about joining a forum or facebook group, (I’m sure you’ve heard the forum term ‘lurker’ - folks who read the forum everyday but never join or post) do you not want to help those folks? of course not we all love cats!

So a possible solution might be to make some type of visual difference between the public and private portions of the site. Something to warn a user that they have left the private portion of the site and are now posting in a topic which is public. This idea taken to it’s extreme would be to style the site to actually appear to be two completely different websites.

It wouldn’t be hard to do because all the private portions of the site require logging in. Once a user logs in, they can be re-direct to a different homepage which could be styled in a completely different way then the public portions of the site

1 like

You might get some ideas from Before You "Build a Community," Decide: Library or Coffee Shop? or The Hawk Origin Story (A Community Builder’s Privacy Paradox). Both touch on the tension between public and private spaces.

1 like

This is what I meant by the Discourse design team taking a look. It isn’t something that is going to work that well with my hacky CSS attempts!!

This absolutely hits the nail on the head.

2 likes

Oh, that is a really great idea! You’re right that if the visual difference is clear, that will help people navigate “indoors” and “outdoors” better.

Regarding the documentation: it was already public, but given it’s in google docs it’s not that visible or indexable.

Thanks!

1 like

Thanks, this was a very useful read. Reminded me of my first steps online 25+ years ago, when I was very much “afraid” of the Big Unknown Internet, and there used a pseudonym – before realising, some years later, that I was building a valuable reputation online that was disconnected from my “real identity”, which led me to completely drop my pseudonym and use my real name pretty much everywhere ever since. Different trajectories, but similar reflections!

Reading your article clarified a few things (the library/coffee shop one too, but not as sharply). DF (the community) is clearly primarily a coffee shop, with a good little library that we built along the years (our documentation, mainly).

The population is 95% female (cat owners, go figure) and I remember that at the time, one of the reasons I made it private on Facebook (aside from the fact that public groups get hammered with spam accounts) and implemented pretty tight checks at the door before letting people in was my awareness of the catfishing (!) risk in strongly female online spaces. In addition to that, this is a very low-tech, not very digital-street-savvy population.

So there is a necessity for privacy not just for people’s comfort and feeling of “safeness”, but also to not expose a vulnerable population to bad actors.

That being said, as we thrive to be of public service to anybody with a diabetic cat, it’s important that we are findable and that people get a chance to see the value (and seriousness, which is uncommon in the “pet space”) of our community before signing up. Clearly, the documentation is going to play a big part here. Having the category descriptions visible, as well as the community rules and principles, some testimonials – that will help.

If I dive in a bit and think about the type of information shared and where doing it in public could present issues. Sorry it’s becoming long but it’s super helpful for me to be able to think about loud about all this.

Location
It’s precious internally to know where people are, which city or area of the city, because it can help us connect them to other members nearby in a crisis, or orient them to a veterinary hospital with the right specialties if they need one. But we probably don’t want this information to be visible to non-members

buy/sell
There is a lot of gifting/second-handing of material like syringes, glucose monitors, and even insulin. There are two issues here: the first is location (if giving in person, or to a lesser extent, you’re not going to send something from Canada to Belgium) and the second is the legally grey aspect of passing on leftover insulin. For those two reasons, this should probably happen in a private zone. We do have people who seek out our community solely to make leftover material available after the death of a pet: so far, we usually do not let these people into the group, we simply give them access to the spreadsheet where we list the offers. I plan on replacing the spreadsheet by a category once we’re on Discourse, but that doesn’t have to be done immediately. We don’t let them in the community because this usually just results in a grief-stricken post for a cat we never had the chance to help - and “dead cat” posts are a big problem in the Facebook group because the algorithm prioritises them (they get a lot of engagement) which means that everyone gets exposed to a lot of dead cats, leading to a distorted view of how “deadly” diabetes is (it’s not, actually, very well treatable and manageable). So on Discourse, we would probably give these people access to the “buy/sell” and “grief” categories and that’s pretty much it.

veterinarian disagreements

Feline diabetes is a niche topic and not all generalist vets are up-to-date on best practices. In France in particular, there is also (particularly amongst older professionals) a “I’m the doctor I know best” attitude that can be problematic. There are also pet owners who are not good at diplomatically suggesting to their vet that there might be scientific/medical advances they are not aware of. In any case, it’s precious that our community gives people a space to talk about the difficulties they face with their veterinarians (in a respectful way of course, we’re very strict about that). We also give them ressources to try and educate their vets when necessary/useful/possible, and help them identify when it really is a blocked situation that requires looking for a second opinion or changing vets. I definitely do not think that these are conversations people would be comfortable having “in public”.

The present situation regarding that on Facebook is actually already a little uncomfortable: we have a separate group for veterinarians, but they are also invited to join the main group as lurkers. So, sometimes our members will bring up issues regarding their vets without realising the vet or their colleagues are in the group. In practice however, vets have very little time to engage with the community on the vet side, let alone go and hang out in the main group. But it can happen. The fact that search in Facebook groups is pretty bad has kept this “privacy by obscurity/ignorance” situation viable so far, but as you can imagine I’m not completely comfortable with it. From my discussions with vets, they don’t really care: most of the online spaces are so prone to vet-bashing they generally never go and read “pet owner” stuff, and are extremely appreciative of how well we moderate our community in that respect. So our pet owners feel like they are in a private space for these discussions (though it might not be as private as they think, with 8k members… and more veterinarians than they imagine, often with pseudonyms), and I think that if we were having them “on the open internet” they clearly would not be possible.

personal information: family, work, schedules

Like location, knowing if somebody lives alone or not, what support they have at home or not, if they are away from home or not during the day, if they have irregular schedules – all that is important because it will influence the advice we give people regarding insulin dosage, surveillance, or dealing with a cat that is not doing well. Given the population our community is made of, it is probably better if discussions relying on this kind of very personal context happens in private. So the general support category, the dosing advice one, dealing with sick animals or emergencies, all that stays private.

food

What to feed a diabetic cat is a big topic of discussion. It’s one I’d like to be able to keep public, because there is a lot of disinformation out there, and one of our strengths is precisely our science-based approach to all this, which can amongst other things help build trust with professionals. As I see it the only “sensitive” information that might come up in these conversations is finances (but who doesn’t want to spend less on cat food?) and maybe presence/absence at home regarding distribution style (but we recommend free-feeding generally). So I think this is a topic that we could leave “public”, on the condition there is a way to mark public and private spaces in a very clear way for members.

medical training

This is another category I’d like to make public, because it is important, but for it to be most helpful to our members we’re going to be having discussions where people film themselves doing injections or the like, and I don’t see us “forcing” that kind of content to be public.

Summary

This bit is going to be a prerequisite:

Like @nathank I’m not sure my 20-year-old CSS skills are up to the challenge. Given what I’ve read in your (@HAWK ) article about how fundamental navigating public/private aspects of a community are, I would definitely join nathank in wishing for a built-in way to very clearly signpost if a space is public or not (the little locks are nice, but frankly, not sufficient imho for a non-tech population).

Assuming that works I’m left with:

  • documentation (the “library” part of DF) is public
  • main support areas are private (including grief support, off-topic)
  • food could be public
  • buy/sell needs to be private
  • medical training needs to be private
  • tech support (not mentioned, but no-brainer): private, so people can screenshot things and give usernames without them ending up in search engines

=> this kind of argues for a public “welcome/new members/general questions” area (but will that hold people back from participating? always that tension…)
=> a bunch of “personal” information (city, family status, etc) is something I’d planned on managing with custom user fields, can those be made visible only to members?

Regarding search engine indexing: by default, does Discourse allow all public content to be indexed?

Sorry once again for the verbose post…

You can see the content of robots.txt here: /admin/customize/robots

1 like