oneandonly's Shouts
-
-
-
-
Nice one on getting that guy admit who he was on FA. Just another reason not to touch that place with a ten foot pole. :P
-
I won't lie to you, I did it solely because willamca was playing his little teasing game. Hopefully he will learn not to taunt those that are obviously out of his league. Now his plan is kaput.
-
Hey, no matter the reasoning, it needed to be done, either way for some reason all the comments are gone (Who would've guessed). I went ahead and saved a backup of the page with the comments though:
https://aldude999.net/cache/starrykitten.html
-
-
-
-
-
-
-
-
-
-
-
-
-
Hint: For your note-sending function, a private message can be sent to multiple users at once by separating the recipient usernames with semicolons (this was better documented in a previous version of the UI, but I seem to have failed to mention it on the notes page, whoops).
-
-
-
Code and documentation added: http://aldude999.net/wiki/index.php?title=WeasylAPI.net\#EasyRecipient
I kept it so that recipients are still one string. It makes a mess of code If i try to add 9 optional variables for multiple recipients I figure API users can just string the recipients together. The new feature "EasyRecipients" Isn't really easier, but it may feel a little more natural to people who use services such as Gmail often.Something completely non-related, this is happening on my phone: http://www.aldude999.net/images/screenshot-1337829807584.png
It's most likely a problem with the phone rendering transparencies, but I'm not sure.
-
-
-
-
Heh, just glad I can finally work on my code now. NONCE has been screwing me over multiple times, from registration, to coding, but I'm getting the hang of it. What I thought previously with the notes was NONCE, turned out to be a problem with textboxes on my end. I had the wrong text boxes sending data to the wrong string. Recipient was sending the subject, the subject was sending the recipient, etc.
POST turned out to look like this:
nonce=yI4crz7PmzDSrib8MBKs&replyid=0&returnto=&title=oneandonly&recipients=My subject goes here&content=My+message+goes+here
Caused a nice 420 error I believe lol.-
Oh yeah I didn't think about `nonce` (which is aptly misnamed) giving you trouble; the newer version of code that we're rolling out with the actual UI uses a slightly different method of generating a field called `token` based on hash(sessionid + some_secret_key) rather than a pseudorandom string, but you won't have to worry about that for a bit.
-
Interesting. Now that will that (sessionid + some_secret_key) be generated server side right? Or is the client going to have to do that?
-
It is calculated server-size both times both during page rendering and form processing. The result value will be available to the client inasmuch as you can pull it out of <input name="token" ... value="blah"> but given a particular user the value will not be predictable (which is the entire point).
-
-
-
Link
RayFloret