This week, I'm trying to focus on the last few pieces needed to finally get the site's code open-sourced (really, I am!). One of those pieces is that we'll need a group on Tildes for discussing development, answering related questions, and so on. The obvious location for this is something like ~tildes.dev, but adding it opens up a few questions related to the group hierarchy in general, so that's what I want to talk about today.
Currently, we only have one subgroup on the site, this one (~tildes.official). The way it works right now, if you visit or subscribe to ~tildes, you will also see the content from ~tildes.official. You also have the option of going to ~tildes.official directly, so that you see only the content from that group without the posts from its parent group. However, there's no way to see only the content from ~tildes without ~tildes.official. This will become more significant when ~tildes.dev is added, because that group will probably only be interesting to a small group of the site's users—people that are involved in (or interested in) the actual code/development behind the site.
So now we have a more interesting case, a subgroup that most people looking at the parent probably won't want to see. How should this work in practice? Some more specific questions that might help thinking through it:
- When someone visits ~tildes, do they see ~tildes.dev posts in there?
- When someone subscribes to ~tildes, are they automatically subscribed (implicitly or not) to both ~tildes.official and ~tildes.dev?
- If someone only wants to see the content from ~tildes and ~tildes.official, what sort of process should they need to go through to make that happen?
- How might these ideas work once the hierarchy gets much larger (for example, imagine a ~games with hundreds of subgroups inside many branches)?
Any input about the topic is appreciated—try not to worry too much about whether a plan is "perfect", we can always adjust it as the hierarchy actually starts becoming more extensive.