- ninky
That is the question. Whether it is nobler to be public and let anyone see what's up, or if some things are best left private.
Everytime we post something, we make a choice to share with the world or with a select few. On this community, are there times and situations that we need to keep things from the greater group? Or should everyone have an all access pass? Do you feel excluded when things are private? I invite discussion on privacy and publicity on this web community.
Is there any middle ground? Are some posts semi-private? What if the post is about ASU things that we what to discuss with only the ASU users? We might not want to the world to know about something.Â
I find this topic particularly interesting. Given the nature of our environment over at the Biodesign Institute, there's very little outside of general development banter we can comfortably offer publicly. That said, there is plenty to discuss in a general development context. When it comes to ASU particulars (such as WebAuth) I think it's fair to say much of these matters can also be discussed as an open topic. Yet when real systems design comes into the mix it becomes very easy to inadvertently let slip secure or potentially hazardous information.
On the whole I'd just love to see more discussion arise. In a general-development context there is so much agony we can spare each-other by pinging ideas and presenting/discussing issues. I find it energizing to share ideas and discuss the big picture at our university with other passionate designers/developers/hybrids. Thus far we've only really been able to engage in this way with John Howard's wonderful team at the library (not because anyone else has been unwilling or unwelcoming, our relationship with the library arose almost by accident).
My burning question (and one probably better-apt posed in a separate thread) is an ancient one: How do we form runnels of mutual-interest dialogue between the astounding number of code-wielding citizen-groups at ASU?