Register - Login
Views: 99386623
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-24-22 05:14:12 AM
Jul - The Cutting Room Floor - TCRF and...nudity New poll - New thread - New reply
Pages: 1 2 3 4 Next newer thread | Next older thread
ReiNi
さよなら＊へヴン
Level: 124


Posts: 4018/4444
EXP: 21750888
For next: 85713

Since: 07-21-07


Since last post: 6.7 years
Last activity: 3.3 years
Posted on 03-12-12 05:46:31 PM (last edited by Reshiram at 03-12-12 02:48 PM) Link | Quote
Possibility doesn't dictate what you can do.
Originally posted by BMF54123
That's a pretty lame solution, considering GIFs can only have 256 colors, and most NSFW stuff tends to exceed that. And what about grownups who want to view the content immediately?

Not to mention it defeats the point of hiding it anyway if it will get displayed if you read everything before the image.

Really now, clicking on a thumbnail probably is the better solution, I'd think. (As just saying "HEY NSFW BELOW scrolled too fast? not my problem!" isn't really convenient either) Making it fancier or whatever... would be pointless and an unnecessary hassle. The point is to just not show it unless the reader wants to see it.
I just ask if for some reason wiki software is stupid and doesn't let an image link to something else.

____________________
devin

Yoshi
i'm mima irl
Level: 112


Posts: 2509/3519
EXP: 14918702
For next: 419503

Since: 04-29-08

Pronouns: any
From: FL

Since last post: 297 days
Last activity: 1 day
Posted on 03-12-12 06:31:24 PM Link | Quote
"The tcrf.net lawyer has informed us that we need a warning! So.. if you are under the age of 18 or find this photograph offensive, please don't look at it. Thank you!"

____________________
Photo by Luc Viatour • go to it
Rick
M'Lord, there's a knife in your head!
Level: 152


Posts: 5693/7539
EXP: 43668632
For next: 633028

Since: 02-15-10

From: Maine

Since last post: 113 days
Last activity: 45 days
Posted on 03-12-12 06:35:40 PM Link | Quote
If the image really warrants a lot of NSFW, could just do what was done with the GTA: San Andreas pic of the Hot Coffee thing.

____________________


_______________________
| 5693 | 14307 | 755 | 19 |
GlitterBerri

Translator
Level: 39


Posts: 276/339
EXP: 403693
For next: 1078

Since: 11-10-10


Since last post: 6.6 years
Last activity: 1.2 years
Posted on 03-12-12 07:31:46 PM Link | Quote
But that's censorship, and I'd be curious to see what the offending content was.
GoldS
Member
Level: 41


Posts: 240/372
EXP: 477150
For next: 2995

Since: 03-15-10


Since last post: 2.1 years
Last activity: 13 days
Posted on 03-12-12 07:47:14 PM Link | Quote
I guess it'd be okay if the censored image was a clickable link to the real image.

____________________
Keitaro

Fire Snake
LOVELY ARRANGEMENT. VOLCANO BAKEMEAT
Level: 70


Posts: 1084/1191
EXP: 2898885
For next: 116926

Since: 09-09-08

From: California

Since last post: 4.1 years
Last activity: 3.8 years
Posted on 03-12-12 08:35:55 PM Link | Quote
Originally posted by Kazinsal
Alternately, a bit of JavaScript could allow a hover-over reveal of the image in question.

this seems like the most practical solution so far, honestly
ReiNi
さよなら＊へヴン
Level: 124


Posts: 4019/4444
EXP: 21750888
For next: 85713

Since: 07-21-07


Since last post: 6.7 years
Last activity: 3.3 years
Posted on 03-12-12 08:40:32 PM Link | Quote
Possibility doesn't dictate what you can do.
I still say something like this


along words words words words words words words words words words


would be simple enough. Maybe also tag the screenshot with {{NSFW}} and add fancy filters or something.


I guess another option would be simply point out WHERE in the game is it and not necessarialy illustrate the content, but I'd guess that wouldn't work.

____________________
Nicole

Disk-kun
Level: 146


Posts: 5847/6469
EXP: 38252672
For next: 260622

Since: 07-07-07

Pronouns: she/her
From: Boston, MA

Since last post: 69 days
Last activity: 1 day
Posted on 03-12-12 08:40:48 PM Link | Quote
Originally posted by Keitaro
Originally posted by Kazinsal
Alternately, a bit of JavaScript could allow a hover-over reveal of the image in question.

this seems like the most practical solution so far, honestly

It'd be nice too if we could have some kind of profile option to always show NSFW content. (Like, a wiki extension or something?)

____________________
Xkeeper

Level: 263


Posts: 19999/25343
EXP: 296716419
For next: 2244034

Since: 07-03-07

Pronouns: they/them/????????

Since last post: 9 days
Last activity: 3 days
Posted on 03-12-12 09:27:40 PM Link | Quote
Why aren't se just putting a box at the top with "NSFW content below"?

____________________
legacyme3
"In short, legacyme3 does horrible things to people, and I don't think anyone else on Jul should be exposed to him, no matter how decent of a person he pretends to be."

I don't normally ban for offsite behavior but you're a whole level of terrible.
Level: NaN


Posts: 1334/-1694
EXP: NaN
For next: 0

Since: 06-01-11


Since last post: 8.9 years
Last activity: 3.7 years
Posted on 03-12-12 10:04:12 PM Link | Quote
Originally posted by Xkeeper
Why aren't se just putting a box at the top with "NSFW content below"?


Apparently it'd be too simple?

____________________

What Would Leggy Do?

