Why am I not allowed to post?

Possibility. Did you write too long a title for the question? There could be a maximum character level for that. Otherwise I know of no length restrictions though it clearly has to be reasonable. Here are the two Apple documents most likely to answer you.

This one mentions violations of the terms of use and it is most ambiguous. But there again, it's Apples site so they can interpret the rules as they like.

http://store.apple.com/uk/help/questions_and_answers

And this one goes more deeply into the matter. Lots of reading.

http://store.apple.com/uk/browse/community/terms_of_use

An additional thought since, if you have a copy, try to post it again ... or at least review it after studying what may be the violation(s). Violations is an evocative word and the fault may lie in something quite innocuous.

7 1,

you know what happened, mi amigo... long post = long time (>30mins) = loginTimeout

👿

ÇÇÇ

I hadn't thought of that, CCC. You may be onto something there, though it would have to be a long post indeed. I still have to go with an unintentional violation.

'Off topic' Now, you watch what you say today. Don't want to lose your company as abruptly as yesterday. 👿

Steve,

You have fallen victim to a flaw in thinking concerning Apple's proactive approach to account security - and one thing they seem to have overlooked in fixing the problem (Ill explain what that one thing is in a bit**)

A period of inactivity (I will explain later what 'activity' means*) will result in one being "Timed Out" from being logged in - Without Fanfare (notice). The TimeOutLength is stored in a cookie and is of ±30 minutes in duration.

* Activity is defined as:

1. navigating using HTML hyperlinks - such as
   1. clicking on a thread title
   2. clicking on an icon/picture/tab that has a URL as a 'target'
   3. Reloading a page***
   4. you can always tell what is a hyperlink by hovering' your cursor over it and it will display in the 'progress' bar of your browser
2. NOT a JavaScript 'link' that invokes a javascript function, such as
   1. Reply
   2. Like
   3. This answered my question
   4. This answer helped
   5. Reply to original post
   6. etc. etc. - these all will show " JavaScript:void(0) " onHover
3. Having a REPLY compose window open (**)

** Overlooked fix for the initial flaw = A NEW question compose pane apparently does not have the same fix applied that a Reply compose pane does, so you experienced that timeout and were served up the "Not allowed to post" error message

*** For quite some time, the only solution to NOT being timed out was activity by clicking or reloading a page. An AutoReloader add-on for the browser solved it in Safari until Yosemite and continues to work well in Firefox. I will provide links to both Safari and FF add-ons if you are here a lot and would benefit from one.

In the meantime, when composing a NEW question

1. do so in a text editor then copy/paste into the new compose pane
2. copy the entirety of your composition before you submit it so you can simulate having done #1 if it fails

Hope this helps

ÇÇÇ

tt2 found that an open REPLY pane on a "throw away" thread as he puts it serves the serves function of resetting the cookie's timer (technically, the Expiration TimeStamp) after 20 minutes. I have tested this and it works. tt2 claims 'weeks' of continual logged in state - I read that as his Windows machine never sleeps!

best regardz

ÇÇÇ

Hi ççç

'Still off topic' Forgive me steve1000.

I'm very much hoping tt2 will be at the London meet up, and with luck he will teach me. Having said that, I find if you use a combination of Firefox and bookmarks you can keep an open thread for ages.

Your main message is far too complex for me but you will notice I have at least achieved your ççç this time. 😀 I'm now off to hunt down a capital version.

Regards, as ever.

Executive Summary

1. click on HTML links, not JavaScript links = reset timer to 30 minutes
2. leave a REPLY compose pane open(or compose in one) = reset timer in 20 minute increments
3. JavaScript:void(0) <- on cursor hover or click do NOT reset the timer
4. Reload a page, any page with Menu / Keyboard shortcut OR with AutoReloader browser add-on(user desired length) = reset timer to 30 minutes

ÇÇÇ = ⌥ alt Option + ⇧ Shift + "c>c>c"

This workflow gets around many problems with ASC.

( I knew there was a reason for keeping my tried and true method. ChitlinsCC, et. al. Ever here the phrase: A fix from Jive is a contradiction in terms? ChitlinsCC posts are great! But in this instance, I think the scenario below is more robust. )

Here is my ASC work flow...

1) I login.

2) Start an auto reloader.

Unless you do something every thirty minutes you get logged out. The forum software waits to tell you this as long as it can to keep you in suspense ;-) .

I use Firefox and ReloadEvery.
https://addons.mozilla.org/en-US/firefox/addon/reloadevery/

You need to pick a page that will reload over time without stalling out. It's ASC. I've found my profile display the best to use. I get my Profile page after some logins. It's ASC. Change rccharles to your apple id.
https://discussions.apple.com/profile/rccharles?view=discussions

3) I open another window to do my normal ASC browsing.

4) I have a FireFox bookmark to goto the discussions that I have participated in. I've modified it to add on the content stuff.

turingtest2 recommends. Change rccharles to your apple id:

https://discussions.apple.com/profile/rccharles/content?filterID=participated~obj ecttype~objecttype%5Bthread%5D

5) Use turingtest2's generated links with the /content suffix as browser bookmark to the ASC discussions:

Site map of Communities and Categories

https://discussions.apple.com/docs/DOC-2463

6) I run with Hiroto's modification to user content. This is the only way these forums are readable for me. How to adjust the format and layout of ASC Web Pages:

https://discussions.apple.com/docs/DOC-7501

7) Read and answer my old posts. I kind of memorize the time I last posted. ( It's way bad that apple eliminated the last poster to a thread. )

8) I use tabbed browsering. From a list of discussions, hold down the command key then click on the link. You get two tabs this way. The original window will keep where you have been.

What is sleep? 😝

tt2

that thing that people who are not self-employed do at night that supposedly refreshes them to do more-better work the next day😎<-not sunglasses but eye shades to blot out the light when we crash from our Mountain Dew buzz ÇÇÇ

It's impossible to know why you couldn't post. The number one reason is you were timed out. Beyond that it was most likely one of the many glitches that haunt the Forum. First, refresh the page, then try again later, last try another browser.

Steve1000 wrote:

SNIP ... a lively conversation. I didn't write too much, didn't take 30 minutes, it just didn't post. I am assuming it was a bug that died shortly after that attempt.

Steve

lively indeed! It is not my intention to beat a dead horse, but your reply quoted prompts questions.

<30 minutes = no timeout

"... it just didn't post. ..." -- what exactly do you mean by that statement? It didn't appear in the thread - with no error message of any sort? Error message? If the former, that would be a rare example indeed - the latter, not at all = happens all the time => your last statement is spot on.

Welcome to the shindig, mi amigo

ÇÇÇ