Problem with posting images

[The Jamie Star Scenario]

For some reason the xxx in my site directory doesn't want to work here, like why is that? See when I post an image instead of getting:

http://theglassprison.net/obey/xxx/signatures/old-navy-TJSS-edit.gif

I get:

http://theglassprison.net/obey/x</userdefined>xx/signatures/old-navy-TJSS-edit.gif

once it is posted, in the images codes of course. What is wrong? :(

Man, it even puts space in the normal link without asking :/

[Flying Mullet]

It's because it's putting a &lt;/userdefined> inside your x</userdefined>xx(like this "x&lt;/userdefined>xx") because it thinks you're linking to a p</userdefined>orn picture and this disables the image from working.

[eestlinc]

*whistle*

I'll let some of the other staff members address this one.

[MecaKane]

Is that why that teen rape thread has that /userdefined> after the T?
That's RETARDED.

[eestlinc]

yes, "we" decided to stick useless html tags into certain porn hot words because people post so much porn at eoff. it doesn't effect text but makes any image or url with a filtered word useless.

[Meat Puppet]

s<</>/>ex

[Yamaneko]

Is it a Vin Diesel fan site?

[Old Manus]

I'm sorry guys for posting porn 134435 times, really.

[MecaKane]

What are the words?
What if someone's photobucket or something account is hentaifreak, or yuna4teen, or whatever, dispite only having holsome content.
Isn't this why you dodn't disable html, because it would cause more problems than the rear instance of some douche crashing your browser?

[Loony BoB]

No need to debate yet, we're discussing it in staff and will sort it out if need be. :p Whatever happens, you'll probably know soon enough.

[MecaKane]

BoB did you come back because of this? >:O

But it's already done. :confused:

[Loony BoB]

What's already done? And no, I made up my mind I'd finish my break earlier today.

[Yamaneko]

Yes, we are currently discussing the matter in staff...

...suckers!

[The Jamie Star Scenario]

:eek: It works again, thank you :)

[Big D]

The point was, originally, to make it a whole lot harder for anyone to post porn - whether it's random nuisance accounts, or actual members who want to get themselves ban. After criscofist's recent porn spam rampage, I realised you could block a lot of inappropriate material by censoring a few key porn-related words - the sorts of things you might find in a porn site's URL. By using an invisible edit - putting a "<</>/>" into the word - the affect should've been largely unnoticeable, except when someone was trying to link to a site with that word in its name. Linking problems would be overcome by asking people to copy/paste; or, in the case of images, using tinyurl.com to generate an alternative.
There were two main considerations here:
(1) thwarting time-wasters who think they're awesome because they know how to post porn on MBs

and

(2) Protecting the interests of people who could potentially get disciplined for accessing porn on a work/school computer, even accidentally.

Basically, I figured there wouldn't be many serious side-effects to this filter, since it'd have minimal effect on normal conversation, and any problems with hyperlinks could be overcome by copy/pasting or tinyURLing.
Evidently, I was wrong.

[Azure Chrysanthemum]

I still think its a good idea, but we probably need to just use a few, key words. For example, "anal" was censored, and suddenly my signature was completely screwed up. We just didn't take that into account, I suppose. We had an initial list of many words, but some are roots of others.

In retrospect, we probably should have thought of the Yo<img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">aka Amano case a bit more and thought about what words have roots that might prove problematic.

[Big D]

In retrospect, we probably should have thought of the Yo<img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">aka Amano case a bit more and thought about what words have roots that might prove problematic.Oh, it was plain that there'd always be some words that'd get affected. However, unlike Yo<img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">aka, there'd be no visisble effects except in URLs, either linking to images or to sites. While there are plenty of legitimate reasons for lining to a site with "gay" somewhere in the URL, that particular filter would've blocked every single image posted during the recent spam session.
It seems kind of silly to censor out the word "<img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">" in a way that messes up what people write on screen, while not using a 'porn keyword' filter, which arguably has a more important job and causes less disruption to legitimate posts.

[-N-]

Yosh</>itaka Amano sucks anyways.

[Del Murder]

Let's get rid of the censor on s h i t then.

[Old Manus]

STOP SWEARING EVERYBODY

[Big D]

It'd be good if there was some way to exclude particular things from the filter - so that it'd take care of "<img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">", but leave "Yosh</i>itaka" alone. Similarly, it could be tweaked to remove only URLs with porn keywords, without touching valid terms like 'canal' or 'sexist'.

[Sepho]

You could put the word in curly braces, i.e. {poop}, to only censor on an exact match, but then it would still fully display words like <img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">face, <img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">ty, <img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">head etc. You could add those individually, but those tricksters will always find some creative suffix to add to the end.

I'm not sure at what point during the pages execution the censoring takes place, but maybe a replacement variable would accomodate for Yos<i></i>hitaka Amano?

I test.

EDIT:

<a href="http://www.omgmyhat.com/forums/showpost.php?p=2150&postcount=1">Hmm</a>
Yeah, the replacement variables come into effect dynamically each time the page loads, so setting up a replacement variable to replace all the img src=xxx etc. with the plain text would sort of be a fix. You'd have to add each exception as its own replacement variable, and all the censored stuff would still be stored in the db, and you'd still see it when editing/quoting posts and all that, but it would display the word "Yos<i></i>hitaka Amano" on showthread/showpost pages. Not sure if someone wants to bother with it, since it isn't a real fix and only serves to eliminate the need for users to do the fix themselves.
:eyebrow: :hourglas:

[Loony BoB]

Personally, I think people use Yo<img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">aka more often in Feedback than in the music forum, so it's not really a solid reason to make changes. People can come up with all sorts of words that are rarely used.

[Drift]

my sig doesnt come up and it doesnt even have porn related words in it ;(

[Loony BoB]

I see your sig fine, DC.

[Sepho]

I'm seeing a single, 500x200 image :/

[MecaKane]

After seeing his first bit of crazy porn posting didn't work, it wouldn't take much for our devious villian to start linking from 4chan, or someplace similar, uploading attachments, or worse yet, deleting that post and saving up a library of gay animal porn on some happy-do-lala free webspace. Think of the children! :cry:

[eestlinc]

Personally, I think people use Yo<img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif"><img src="/xxx.gif">aka more often in Feedback than in the music forum, so it's not really a solid reason to make changes. People can come up with all sorts of words that are rarely used.
Probably because he is an artist, not a musician.

It should be noted that I got "kitty" added to the filter during its short life.

[Loony BoB]

Art, music, same difference.

[Big D]

After seeing his first bit of crazy porn posting didn't work, it wouldn't take much for our devious villian to start linking from 4chan, or someplace similar, uploading attachments, or worse yet, deleting that post and saving up a library of gay animal porn on some happy-do-lala free webspace. Think of the children! :cry:Yeah, but that'd at least give us more of a chance to ban and delete before he/she/it realised what was up, and changed strategy. No system is ever foolproof, since there's always a new model of fool waiting to be unleashed, but it'd have helped, in my opinion.