Skip to Content
7-14-2008 @ 11:11AM
Personally, I find it a little odd that this guy grabbed the recipe from the Public tab, when he clearly implies, in his e-mail, that he was not used to seeing such things happen. That should have been the first red flag: "Wait ... This never happens. Why is this the first time they've put something this valuable in the Public area?"I think he could have definitely asked one of the Officers first.
7-14-2008 @ 11:24AM
I don't see that implication at all. As written, it's pretty straightforward: someone accidentally puts the recipe in the public tab instead of the private tab, Our Hero sees the recipe in the public tab and learns it, and someone else says "wait, that wasn't supposed to be there" and kicks Our Hero out for "stealing" it. There's no indication that the emailer saw anything out of the ordinary about the recipe being available, until he learned after the fact that it wasn't supposed to be.However, I do agree that there's more to this story than has been presented in the email. It's simply not rational to kick someone from your guild *just* for the reasons stated. Either someone in the guild leadership is massively overreacting, or Our Hero is leaving out significant chunks of the story.
7-14-2008 @ 11:50AM
"As written, it's pretty straightforward: someone accidentally puts the recipe in the public tab instead of the private tab, Our Hero sees the recipe in the public tab and learns it, and someone else says "wait, that wasn't supposed to be there" and kicks Our Hero out for "stealing" it."Maybe I was reading too much into it ... ? For some reason I got the impression that it wasn't typical for presumably high-level recipes to be stuck in the GB's Public tab, so I figured it would have been more tactful for "Our Hero" (haha, nice word choice) to ask first. Then the problem could have been fixed even sooner.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.