legacyme3 Trophy Card
Kazinsal

Level: 53


Posts: 197/674
EXP: 1122212
For next: 34907

Since: 01-19-11

Pronouns: he/him
From: Vancouver, Canada

Since last post: 232 days
Last activity: 191 days
Posted on 03-12-12 10:07:47 PM Link | Quote
It would work.

I don't see a problem with it.

So why not?

____________________
Tears fall from the shameless
Shelter me, guide me to the edge of the water
Selfless are the righteous
Burden me, lead me like a lamb to the slaughter
Nksor

Beezo
Level: 46


Posts: 417/478
EXP: 662202
For next: 49572

Since: 04-27-11

Pronouns: they/them
From: olympia, wa

Since last post: 3.6 years
Last activity: 3.6 years
Posted on 03-12-12 11:14:02 PM Link | Quote
I've bounced this idea around my idea more times than there are stars in the sky and I think that, after serious consideration, I've come to a position on this topic.

Putting any of these "NSFW tag" ideas into effect would mark an extremely tragic turn for TCRF. I'll try to detail why it's such a bad idea in the paragraphs below.

Doing this would be drawing a line where no line should be drawn. What would be "too NSFW," or at least explicit enough to waiver the little box? Would doing this encourage people to search for explicit stuff in games, and dump it all on TCRF? I'm not saying that this kind of content is a bad idea; rather, any content is positive content; but can you imagine what several pages bearing NSFW tags, boxes, etc everywhere would look like? It'd make us look more like a hub for hidden video game smut more than anything else. Upon plastering pages with "NSFW", the administrators would more than likely screen for things that would be considered too explicit - and where would you draw the line there? Are we going to start putting boxes on every page that has the word "fuck" on it? Are we simply going to "turn down" people who have content that the admins don't consider "proper" enough to be included?

You'd be alienating your audiences - and, with a wiki, your viewers are your contributors. It's a slippery slope, and everyone seems to be eager to go running head first down it. I can personally cite a conversation that took place inside of #tcrf, where a handful of people were complaining about the amount of articles based on games made with Adobe Flash. I can remember the general consensus that the majority came to, which was that in a community based resource - and in any case, really - you can't choose to act upon something, if something else is doing the exact same thing. If you're going to put a NSFW tag on one thing, well, you might as well do it on every page that includes things that are NSFW! Right? Right?

Not to mention the fact that doing this would be contradicting the very ideals of the site itself, one of them being to bring censored or cut things to light. And then we turn around and censor the very content that we just "un-censored?" What?

My opinion? Put the content in, as it is. Who are we really protecting? Are we protecting the kids, who, in all honestly, shouldn't be reading an article about Splatterhouse in the first place?

I apologize for my strong feelings on the subject, but I felt that I needed to get out my opinions.
Bagel

Giant Red Paratroopa
without music life would Bb
Level: 75


Posts: 1095/1446
EXP: 3798594
For next: 28310

Since: 03-30-09

Pronouns: he/him
From: bear

Since last post: 181 days
Last activity: 14 days
Posted on 03-12-12 11:17:50 PM (last edited by Bagel at 03-12-12 08:18 PM) Link | Quote
How about a disclaimer on the front page that tcrf may not always be the best site to view when at work, and that you should probably just go home first.

People should be responsible for themselves.

____________________
 bandcamp
google

twitters:
pri
pub
sister miyagi
50
Level: 17


Posts: 44/50
EXP: 23391
For next: 1352

Since: 04-30-10

From: Illinois

Since last post: 8.6 years
Last activity: 340 days
Posted on 03-12-12 11:29:49 PM (last edited by sister miyagi at 03-12-12 08:30 PM) Link | Quote
Why do people think putting NSFW warnings on pages would make people look exclusively for NSFW content to find? Why would having a NSFW template turn NSFW content into OMG HOT XXXX PRONS HERE? I agree it might be hard to define a line for what's NSFW and what's not, but if the Supreme Court knows it when they see it, I'm sure we can too

Yet another suggestion: put a disclaimer on the main page saying something along the lines of "There may be boobies on some of these pages so don't browse this site at work if your boss votes Republican!" That way it's up to the individual if they ding their work's web filter or whatever.

Edit: Probably should've read Bagel's post before posting mine...
Rachel Mae

Creature of Chaos
Level: 141


Posts: 4907/5929
EXP: 33575792
For next: 544222

Since: 07-03-07

Pronouns: she/her
From: Foxglen

Since last post: 12 days
Last activity: 2 hours
Posted on 03-12-12 11:35:32 PM Link | Quote
Originally posted by BlueWhirl
words
I think you're being a bit paranoid.

My biggest concern is people browsing the wiki at work, or in a public place, or with other family members around, unaware that such content even exists. I don't want anyone getting in trouble, and a NSFW tag is just common courtesy in many places on the Internet.

____________________
Nksor

Beezo
Level: 46


Posts: 418/478
EXP: 662202
For next: 49572

Since: 04-27-11

Pronouns: they/them
From: olympia, wa

Since last post: 3.6 years
Last activity: 3.6 years
Posted on 03-13-12 12:02:55 AM Link | Quote
Perhaps I should clarify what I meant when I said that I didn't want "NSFW tags" on the website. Many of the ideas suggested include flashy, annoying, or otherwise bothersome warnings. Not to mention the "spoiler boxes" and the idea to open up the image in a new tab, which would seriously chop up the flow of the pages. If a warning for potential NSFW content is necessary, then it should at least fit in with the page, no?

