TheNextBigWriter Premium → Not Authorized
Pages 1
Could a small change be made to the interface that would let us know just WHAT group a person posted to instead of giving us a somewhat rude "Not Authorized"? On the very page that tells us this, we could at least be told what group holds the post.
~Tom
Hmm... If the author doesn't want me to read it, I don't give a crap about what group he/she actually posted the "Not Authorized" material. But that's just me. Take care. Vern
Well, that's certainly something to think about, Vern. And I do agree. Then perhaps the favor I should be asking is to not get notification emails for a posting that I cannot read. I have connected to this person, so I am sure that's why I received the email, but if I am not in the group it was posted to, then I shouldn't have gotten it. A rather odd dilemma, I guess.
~Tom
Could a small change be made to the interface that would let us know just WHAT group a person posted to instead of giving us a somewhat rude "Not Authorized"? On the very page that tells us this, we could at least be told what group holds the post.
~Tom
There's a 'Not Authorized' because you are blocked, and there's a 'Not Authorized' because you must be in the group in which the work is published, and one has to look at the direct listing to see what that might be, and sometimes the author has removed the work form all groups, and therefore (I think) access can only be for the author's connected users, but I think there is also an issue of old works carried into the new TNBW. The plain and simple 'Not Authorized' means you're blocked, but others give more information but never "you must join this or that group" to read.
I am definitely not being blocked by this person. I can read other offerings by the same person, but those also state that the "Internet" was one of the groups (widest coverage). The one I was notified for was in a specific group, BUT it does not tell me which group. MY suggestion is either stop the email from getting to me because I am not in that group, or let me know which group it is in because I might want to join it.
I do agree that a flat statement of "Not Authorized" can cover a multitude of reasons.
~Tom
Tom, would it not be easier to contact the author and simply ask which group it was posted to? It sounds like you have a connection\understanding\relationship going and this wouldn't be out of line. Although I agree that receiving emails of work we cannot access doesn't make a lot of sense either.
That is correct, Janet. I have since contacted the author and know what group it was posted in. This person also agrees that sending an email to someone who can't read it is pointless.
~Tom
I just received another email notification that led me to "Not Authorized".
What is the point of emailing notification that I can't see? Can't the mailing daemon be taught to check the membership of a given forum before sending out notifications? Here is what the email contains:
"bimmy has created new topic 'How it feels to be writing a novel. ...' in forum to which you are subscribed."
Note the phrase "...to which you are subscribed." Doesn't that mean I should be authorized to see the forum post?
~Tom
Tom, I received that error message as well. I think it's due to the author of the post deleting it after the emails have gone out. That was my assumption.
I deleted that because I couldn't get the link to worn I posted in the topic. Sorry!
Bimmy
Ah so. In that case, perhaps the message should read "post deleted" instead of "not Authorized". Even a "not Found" would point me in the right direction. I'll keep this in mind next time.
Minor kerfuffle.
~Tom
And another one:
dagnee has created new topic 'Washington Post Article part 2' in forum to which you are subscribed.
"Not Authorized".
~Tom
I got this "NOT AUTHORIZED"... and it hurt. I thought dagnee and I had kissed and made up years ago. When I was writing code... a switch statement allows a variable to be tested for equality against a list of values. In this case it evaluated it to a generic statement after all other options failed.
Switch statements are so passe. Nowadays, youngins get lost without an exception handler. Back in the day, the only exception handler was: trace bpt trap (core dump). What was even more fun was when C++ first came out. It was a simple preprocessor that produced C code. If you wanted to debug that core dump, you needed to know the C code that C++ was generating. Ah, the memories.
Pages 1
TheNextBigWriter Premium → Not Authorized
