liv | (Reply)

From:

yes, what

liv said -- there's way, way too many potential for information leaks that way, not to mention that we'd then have to come up with a UI for "create this tag privately" when you typed a new tag into the update page, plus a UI for "turn this tag private" on the manage tags page, and both of those workflows are already very complex, and more options are bad UI -- not that options shouldn't be allowed, but there needs to be a really freakin' good reason for them.

basically, there's no way to manage "private tags" that doesn't lead to a UI clusterfuck, which leads to people creating things publicly that they didn't want public. it is much, much, MUCH easier for tags to inherit the security of the posts they're used on.

workaround for tagging public posts with a specific tag that you don't want others to know about: either tag with a nonsense term that you know what it means, or use a certain word or phrase inside the post and search your journal for it.