I'm seriously against censorship, or whatever you wish to call this, but I can understand people's concerns.
ReiNi
さよなら＊へヴン
Level: 124


Posts: 4020/4444
EXP: 21750888
For next: 85713

Since: 07-21-07


Since last post: 6.7 years
Last activity: 3.3 years
Posted on 03-13-12 12:35:21 AM (last edited by Reshiram at 03-12-12 09:36 PM) Link | Quote
Possibility doesn't dictate what you can do.
I am not trying to be harsh, I'm just going over everything you said and explaining why I think you are wrong.
Putting any of these "NSFW tag" ideas into effect would mark an extremely tragic turn for TCRF
It literally would show a picture before another one, or a notice, or something. A "tragic turn" happening would be the fault of those who would react to it.
Doing this would be drawing a line where no line should be drawn. What would be "too NSFW," or at least explicit enough to waiver the little box?
Simple guidelines, and a per-case basis. We are a small site and it's not like it isn't being watched over already.
Would doing this encourage people to search for explicit stuff in games, and dump it all on TCRF?
1. It shouldn't.
2. It'd still be unused content.
can you imagine what several pages bearing NSFW tags, boxes, etc everywhere would look like? It'd make us look more like a hub for hidden video game smut more than anything else.
1. The games that have such stuff are already not clean to begin with.
2. I don't understand how would a NSFW page somehow look worse with warnings than without.
the administrators would more than likely screen for things that would be considered too explicit - and where would you draw the line there?
hey BMF someone uploaded a sock to the site its porn
There won't be any "power corrupt administrators" scenarios. It's an easy to define thing.
Are we going to start putting boxes on every page that has the word "fuck" on it?
No. There would be simple guidelines. Something like "warn about realistic tits and genitals please". Further questionable cases can, again, simply be treated specifically.
Are we simply going to "turn down" people who have content that the admins don't consider "proper" enough to be included?
Nobody has ever mentioned "turning down" anything, nor will something be turned down because of the content itself.
You'd be alienating your audiences
Unless this audience gets offended at being warned that there's NSFW content, no.
I can personally cite a conversation that took place inside of #tcrf, where a handful of people were complaining about the amount of articles based on games made with Adobe Flash.
Which is an entirely different issue both in nature and consequence: There what was being discussed was basically notability. Which has absolutely nothing to do with this.
you can't choose to act upon something, if something else is doing the exact same thing
Wrong. Simply because that "something else" would not be doing the "exact same thing". The hypothetical context would vary.
This is why the so-called "Rule 0" exists. If in an specific case, something NEEDS to bypass certain guidelines and rules, it can be done.
If you're going to put a NSFW tag on one thing, well, you might as well do it on every page that includes things that are NSFW! Right? Right?
It would deppend on the pages themselves. Some things just wouldn't matter at all. Some others would benefit from HEY THIS IS NSFW JUST SO YOU KNOW.
Not to mention the fact that doing this would be contradicting the very ideals of the site itself, one of them being to bring censored or cut things to light. And then we turn around and censor the very content that we just "un-censored?" What?
... What are you saying? Nobody is censoring anything.
Who are we really protecting?
We aren't protecting anyone. This is a formality so people don't look at something and SUDDENLY PORN, which wouldn't be a nice thing to do because of what BMF said.



In the end, I'd rather just echo that. The point is simply warning people.

My suggestion was for when just a single thing was NSFW in an otherwise safe article... which now that I think about, is actually too much for something that probably will happen very rarely. But ultimately was purely for convenience sake.

A simple notice over the page for those heavy in such content would probably be a better choice.

____________________
sister miyagi
50
Level: 17


Posts: 45/50
EXP: 23391
For next: 1352

Since: 04-30-10

From: Illinois

Since last post: 8.6 years
Last activity: 340 days
Posted on 03-13-12 12:38:10 AM Link | Quote
Originally posted by BlueWhirl
Perhaps I should clarify what I meant when I said that I didn't want "NSFW tags" on the website. Many of the ideas suggested include flashy, annoying, or otherwise bothersome warnings. Not to mention the "spoiler boxes" and the idea to open up the image in a new tab, which would seriously chop up the flow of the pages. If a warning for potential NSFW content is necessary, then it should at least fit in with the page, no?

I'm seriously against censorship, or whatever you wish to call this, but I can understand people's concerns.


This isn't censorship. Censorship would be denying access to the pictures at all, either by editing them or refusing to have them on the wiki. This is just warning people they're about to see images that have nudity. Sorry but it irks me when people use that word wrong.

As far as chopping up the flow of a page, I've seen other wikis use expandable galleries to house large collections of images to save bandwidth (the pictures aren't loaded until the gallery is expanded), and it doesn't chop up pages at all - it actually makes them easier to navigate because you don't have to scroll through a million images. I really feel like you're just opposed to any sort of warning at all for some reason.

Anyway, it seems to have been taken care of.
Nksor

Beezo
Level: 46


Posts: 419/478
EXP: 662202
For next: 49572

Since: 04-27-11

Pronouns: they/them
From: olympia, wa

Since last post: 3.6 years
Last activity: 3.6 years
Posted on 03-13-12 01:14:57 AM Link | Quote
When I said "censorship" I wasn't meaning it in its most extreme form. Again, referring strictly to the ideas that would make users click things to view - you're altering the way people would see it.

content
[click here to view NSFW content]
content

The content aught to be equal with the rest, and we shouldn't be giving off the impression that certain content is better than other content.


Although, I don't know how much my argument matters anymore - it looks like the banner idea is going through anyways, which would be something that I support, or at least more than the idea I mentioned above.
RahanAkero

The End of the World
Level: 57


Posts: 521/756
EXP: 1399510
For next: 86418

Since: 11-25-09

From: Staten Island, NY

Since last post: 254 days
Last activity: 16 days
Posted on 03-13-12 03:55:18 AM Link | Quote
Originally posted by BlueWhirl
When I said "censorship" I wasn't meaning it in its most extreme form. Again, referring strictly to the ideas that would make users click things to view - you're altering the way people would see it.

content
[click here to view NSFW content]
content

The content aught to be equal with the rest, and we shouldn't be giving off the impression that certain content is better than other content.


Although, I don't know how much my argument matters anymore - it looks like the banner idea is going through anyways, which would be something that I support, or at least more than the idea I mentioned above.


Except it doesn't make any content "better" than other content, it just safeguards someone from potentially losing their job over a titty on their monitor, so to speak.

Simple solution, which was suggested before: In an article that is saturated with NSFW stuff or has an incredibly egregious *kind* of NSFW, a banner across the top with a mosaic'd-out cactus (or a cactus with some strategically-placed black bars) that says "This article isn't work-safe. There are many boobies or other offensive material that will make your boss act all prickly at you" should suffice.

If the article has a bunch of tame things and then , then a click-through would be a good diplomatic way of handling it.

If it's something like Mechanized Attack or Castlevania IV, then no real warning is needed. It's not that difficult or radical. D:

____________________
Pages: 1 2 3 4 Next newer thread | Next older thread
Jul - The Cutting Room Floor - TCRF and...nudity New poll - New thread - New reply


Rusted Logic
Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

35 database queries, 2 query cache hits.
Query execution time:  0.085858 seconds
Script execution time:  0.035965 seconds
Total render time:  0.121823 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 2 column 311 - Warning: unescaped & or unknown entity "&page"
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 188 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 95 - Warning: unescaped & or unknown entity "&page"
line 149 column 130 - Warning: unescaped & or unknown entity "&page"
line 149 column 163 - Warning: unescaped & or unknown entity "&page"
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 198 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 179 column 425 - Warning: missing </font> before <blockquote>
line 179 column 483 - Warning: inserting implicit <font>
line 179 column 483 - Warning: missing </font> before <hr>
line 179 column 548 - Warning: inserting implicit <font>
line 179 column 548 - Warning: missing </font> before <hr>
line 180 column 1 - Warning: inserting implicit <font>
line 183 column 1530 - Warning: discarding unexpected </font>
line 183 column 1702 - Warning: discarding unexpected </td>
line 186 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 188 column 9 - Warning: missing <tr>
line 206 column 13 - Warning: missing <tr>
line 207 column 102 - Warning: unescaped & or unknown entity "&postid"
line 212 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 214 column 9 - Warning: missing <tr>
line 232 column 13 - Warning: missing <tr>
line 233 column 102 - Warning: unescaped & or unknown entity "&postid"
line 241 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 243 column 9 - Warning: missing <tr>
line 261 column 13 - Warning: missing <tr>
line 262 column 102 - Warning: unescaped & or unknown entity "&postid"
line 267 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 269 column 9 - Warning: missing <tr>
line 287 column 13 - Warning: missing <tr>
line 288 column 102 - Warning: unescaped & or unknown entity "&postid"
line 293 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 295 column 9 - Warning: missing <tr>
line 313 column 13 - Warning: missing <tr>
line 314 column 102 - Warning: unescaped & or unknown entity "&postid"
line 320 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 322 column 9 - Warning: missing <tr>
line 340 column 13 - Warning: missing <tr>
line 341 column 102 - Warning: unescaped & or unknown entity "&postid"
line 352 column 1209 - Warning: discarding unexpected </font>
line 352 column 1381 - Warning: discarding unexpected </td>
line 355 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 357 column 9 - Warning: missing <tr>
line 375 column 13 - Warning: missing <tr>
line 376 column 102 - Warning: unescaped & or unknown entity "&postid"
line 378 column 136 - Warning: missing <tr>
line 380 column 1425 - Warning: <style> isn't allowed in <td> elements
line 378 column 9 - Info: <td> previously mentioned
line 383 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 385 column 9 - Warning: missing <tr>
line 403 column 13 - Warning: missing <tr>
line 404 column 102 - Warning: unescaped & or unknown entity "&postid"
line 409 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 411 column 9 - Warning: missing <tr>
line 429 column 13 - Warning: missing <tr>
line 430 column 102 - Warning: unescaped & or unknown entity "&postid"
line 432 column 74 - Warning: <style> isn't allowed in <td> elements
line 432 column 9 - Info: <td> previously mentioned
line 434 column 1238 - Warning: discarding unexpected </div>
line 434 column 1244 - Warning: discarding unexpected </td>
line 437 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 439 column 9 - Warning: missing <tr>
line 457 column 13 - Warning: missing <tr>
line 458 column 102 - Warning: unescaped & or unknown entity "&postid"
line 470 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 472 column 9 - Warning: missing <tr>
line 490 column 13 - Warning: missing <tr>
line 491 column 102 - Warning: unescaped & or unknown entity "&postid"
line 508 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 510 column 9 - Warning: missing <tr>
line 528 column 13 - Warning: missing <tr>
line 529 column 102 - Warning: unescaped & or unknown entity "&postid"
line 531 column 85 - Warning: <style> isn't allowed in <td> elements
line 531 column 9 - Info: <td> previously mentioned
line 531 column 1400 - Warning: missing <tr>
line 536 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 538 column 9 - Warning: missing <tr>
line 556 column 13 - Warning: missing <tr>
line 557 column 102 - Warning: unescaped & or unknown entity "&postid"
line 566 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 568 column 9 - Warning: missing <tr>
line 586 column 13 - Warning: missing <tr>
line 587 column 102 - Warning: unescaped & or unknown entity "&postid"
line 589 column 74 - Warning: <link> isn't allowed in <td> elements
line 589 column 9 - Info: <td> previously mentioned
line 594 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 596 column 9 - Warning: missing <tr>
line 614 column 13 - Warning: missing <tr>
line 615 column 102 - Warning: unescaped & or unknown entity "&postid"
line 622 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 624 column 9 - Warning: missing <tr>
line 642 column 13 - Warning: missing <tr>
line 643 column 102 - Warning: unescaped & or unknown entity "&postid"
line 645 column 425 - Warning: missing </font> before <blockquote>
line 647 column 601 - Warning: inserting implicit <font>
line 647 column 601 - Warning: missing </font> before <hr>
line 647 column 605 - Warning: inserting implicit <font>
line 647 column 605 - Warning: missing </font> before <hr>
line 647 column 716 - Warning: inserting implicit <font>
line 647 column 716 - Warning: missing </font> before <blockquote>
line 649 column 893 - Warning: inserting implicit <font>
line 649 column 893 - Warning: missing </font> before <hr>
line 649 column 897 - Warning: inserting implicit <font>
line 649 column 897 - Warning: missing </font> before <hr>
line 649 column 1059 - Warning: inserting implicit <font>
line 649 column 1059 - Warning: missing </font> before <blockquote>
line 651 column 1194 - Warning: inserting implicit <font>
line 651 column 1194 - Warning: missing </font> before <hr>
line 651 column 1198 - Warning: inserting implicit <font>
line 651 column 1198 - Warning: missing </font> before <hr>
line 651 column 1312 - Warning: inserting implicit <font>
line 651 column 1312 - Warning: missing </font> before <blockquote>
line 654 column 1391 - Warning: inserting implicit <font>
line 654 column 1391 - Warning: missing </font> before <hr>
line 654 column 1395 - Warning: inserting implicit <font>
line 654 column 1395 - Warning: missing </font> before <hr>
line 654 column 1590 - Warning: inserting implicit <font>
line 654 column 1590 - Warning: missing </font> before <blockquote>
line 657 column 1774 - Warning: inserting implicit <font>
line 657 column 1774 - Warning: missing </font> before <hr>
line 657 column 1778 - Warning: inserting implicit <font>
line 657 column 1778 - Warning: missing </font> before <hr>
line 657 column 1935 - Warning: inserting implicit <font>
line 657 column 1935 - Warning: missing </font> before <blockquote>
line 660 column 2101 - Warning: inserting implicit <font>
line 660 column 2101 - Warning: missing </font> before <hr>
line 660 column 2105 - Warning: inserting implicit <font>
line 660 column 2105 - Warning: missing </font> before <hr>
line 660 column 2203 - Warning: inserting implicit <font>
line 660 column 2203 - Warning: missing </font> before <blockquote>
line 662 column 2395 - Warning: inserting implicit <font>
line 662 column 2395 - Warning: missing </font> before <hr>
line 662 column 2399 - Warning: inserting implicit <font>
line 662 column 2399 - Warning: missing </font> before <hr>
line 662 column 2525 - Warning: inserting implicit <font>
line 662 column 2538 - Warning: inserting implicit <font>
line 662 column 2538 - Warning: missing </font> before <blockquote>
line 664 column 2673 - Warning: inserting implicit <font>
line 664 column 2673 - Warning: missing </font> before <hr>
line 664 column 2677 - Warning: inserting implicit <font>
line 664 column 2677 - Warning: missing </font> before <hr>
line 664 column 2728 - Warning: inserting implicit <font>
line 664 column 2728 - Warning: missing </font> before <blockquote>
line 666 column 2829 - Warning: inserting implicit <font>
line 666 column 2829 - Warning: missing </font> before <hr>
line 666 column 2833 - Warning: inserting implicit <font>
line 666 column 2833 - Warning: missing </font> before <hr>
line 666 column 3029 - Warning: inserting implicit <font>
line 666 column 3029 - Warning: missing </font> before <blockquote>
line 668 column 3220 - Warning: inserting implicit <font>
line 668 column 3220 - Warning: missing </font> before <hr>
line 668 column 3224 - Warning: inserting implicit <font>
line 668 column 3224 - Warning: missing </font> before <hr>
line 668 column 3328 - Warning: inserting implicit <font>
line 668 column 3328 - Warning: missing </font> before <blockquote>
line 671 column 3613 - Warning: inserting implicit <font>
line 671 column 3613 - Warning: missing </font> before <hr>
line 671 column 3617 - Warning: inserting implicit <font>
line 671 column 3617 - Warning: missing </font> before <hr>
line 671 column 3775 - Warning: inserting implicit <font>
line 671 column 3775 - Warning: missing </font> before <blockquote>
line 673 column 3943 - Warning: inserting implicit <font>
line 673 column 3943 - Warning: missing </font> before <hr>
line 673 column 3947 - Warning: inserting implicit <font>
line 673 column 3947 - Warning: missing </font> before <hr>
line 673 column 4196 - Warning: inserting implicit <font>
line 673 column 4209 - Warning: inserting implicit <font>
line 673 column 4209 - Warning: missing </font> before <blockquote>
line 675 column 4283 - Warning: inserting implicit <font>
line 675 column 4283 - Warning: missing </font> before <hr>
line 675 column 4287 - Warning: inserting implicit <font>
line 675 column 4287 - Warning: missing </font> before <hr>
line 675 column 4333 - Warning: inserting implicit <font>
line 683 column 5141 - Warning: discarding unexpected </font>
line 683 column 5313 - Warning: discarding unexpected </td>
line 686 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 688 column 9 - Warning: missing <tr>
line 706 column 13 - Warning: missing <tr>
line 707 column 102 - Warning: unescaped & or unknown entity "&postid"
line 720 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 722 column 9 - Warning: missing <tr>
line 740 column 13 - Warning: missing <tr>
line 741 column 102 - Warning: unescaped & or unknown entity "&postid"
line 754 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 756 column 9 - Warning: missing <tr>
line 774 column 13 - Warning: missing <tr>
line 775 column 102 - Warning: unescaped & or unknown entity "&postid"
line 777 column 277 - Warning: missing <tr>
line 777 column 549 - Warning: missing <tr>
line 777 column 651 - Warning: missing </font> before <blockquote>
line 777 column 681 - Warning: inserting implicit <font>
line 777 column 681 - Warning: missing </font> before <hr>
line 777 column 747 - Warning: inserting implicit <font>
line 777 column 747 - Warning: missing </font> before <hr>
line 784 column 1 - Warning: inserting implicit <font>
line 784 column 1 - Warning: missing </font> before <hr>
line 786 column 1 - Warning: inserting implicit <font>
line 777 column 639 - Warning: missing </blockquote>
line 794 column 2594 - Warning: plain text isn't allowed in <tr> elements
line 777 column 549 - Info: <tr> previously mentioned
line 797 column 17 - Warning: missing <tr>
line 797 column 17 - Warning: discarding unexpected <table>
line 800 column 35 - Warning: missing <tr>
line 800 column 95 - Warning: unescaped & or unknown entity "&page"
line 800 column 130 - Warning: unescaped & or unknown entity "&page"
line 800 column 163 - Warning: unescaped & or unknown entity "&page"
line 800 column 50 - Warning: missing </font> before </td>
line 800 column 198 - Warning: missing </font> before </table>
line 802 column 35 - Warning: missing <tr>
line 802 column 50 - Warning: missing </font> before </td>
line 803 column 37 - Warning: unescaped & or unknown entity "&id"
line 802 column 188 - Warning: missing </font> before </table>
line 804 column 17 - Warning: discarding unexpected </textarea>
line 804 column 28 - Warning: discarding unexpected </form>
line 804 column 35 - Warning: discarding unexpected </embed>
line 804 column 43 - Warning: discarding unexpected </noembed>
line 804 column 53 - Warning: discarding unexpected </noscript>
line 804 column 64 - Warning: discarding unexpected </noembed>
line 804 column 74 - Warning: discarding unexpected </embed>
line 804 column 82 - Warning: discarding unexpected </table>
line 804 column 90 - Warning: discarding unexpected </table>
line 806 column 9 - Warning: missing </font> before <table>
line 818 column 25 - Warning: discarding unexpected </font>
line 827 column 57 - Warning: discarding unexpected </font>
line 805 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 23 - Warning: <img> lacks "alt" attribute
line 161 column 64 - Warning: <img> lacks "alt" attribute
line 161 column 113 - Warning: <img> lacks "alt" attribute
line 161 column 163 - Warning: <img> lacks "alt" attribute
line 162 column 11 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 180 column 872 - Warning: <img> proprietary attribute value "absmiddle"
line 180 column 872 - Warning: <img> lacks "alt" attribute
line 183 column 1425 - Warning: <img> lacks "alt" attribute
line 183 column 1587 - Warning: <img> lacks "alt" attribute
line 190 column 11 - Warning: <img> lacks "alt" attribute
line 191 column 23 - Warning: <img> lacks "alt" attribute
line 191 column 64 - Warning: <img> lacks "alt" attribute
line 191 column 113 - Warning: <img> lacks "alt" attribute
line 191 column 163 - Warning: <img> lacks "alt" attribute
line 192 column 11 - Warning: <img> lacks "alt" attribute
line 202 column 15 - Warning: <img> lacks "alt" attribute
line 217 column 23 - Warning: <img> lacks "alt" attribute
line 217 column 64 - Warning: <img> lacks "alt" attribute
line 217 column 113 - Warning: <img> lacks "alt" attribute
line 217 column 163 - Warning: <img> lacks "alt" attribute
line 218 column 11 - Warning: <img> lacks "alt" attribute
line 228 column 15 - Warning: <img> lacks "alt" attribute
line 235 column 285 - Warning: <img> lacks "alt" attribute
line 245 column 11 - Warning: <img> lacks "alt" attribute
line 246 column 22 - Warning: <img> lacks "alt" attribute
line 246 column 63 - Warning: <img> lacks "alt" attribute
line 246 column 112 - Warning: <img> lacks "alt" attribute
line 246 column 161 - Warning: <img> lacks "alt" attribute
line 247 column 11 - Warning: <img> lacks "alt" attribute
line 257 column 15 - Warning: <img> lacks "alt" attribute
line 272 column 22 - Warning: <img> lacks "alt" attribute
line 272 column 63 - Warning: <img> lacks "alt" attribute
line 272 column 112 - Warning: <img> lacks "alt" attribute
line 272 column 161 - Warning: <img> lacks "alt" attribute
line 273 column 11 - Warning: <img> lacks "alt" attribute
line 283 column 15 - Warning: <img> lacks "alt" attribute
line 290 column 188 - Warning: <img> lacks "alt" attribute
line 297 column 11 - Warning: <img> lacks "alt" attribute
line 298 column 22 - Warning: <img> lacks "alt" attribute
line 298 column 63 - Warning: <img> lacks "alt" attribute
line 298 column 112 - Warning: <img> lacks "alt" attribute
line 298 column 162 - Warning: <img> lacks "alt" attribute
line 309 column 15 - Warning: <img> lacks "alt" attribute
line 317 column 323 - Warning: <img> proprietary attribute value "absmiddle"
line 317 column 323 - Warning: <img> lacks "alt" attribute
line 325 column 23 - Warning: <img> lacks "alt" attribute
line 325 column 64 - Warning: <img> lacks "alt" attribute
line 325 column 113 - Warning: <img> lacks "alt" attribute
line 325 column 163 - Warning: <img> lacks "alt" attribute
line 326 column 11 - Warning: <img> lacks "alt" attribute
line 336 column 15 - Warning: <img> lacks "alt" attribute
line 345 column 586 - Warning: <img> lacks "alt" attribute
line 352 column 1104 - Warning: <img> lacks "alt" attribute
line 352 column 1266 - Warning: <img> lacks "alt" attribute
line 359 column 11 - Warning: <img> lacks "alt" attribute
line 360 column 23 - Warning: <img> lacks "alt" attribute
line 360 column 64 - Warning: <img> lacks "alt" attribute
line 360 column 113 - Warning: <img> lacks "alt" attribute
line 360 column 163 - Warning: <img> lacks "alt" attribute
line 361 column 11 - Warning: <img> lacks "alt" attribute
line 371 column 15 - Warning: <img> lacks "alt" attribute
line 379 column 1012 - Warning: <img> proprietary attribute value "absmiddle"
line 379 column 1012 - Warning: <img> lacks "alt" attribute
line 380 column 1273 - Warning: <td> attribute "width" has invalid value "215px"
line 388 column 23 - Warning: <img> lacks "alt" attribute
line 388 column 64 - Warning: <img> lacks "alt" attribute
line 388 column 113 - Warning: <img> lacks "alt" attribute
line 388 column 163 - Warning: <img> lacks "alt" attribute
line 389 column 11 - Warning: <img> lacks "alt" attribute
line 399 column 15 - Warning: <img> lacks "alt" attribute
line 406 column 276 - Warning: <img> lacks "alt" attribute
line 414 column 23 - Warning: <img> lacks "alt" attribute
line 414 column 64 - Warning: <img> lacks "alt" attribute
line 415 column 11 - Warning: <img> lacks "alt" attribute
line 425 column 15 - Warning: <img> lacks "alt" attribute
line 434 column 934 - Warning: <img> proprietary attribute value "absmiddle"
line 434 column 934 - Warning: <img> lacks "alt" attribute
line 442 column 22 - Warning: <img> lacks "alt" attribute
line 442 column 63 - Warning: <img> lacks "alt" attribute
line 442 column 112 - Warning: <img> lacks "alt" attribute
line 442 column 162 - Warning: <img> lacks "alt" attribute
line 443 column 11 - Warning: <img> lacks "alt" attribute
line 453 column 15 - Warning: <img> lacks "alt" attribute
line 474 column 11 - Warning: <img> lacks "alt" attribute
line 475 column 22 - Warning: <img> lacks "alt" attribute
line 475 column 63 - Warning: <img> lacks "alt" attribute
line 475 column 111 - Warning: <img> lacks "alt" attribute
line 475 column 161 - Warning: <img> lacks "alt" attribute
line 476 column 11 - Warning: <img> lacks "alt" attribute
line 486 column 15 - Warning: <img> lacks "alt" attribute
line 512 column 11 - Warning: <img> lacks "alt" attribute
line 513 column 22 - Warning: <img> lacks "alt" attribute
line 513 column 63 - Warning: <img> lacks "alt" attribute
line 513 column 112 - Warning: <img> lacks "alt" attribute
line 513 column 162 - Warning: <img> lacks "alt" attribute
line 524 column 15 - Warning: <img> lacks "alt" attribute
line 533 column 2362 - Warning: <img> lacks "alt" attribute
line 540 column 14 - Warning: <img> proprietary attribute value "absmiddle"
line 540 column 14 - Warning: <img> lacks "alt" attribute
line 541 column 22 - Warning: <img> lacks "alt" attribute
line 541 column 63 - Warning: <img> lacks "alt" attribute
line 541 column 112 - Warning: <img> lacks "alt" attribute
line 541 column 162 - Warning: <img> lacks "alt" attribute
line 552 column 15 - Warning: <img> lacks "alt" attribute
line 559 column 413 - Warning: <img> proprietary attribute value "absmiddle"
line 559 column 413 - Warning: <img> lacks "alt" attribute
line 570 column 11 - Warning: <img> lacks "alt" attribute
line 571 column 23 - Warning: <img> lacks "alt" attribute
line 571 column 64 - Warning: <img> lacks "alt" attribute
line 571 column 113 - Warning: <img> lacks "alt" attribute
line 571 column 163 - Warning: <img> lacks "alt" attribute
line 572 column 11 - Warning: <img> lacks "alt" attribute
line 582 column 15 - Warning: <img> lacks "alt" attribute
line 598 column 11 - Warning: <img> lacks "alt" attribute
line 599 column 22 - Warning: <img> lacks "alt" attribute
line 599 column 63 - Warning: <img> lacks "alt" attribute
line 599 column 111 - Warning: <img> lacks "alt" attribute
line 599 column 161 - Warning: <img> lacks "alt" attribute
line 600 column 11 - Warning: <img> lacks "alt" attribute
line 610 column 15 - Warning: <img> lacks "alt" attribute
line 627 column 23 - Warning: <img> lacks "alt" attribute
line 627 column 64 - Warning: <img> lacks "alt" attribute
line 627 column 113 - Warning: <img> lacks "alt" attribute
line 627 column 163 - Warning: <img> lacks "alt" attribute
line 628 column 11 - Warning: <img> lacks "alt" attribute
line 638 column 15 - Warning: <img> lacks "alt" attribute
line 683 column 5036 - Warning: <img> lacks "alt" attribute
line 683 column 5198 - Warning: <img> lacks "alt" attribute
line 690 column 14 - Warning: <img> proprietary attribute value "absmiddle"
line 690 column 14 - Warning: <img> lacks "alt" attribute
line 691 column 22 - Warning: <img> lacks "alt" attribute
line 691 column 63 - Warning: <img> lacks "alt" attribute
line 691 column 112 - Warning: <img> lacks "alt" attribute
line 691 column 162 - Warning: <img> lacks "alt" attribute
line 702 column 15 - Warning: <img> lacks "alt" attribute
line 724 column 11 - Warning: <img> lacks "alt" attribute
line 725 column 22 - Warning: <img> lacks "alt" attribute
line 725 column 63 - Warning: <img> lacks "alt" attribute
line 725 column 111 - Warning: <img> lacks "alt" attribute
line 725 column 161 - Warning: <img> lacks "alt" attribute
line 726 column 11 - Warning: <img> lacks "alt" attribute
line 736 column 15 - Warning: <img> lacks "alt" attribute
line 758 column 11 - Warning: <img> lacks "alt" attribute
line 759 column 22 - Warning: <img> lacks "alt" attribute
line 759 column 63 - Warning: <img> lacks "alt" attribute
line 759 column 111 - Warning: <img> lacks "alt" attribute
line 759 column 161 - Warning: <img> lacks "alt" attribute
line 760 column 11 - Warning: <img> lacks "alt" attribute
line 770 column 15 - Warning: <img> lacks "alt" attribute
line 777 column 329 - Warning: <img> lacks "alt" attribute
line 791 column 2107 - Warning: <img> lacks "alt" attribute
line 793 column 2513 - Warning: <img> lacks "alt" attribute
line 794 column 2602 - Warning: <img> lacks "alt" attribute
line 803 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 803 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 803 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 812 column 25 - Warning: <img> lacks "alt" attribute
line 817 column 267 - Warning: <img> lacks "alt" attribute
line 179 column 425 - Warning: trimming empty <font>
line 647 column 601 - Warning: trimming empty <font>
line 649 column 893 - Warning: trimming empty <font>
line 651 column 1194 - Warning: trimming empty <font>
line 654 column 1391 - Warning: trimming empty <font>
line 657 column 1774 - Warning: trimming empty <font>
line 660 column 2101 - Warning: trimming empty <font>
line 662 column 2395 - Warning: trimming empty <font>
line 662 column 2525 - Warning: trimming empty <font>
line 664 column 2673 - Warning: trimming empty <font>
line 666 column 2829 - Warning: trimming empty <font>
line 668 column 3220 - Warning: trimming empty <font>
line 671 column 3613 - Warning: trimming empty <font>
line 673 column 3943 - Warning: trimming empty <font>
line 673 column 4196 - Warning: trimming empty <font>
line 675 column 4283 - Warning: trimming empty <font>
line 777 column 651 - Warning: trimming empty <font>
line 797 column 17 - Warning: trimming empty <tr>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 179 column 74 - Warning: <table> proprietary attribute "height"
line 183 column 1399 - Warning: <marquee> is not approved by W3C
line 207 column 27 - Warning: <nobr> is not approved by W3C
line 233 column 27 - Warning: <nobr> is not approved by W3C
line 262 column 27 - Warning: <nobr> is not approved by W3C
line 288 column 27 - Warning: <nobr> is not approved by W3C
line 314 column 27 - Warning: <nobr> is not approved by W3C
line 341 column 27 - Warning: <nobr> is not approved by W3C
line 343 column 74 - Warning: <table> proprietary attribute "height"
line 352 column 1078 - Warning: <marquee> is not approved by W3C
line 376 column 27 - Warning: <nobr> is not approved by W3C
line 378 column 74 - Warning: <table> proprietary attribute "height"
line 404 column 27 - Warning: <nobr> is not approved by W3C
line 406 column 176 - Warning: <marquee> is not approved by W3C
line 430 column 27 - Warning: <nobr> is not approved by W3C
line 458 column 27 - Warning: <nobr> is not approved by W3C
line 491 column 27 - Warning: <nobr> is not approved by W3C
line 529 column 27 - Warning: <nobr> is not approved by W3C
line 557 column 27 - Warning: <nobr> is not approved by W3C
line 587 column 27 - Warning: <nobr> is not approved by W3C
line 615 column 27 - Warning: <nobr> is not approved by W3C
line 643 column 27 - Warning: <nobr> is not approved by W3C
line 645 column 74 - Warning: <table> proprietary attribute "height"
line 683 column 5010 - Warning: <marquee> is not approved by W3C
line 707 column 27 - Warning: <nobr> is not approved by W3C
line 741 column 27 - Warning: <nobr> is not approved by W3C
line 775 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 450 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md