Twitter's version of it, you might say, is putting the whole world in one flat namespace.
Naturally (as per Tobler's law), we care more about our direct environment, but Twitter never created a view like finger where you could only see the direct members of your own lab, all content is external/public. I think that's because Twitter wasn't planned, but happened as an accidental side project. A more careful design would have created a multi-tiered visibility level with ways to choose what visibility is best for a message (default: local).
It would be cool to create .plan files dynamically using content pulled from social media status updates for people who do not maintain their own .plan.
Twitter's version of it, you might say, is putting the whole world in one flat namespace.
Naturally (as per Tobler's law), we care more about our direct environment, but Twitter never created a view like finger where you could only see the direct members of your own lab, all content is external/public. I think that's because Twitter wasn't planned, but happened as an accidental side project. A more careful design would have created a multi-tiered visibility level with ways to choose what visibility is best for a message (default: local).
It would be cool to create .plan files dynamically using content pulled from social media status updates for people who do not maintain their own .plan.
You can use the "Lists" feature to zero in on, for example, just your team.