Problem with posting images
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/s...-TJSS-edit.gif
I get:
http://theglassprison.net/obey/xxx/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 :/
It's because it's putting a </userdefined> inside your xxx(like this "x</userdefined>xx") because it thinks you're linking to a porn picture and this disables the image from working.
Last edited by Flying Mullet; 10-21-2005 at 08:54 PM.
*whistle*
I'll let some of the other staff members address this one.
Is that why that teen rape thread has that /userdefined> after the T?
That's RETARDED.
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.
s</>ex
Is it a Vin Diesel fan site?
I'm sorry guys for posting porn 134435 times, really.
there was a picture here
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?
No need to debate yet, we're discussing it in staff and will sort it out if need be.Whatever happens, you'll probably know soon enough.
Bow before the mighty Javoo!
BoB did you come back because of this? >:O
But it's already done.
What's already done? And no, I made up my mind I'd finish my break earlier today.
Bow before the mighty Javoo!
Yes, we are currently discussing the matter in staff...
...suckers!
It works again, thank you
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.
Posting Permissions
