ok so i had deleted that post because the forum here distorted so much of it and deleted like 80% of it so you couldn’t even see what i was talking about.

I basically looked in to this for an hour or two last night ~delved far in to the workings of the text-to-image plugin and alot of rightclicking then inspecting the comment box and gallery to see what of iframes was touchable. also alot of messing with window.frames and such to see if i could get a hold on iframes and their contents housing things like the gallery.

let’s see if i can sum up what i learned.

I found somewhere we don’t have access to (i think it was while inspecting the iframe of the gallery) that marks created somewhere i couldn’t see were tallied and they added up to an image being nsfw. I may have been seeing the end result of inner workings of the server, where images are judged for nsfwness and if they are beyond a certain amount they get flagged as nsfw. It would make sense much of the nsfw calculating is behind the perchance main server where we can’t touch it so people are hardprevented from generatin ‘the bad stuff’, and this seems to be the case. Inspecting the gallery and looking at the iframe, here is what i was trying to bring to attention in my post originally but was magically cut out for no reason: every image in that iframe is programmatically generated BEFORE the page is written. It isn’t a page which does clever code and generates X number of images… The code for ‘generate image’ has been repeated X number of times programmatically to write the page and the page placed there for us to interact with. And these programmatically generated text chunks containing the variable: data-is-nsfw = false . What this means is it is somewhere on the server we can’t see, which is generating this page in real time, that has data of whether each image is nsfw or not.

It is also extremely hard to access and touch the inner contents of the iframe containing the gallery. I have not managed it yet, though it is also new territory for me and there may be simple things about iframe origins i do not know. I rarely have used iframes.

what other useful info is there, hmmm. so i got a hold on the iframe containing the gallery pretty easily and looked deep in to the windowmessages sent upon events from the server. But none of it allows touching the inner contents of the box holding the gallery, just the outside of the box.

All this implies it is actually REALLY EASY for the maker of perchance to do on their side since they would just add a button seeable by only the admin on each image… just have whatever is programmatically making the gallery page that gets iframed in have an additional button. then make a function on the server to toggle an image rating, which should be as simple as changing a variable false to true for the owner of the server but we cannot do from here. Then just have the button call the function. For us to do it it seems REALLY HARD to impossible through the existing Gallery as is. I have never, that I know of, seen nor met the perchance creator nor have any knowledge of how often they update nor how much they listen.

I could not find a way to A: get a useable reference to anything within the gallery iframe (which would allow finding the images and multiple paths to success)

and I could not find a way to hit any of the variables or do any of the authentication stuff to artificially manipulate gallery variables from afar. I tried looking at how the page that is the gallery within the iframe sends signals to the server, but my attempts to replicate the signals from another perchance site did not work. It may have to do with the server set up to only allow requests from certain paths and more likely may have to do with me not having the same variables as are available within the iframe.

I see your problem and if I think of anything I’ll let you know. From delving through for hours it looks like it’s behind walls but an easy fix for the one(s) with access behind the wall.