MS Update Mod Squad Update - October 24th, 2007

Add me to the "excessive HTML in MS updates is problematic" crew list. At least make sure a plaintext version gets posted somewhere for history's sake if you want to make the update a fancy one. We've already got one for this week, so it's hardly worth squabbling over, but it might be a good idea to make that a general policy for future uber-HTMLed MSUs.

 

This no-HTML issue has come up, oh, like A MILLION times in the past. Every time the "No HTML unless necessary" rule is planted. A few months later, a new slew of mods comes in and uses HTML. Then the issue comes up again...

...I've been here too long.

 

I'd be for just having the main points listed in plain text below the fancy version.

 

Might not be a bad idea. Instead of banning HTML completely, we can just require moderators, who want to do HTML, to also do an outline in Plain Text as well.

 

Excellent compromise.

 

I agree. If it keeps coming up, its something worth noting and looking at. I don't want to necessarily deny the ability to do it, but understand the need for it being done in plain version, too.

I do think we need to remember that not everyone has the huge high res monitors, especially at work, even when we make banners. Maybe we can lower the res when do HTML as a general good practice, at least on the MSUs.

 

That sounds like a good idea to me as well. I always enjoy the HTML updates but we need to make sure that everyone can read them.

 

Why bother with the HTML at all though. It serves no purpose.

Let's just have the updates in standard board markup, and the time saved by the mod in question could be put to better use elsewhere (on the boards, in modsquad or in real life).

 

One could argue that HTML serves the same purpose of pretty banners. They're not necessary, but they're still nice to have, and fun to make.

 

The HTML is fun, a lot of people get a kick out of it, and, providing the mod isn't failing at his moderating duties in the process of providing an HTML-ful Mod Squad update, I don't see any harm in it. Of course it shouldn't be a requirement; of course there's nothing wrong with it if a mod should not provide an HTML update. But the readability/history objection is the important one. And, since we've got a compromise suggested to deal with that, I see no harm in HTML updates, if the mods want to take the time to do them. I enjoy them, in general.

-Paul

 

It's fun. People get enjoyment out of it. I don't think there's any pressure on the mods to use it and I'm sure they're better able to determine how they should spend their own time than we are. I don't see the point of denying people bit of a laugh. If a mod wishes to use HTML, let them provided they also post the main points in plain text. The people who want HTML are happy. The people who can't view the HTML are happy. And the people who just want them main points without having to read the extra theme based fluff are happy. And frankly anyone else will never be happy. I think that's everyone.

 

i used to be anti html but i've warmed to it. who cares if you can't read am MSU from like a year ago? person wasting time reading old MSU's < person wasting time creating html MSU's

but i agree with the main points in plain text thing.

 

HTML is fun, and it stimulates the creative part of your brain.

 

Its just down to individual mod preference. Some mods like to put HTML in because thats what they want to do. Others are more "traditional" about just writing the update and leaving it at that.
I think its fine the way we do it right now. Some weeks you'll get a pretty HTML style MSU and other weeks it'll just be a straightforward write up.

 

Well, I won't deny that's true, but by that logic, I'm sure there are tons of things you, I, and everyone else has done that probably weren't the best uses of time we needed for some other activities, so we'd better stop doing all fun stuff right this minute. If a mod wants to make a fancy update and enjoys doing it, I think that's their prerogative. I'd just prefer if the plaintext option were there as well for readers who want it.

Also, sign-ups are going on for the PT Trivia Game.

 

Looks like my definition of 'fun' doesn't quite gel with many of the users here.

May I request that the markup version of future updates be posted in a second post beneath the opening one, so that it can be quoted (and futureproofed for viewing) without being encumbered by HTML in the same post.

 

What about HTML to open the thread with the first post and then a separate, second post with the Plain Text version?

 

I think that's a good idea.

 

I like the idea proposed by 506 and jp.

 

Hey, I'm not saying I would find it fun to sit down and write out a bunch of crap in HTML, just that it's not really my business if someone else does. Sort of like... um... I don't really care what people believe as long as they don't start handing me those comic strips telling me I'm going to hell.

And I like your suggestion.

 

makes more sense to have it the other way around

 

It's McCartney/Lennon, dammit!

 

Well the only reason I say that HTML should be first is because - for updates that want HTML - the opening post is the first thing everyone sees. If someone were to do an HTML update, it would be for the visual effects. So I would want the visual effects to be seen first, not second. Plain Text could come second and wouldn't be affected at all since it'll be a separate post.

 

I couldn't disagree more. The first priority of the MS Update is to convey information to everyone, not impress us with your html skills.

Hence the plain text should come first to ensure that everyone can read the update when first opened. The second, and potentially more important point, is that following demotion an MS update in html is completely unreadable, and often becomes significantly longer than the original post. Hence someone looking through an old MS update will open the thread, sees the babble of unreabable nonsense and have to scroll to read the plain text version. Those not in the know will simply close the thread unaware of the plain text version sitting below.

To be honest I'd go a step further and limit the plain text version to main points only, and keep it free of the fluff which has plagued MS Updates recently. That gives you an executive summary in the opening post for those only interested in actual updates, then the mod is free to impress us all with their instant wit and ready-repartee in the subsquent post.

 

OTOH, you have my updates which are always guaranteed to be HTML-free as well as including attempts at witty and I am fairly certain that you can't say that my updates *don't* contain the information contained within the attempted-wit that needs to be conveyed though, right?

Which means it's not a problem with the wit and repartee so much as the individual mod. And that is what makes us all human... or robotic-attempting-human in my case.