All boards as it were too. I started a thread on /c/ posting girls in wedding dresses and after about an hour and 25-30 pictures I post one that gets me banned for a week for posting an image with malicious code. Almost all the pictures I get come from /c/ itself so to post something with malicious code on the very image board I got it from confuses me. I haven't seen a wedding thread there in about 5 months so I think the picture in question was 5-8 months old.
So how do I prevent this from happening again? To be banned posting old images means that I won't be able to post anything again for fear of receiving the same ban. Unless I know how to tell whether a 6 month old picture contains malicious code.
Also while I'm gone would anyone be kind enough to let them know on that thread that I've been banned? I promised that I would post pictures of Mint when I'm done and that won't happen now.
don't bother. post on iichan henceforth.
well that seems rather harsh. I'm wondering if it's fallout from the pictures that were causing all the trouble over the last few days. I have Avira which when I first clicked on one of those said it contained an html code and I probably didn't want to download it so I didn't.
I doubt that anything from that was the problem though all I'm asking is some way of knowing which one of my old files would get me banned. If there is now way of knowing then a lot of innocent people will be banned for no reason and you may be right.
lol on myself, I meant no instead of now, sorry about the misspelling.
Which particular image got you banned? Can you upload it somewhere for me to see?
I'll find the pattern that 4chan recognizes and I'll come up with some shell command to list all the images that have such pattern, so you can just delete them if you want.
Sure, uh, guess I can upload it to photobucket and link it here.
I'm 95% certain this is the picture, it looks too large for an ordinary .jpg and it's the last one I tried uploading.
it sure chugged away on photobucket to upload it, maybe it didn't get altered in transit but I dunno how that site does it's thing.
http://i33.photobucket.com/albums/d65/Tekrelious/1145695768524.jpg
nope, it altered it, mine is 420k, this one came out 117k. I don't know where else I can try uploading something like this. I'm relatively low on the computer intelligence list.
Try a file host instead of an image host. Quickest and easiest would probably be to zip it and stick it on rapidshare or the like.
I'm in the same boat here.
Ban screen: http://i11.photobucket.com/albums/a171/ivegotgas/Allboardban.png
Image I posted(exactly the same size as on my HD):
http://i11.photobucket.com/albums/a171/ivegotgas/CossackondutyJzefBrandt.jpg
I'm assuming they're just banning base on the images now? That's bullshit, because I know the file I was uploading is safe.
It took them 5 days to review my ban and uphold it. No further explanation.
Here's the picture uploaded to mediafire.
http://www.mediafire.com/?sharekey=3d7f0951d68bb814d2db6fb9a8902bda
That's your whole library of files. But yeah, it looks like it's going to take a while for them to get to my appeal.
Is it really? Wow my mistake, I'll try to weed out the one in question.
http://www.mediafire.com/file/m47h4zlnczk/1145695768524.jpg
Good thing I don't give much care to what's on mediafire. Lol.
It just happened to me too...
Same ban screen as well
I'm really clueless about all this.
What should I do?
I dunno man, they're hitting a lot of innocent people by the look of it. They upheld my ban without explanation so I wouldn't expect leniency. Should be lifted sometime today.
I'm guessing it's fallout from last week's, lol rename this file and run it garbage. They tried protecting their server by banning anyone who posts something questionable is my guess.
Ban appeal was denied without explanation today...
>>9
Picture has a bit of (harmless) HTML at the end. That probably triggered it.
Your best bet is to get on #4chan@rizon and explain it to them. I don't know who coded this, I'm guessing Coda or MrVacBob. You might want to inform them as well.
What's the HTML code do if I can ask and why would someone put HTML into a picture?
>>17
It does nothing, it just seems like the end of a web page. Some screw up on the part of whatever gallery software they were using or something.
<CENTER>
<P><A HREF="http://banery.wolfnet.pl/skok.asp"><img src="http://banery.wolfnet.pl/obrazek.asp?3"
width=400 height=50 border=0 alt="Hosted by WolfNet http://www.wolfnet.wd.com.pl/"></A></P>
<P><A HREF="http://www.wolfnet.wd.com.pl/"><img src="http://www.wolfnet.wd.com.pl/Baner.jpg"
width=400 height=50 border=0 alt="Wolfnet http://www.wolfnet.wd.com.pl/"></A></P>
</CENTER>
</BODY>
</HTML>>>18
Ohh... that explains that. I just checked two of my own pics that tripped the detector, and both have Minitokyo html at the end. Dang, guess that means no Minitokyo images are postable anymore.
On the plus side, one of those false alarms happened the other day, and I wasn't autobanned. Maybe they've lightened up.
Interestingly, someone else posted a "clean" version of the picture in that thread, and I was also able to find it on Gelbooru. The actual image data is identical: Saving the "clean" and "infected" images to png produce identical files according to md5sum.
Also, manually removing the trailing html in a text editor changes the "infected" image into a "clean" one, with the md5sum matching the "clean" version. So that's how to fix it.
>guess that means no Minitokyo images are postable anymore.
Sure you can, you just need to strip out the html at the end with a hex editor. I'm surprised no one has written a program to do it yet...
how to make a "clean" pic. printscreen the pic, paste and crop.
>>21
more like how to make a crappy pixilated pic.
I'll bet you think printscreen means getting out a camera and taking a picture of the monitor ...then having it developed and trying to load the image on the computer by putting it in the CD tray.
http://compy4.servehttp.com/my%20pictures/+meeeenotagain.png
the 4chan mods are a bunch of fags!
>>23 thinks running things through a lossy compression algorithm multiple times is a good idea.
>>23 can see the fnords
>>23 can see that honking antelope.
