getting security groups right
When I joined LJ there were three levels of publicity for posts: public, friends-only, and private. Years later they introduced filters, so you could group your friends into buckets for both reading and access. Either you could not at the time put a post in multiple filters or I did not know that you could, so I ended up creating some hierarchical security filters. For example, some posts would be restricted to the "best buddies" filter, others to the "know pretty well" filter, and others to the "know" filter. A "best buddy" was therefore in all three groups. This is a royal pain to administer on LJ (you can't put a group in a group), and I've been moving to another model now that I can. I may never get around to correcting the older entries, though.
I would like to not have such a mess with G+. I note that G+ (unlike LJ) tells you right there on a person's page what group (er, circle) you've put that person in. I haven't put anybody in multiples, but I assume that if I did they would all show up.
So I'm thinking that what I want to do is to put everybody in exactly one security filter, and then make posts visible to all applicable filters. Instead of having a person in multiple filters, I would have a post in multiple filters. Does this seem right to y'all? Are there other factors I should be thinking about?
On LJ I post almost everything publicly, but it looks like G+, with its ability to make posts to specific individuals, is likely to involve more non-public posting. I can't tell yet. By the time I know, it will be too late to go back and fix my circles if I get this wrong. So I'd like to hear people's thoughts now, while everybody is in one big "acqaintances" bucket awaiting sorting.
Note that I am not talking about reading filters here, and I don't intend to mingle them. I might trust somebody deeply but not want to give his 20 posts per day high priority, y'know? Reading filters can help manage that.
Edit: To clarify, my current thinking is to put each person in exactly one security filter and in one or more reading filters.
no subject
no subject