On Dec 18, 2007 3:45 PM, Karl Kuehn <email@hidden> wrote:
> First off a small rant:
> Normally I don't care about top or bottom posting as long as it is
> understandable. I strongly prefer people properly trim out the
> unneeded sections of the text rather than simply creating a never
> ending email. Now if you are top-posting you better have a narrative
> text that allows people to jump in to the conversation cold (you have
> to have at least a trivial introduction in your first sentence). Your
> post spectacularly fails on all counts, and is exactly why the "no top
> posting trolls" have gotten that way.
>
> Without skipping to the bottom and reading the whole post series to
> decipher what you were talking about there was no chance that I could
> guess what you were talking about. In fact even reading all of that it
> was difficult to guess what you were talking about. All of my English
> teachers along the way would have failed you for that one. And then my
> 3rd grade teacher would have also given you a bad mark if you had
> written that line in her class for not being mature enough (for a 3rd
> grader).
Normally I don't make the effort on a one-liner, because they tend not
to make sense unless one has read and followed the entire post.
You'll notice that I have made special accommodation for you this time
around, though since you only addressed this message to me, you surely
couldn't be confused about the topic of conversation. I have taken
the liberty of CCing the list, since you obviously intended to address
a wider audience.
As to immaturity, it was a comment in kind from someone who is at his
limit with this inane post bouncing around his inbox. Your comments
about my English skills are unwarranted. You'll note the lack of jabs
about third-graders' competency with the Reply to All button.
> Now for the real content:
> Is there really anything that gets put into /Library/Caches that is
> not general information? I do ask this as a serious question. Looking
> at my system there is nothing there that I can think would require
> reporting from a privacy standpoint if it were compromised. It is all
> plugin data, an nothing from QuickLook is there, and that is the only
> one that I can think might expose private data. Can anyone come up
> with an example where this would require reporting?
Anything may wind up in any Library cache, which is why it's chmod
01777. Xcode has put its precompiled headers there in a directory
owned by me, instead of just putting it in ~/Library/Caches. If I put
trade secrets, passwords or other sensitive data in header files, I'd
be very concerned.
--Kyle Sluder
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
