It's a bit of a Catch-22. Work around it by:
Make a app (or script) post for your app (or script).
Also tag it with placeholder.
And put "PLACEHOLDER -" at the beginning of the title.
Also, indicate in the post text that the app is not yet ready for prime time.
This has already been done a few times, for example:
"Chatdump - a site monitor (placeholder)"...
The \r\n issue was solved when I changed to a POST request.
But, since I was retagging questions (didn't really need to change the body, just resend it), I ended up using the body_markdown, encoded with HTMLParser.HTMLParser().unescape()
body_markdown = str(HTMLParser.HTMLParser().unescape(question_data['items']['body_markdown']))
And then sending it ...
You're abusing a browser action button. If you want to have an option page, just define it in your manifest as an option page. What you have now is an option page hidden behind a browser action button... :S
Try updating the css live. Not sure how your code works, but it makes it far easier to understand what various features do and if you're properly saving ...
I've written a simple script for this, called NSFW (because it shows content that is Not Suitable For Work). It will only work if you have 10k reputation (2k on beta sites); otherwise, you probably won't see the post anyway. The link to the revision history will be added to the 'post menu' with the share, edit and flag links.
You can install it here (...
Yeah, that's annoying and a problem with text areas throughout the interwebz.
So, I went ahead and banged out a script for this; Merry Christmas!
To install, click here (SE WMD scrollbar killer, install at GitHub).
To preview the source, click here (SE WMD scrollbar killer, preview at GitHub).
This script expands away the vertical scrollbar for all open ...
The stack exchange API officially does not support posting questions or answers, but it does allow posting comments.
So you can install the StackX app and use it to comment on posts.
There is also an Official Android App in alpha development. It looks like they are still taking sign-ups for guinea pigs volunteers. ;)
This was an old, old bug: a bit of logic assumes that revisions can be ordered by their creation date. This is not true for Improved edits, as both the suggested edit and subsequent Improvement share the same date... So you'd get the wrong markdown.
I've resolved this by falling back on ID to order, which is how we do it most other places. This may not ...
Does it work on answers at all?
Here's a newer locked answer. Yet, it doesn't have a locked_date either.
It's not a filter issue.
Nor is it fixed in version 2.3 (yet).
Also, additional bug feature-request:
The post object should also return a locked_date.
A sample locked question does return a locked_date as expected.
last_editor will be missing (empty) from the results when the last editor is a deleted user. This deleted user does not have to be the owner, or original poster, of a given question or answer.
For example, see this answer -- which looks like this in the API:
The script is working except in the Suggested Edits review queue, since the .subheader h2:first does not exist for that queue.
Can you please add some workaround for the Suggested Edits review queue?