14

I'm a committer for the Pets proposal.

It went to the private beta phase sometime in the last 12 hours, but yet to have been invited. When I visit https://pets.stackexchange.com/ I get the standard "To log in, you must have commited to the Area 51 site proposal and received the invitation email." message.

However, when I navigate to the Pets site via the Android app, I'm able to view the site in it's entirety (questions, answers and comments). When I attempt to post, I get a message saying my user token isn't allowed to take action on this site.

Same behavior is observed when using the iOS app.

6

The Android app leverages the Stack Exchange API, which exposes private beta site data. This is currently , so the behaviour is expected.

  • I was just looking at the API to prove this exact thought thanks to the question was just asked. Thanks for the insight Tim! – Steven V Jan 7 '14 at 20:29
  • 3
    A note that 'private' betas are only as 'private' as they must be to simply afford the group that founded the proposal enough time to get the various beta things worked out, and get a nice selection of questions written. There's nothing fundamentally seekrit going on, as everything they're doing will be open to the public in a week anyway. Given that, I doubt that there's any real reason or motivation to ever change this for sites that will eventually face the public. It just gives them time to get organized without the network rushing in, by no means a lock & key :) – Tim Post Jan 8 '14 at 9:09
5

Remember that a private beta is only private insofar as it allows the core community behind a new site a little bit of time to get things set up without distraction. This small, initial group of enthusiasts need to come together and get some things worked out pretty quickly:

  • What is on, or off topic?
  • How are we going to tag things?

Of all the essential questions, those are probably the most essential during the private beta. If you don't get that right in the first week, it can be very difficult to fix later.

The good thing is this naturally happens as they begin asking and answering questions; if you bring too many people into these sorts of discussions, they tend to take much longer than they otherwise would. You need to have a degree of long term investment in the site in order to actively participate during the initial construction.

There's no reason why the rest of the world can't use the API to watch this happening, in fact some users have been known to find questions that they can really nail and begin composing answers offline in anticipation of the public beta.

Some private betas could probably have gone a little better if in fact they were just a little more open. You get cases where some proposals just take quite a while to reach this stage, where a respectable chunk of users that had once committed just lost interest along the way. There's also the case of folks not actively following Area 51 and missing the opportunity to commit to something that they're really passionate about.

While our often alluded "Area 52" should address the root causes of such phenomena, it also needs to have facilities so that those who are really interested in getting into a site early can do so, even if they unfortunately missed the metaphorical boat. We're fixing that to a degree in the current Area 51 model.

However, as I commented briefly below Tim's delightfully laconic answer, this behavior is very much by design. We didn't design the API to be able to be used as a spyglass into private betas, but we're happy that it does this. There's really just no reason to lock them down more than they are, and many signs indicating that opening them up a bit more would probably be quite beneficial.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .