next »

[m1t0s1s]

perkiset, did you just hit your own forum with spam? What was that harkening elegance post all abovt?

[perkiset]

perkiset, did you just hit your own forum with spam? What was that harkening elegance post all abovt?

Interesting that you read that... I created a post and then deleted it - I was testing the SMF Forum software for it's encoding of double and single quotes... (which it did expertly) and now I am walking through the code to see what it did. But I deleted the post almost as quickly as I created it... where are you seeing that?

Thanks!
/p

[m1t0s1s]

perkiset, did you just hit your own forum with spam? What was that harkening elegance post all abovt?

Interesting that you read that... I created a post and then deleted it - I was testing the SMF Forum software for it's encoding of double and single quotes... (which it did expertly) and now I am walking through the code to see what it did. But I deleted the post almost as quickly as I created it... where are you seeing that?

Thanks!
/p

It was from the smf notification, archived forever, in gmail. Speaking of which, I just found the blog of the creator of gmail, Paul Buchheit

[drdoomgod]

hey, i just thought a bit about your cross domain rpc and what to do with it...

as the client makes the calls, isnt it possible to bypass cooki authentification for, say a bookmarking site (digg style)

like having the user executing a "digg.com?bookmark=mynicepage.com" ?

i guess this is the direction the imortal promoter goes, or am i completely wrong? im just starting with the js stuff, so im not sure

thx, drdoomgod

[vsloathe]

It is similar to the direction Immortal Promoter goes in, but not entirely the same.

We would require some reflective XSS in order to use this cross-domain without the other server's express permission. Immortal Promoter requires no such trickery for what it does.

[kurdt]

Hmm, I'm not a javascript expert so this might be a stupid question but any idea why I'm getting this error from Firebug:
target[0] is undefined
target[0].appendChild(newNode);

[perkiset]

Nope... but the error means that it's pointing to something (target, which I use by default as a node pointer) or more correctly, an array meaning that probably the lines above that were something like "target = getElementsByTagName('DIV')" or some such, and it expected something at element 0. Since this hasn't been reported before, I'd assume that it's something to do with integration into your code.

You should get your arms around some JS if you're going to use that... it's a rather sophisticated class and method and you can hurt yourself if you don't do things correctly.

[kurdt]

Actually I found out the reason why it did that.. I was running it inside head tag. I usually do all my javascript inside head so it didn't occur to me that this might require that you run it in body

[perkiset]

heh... that'd do it. Glad you got it sorted.

/p