Not sure if the other moderators have dealt with any. It's the same linseo****blog bollox, I think that should be blocked. 

i'll look at it tonight, if it's all one IP it should be easy to block. 

thanks for the report, it appears the problem is unclosed uppercase tags don't get closed correctly (my code was only scanning for unclosed lowercase tags.) Will fix soon. 

I can't get the RSS feed to load, is it down for everyone or is it something with just my machine? 

seems like there is a problem with the (R) symbol in the second news story (fruitz of dojo post.) I wonder if i need to do something to correctly HTML-encode symbols like that. 

Recently I started Q1 modelling and found it hard work trying to track down all the resources for my project. I read through the modelling thread here which was full of really cool information but it could have been summarized into a sticky top post.

Is there any plans of implementing a knowledge thread about certain core subjects? (qc, coding, skins, modelling, entities etc) Like they only contains core stuff and not the pages of fluff that often is the case with some of the threads here. 

if i understand correctly, you're talking about how at the top of a thread, there is a regularly-updated "super-post" that contains all of the best info from all the other posts in the thread?

I'm not sure about that since it requires a lot of human labor, but it might be a good idea to be able to flag posts as "informative" and then have a filter view where you see only the informative posts from the thread. 

would certainly be a good idea because there is some awesome information already in the threads, just they are buried. If you can flag good content then at least it would make a super post of information. 

here, or i'm just to dumb to find?
Would save some questions ^^ 

google does a pretty decent job tbh. never really missed having a search here. 

quaddicted is partially a wiki nowadays, pages like that would be very welcome. put them into /tools/ I guess.

eg http://www.quaddicted.com/tools/map_compilers 

What you want is a wiki. 

Yeah, just add site:celephais.net/board to your search term and there you go. Of course you can also open the whole thread and do a browser search if it's in Mapping Help, for example. 

nice tipp negke, thx!

A general wiki about Quake (1-3A) editing would be nais.
Much information about such stuff (advanced compilers & their switches, editors, entities) is scattered throughout the net, imo it would make sense to collect it in such a place. 

http://quake.wikia.com/ maybe? 

http://www.grandtheftwiki.com/Grand_Theft_Wiki:Move_from_Wikia 

haven't checked it out though. If its a genuinely bad layout and awkward to use people will prefer a better one.

The reasoning laid out sounds more like a personal fued. Which is fine, although the reasoning sounds a bit naive. 

why would you let a company make money off your work? 

 

But it's a fine line, and I haven't investigated the thing. 

Func is free!
Quaddicted is free!
Oh wait, you are all being sold!

Your mod will be free right?
All those hours.

If one cares, one invests time and money into providing something to others for free. 

And often you yourself get a benefit off it too. God, I hated having to use Fileplanet and other "login and wait 2 minutes" money-makers for map downloads...

Oh look, all the ad-supported hosted sites on Planetquake.com were deleted. Oops! Who tells you Wikia gives a fuck about your content if it is not profitable?

Disclaimer: I am one of those Archiveteam zealots. 

How about an approval process for discussion threads, just as there is for news threads? 

as well as getting rid of spam threads, it means we hopefully won't get any shitstorms like that fiend mod/cyst popping palava. Considering how strict the rules supposedly are for discussion threads, it seems odd that there is literally no restrictions on posting them. 

What kind of forum would that be...

The moderators simply need more power - an option to mark posts as spam and delete (or hide) threads. This shouldn't be hard to implement.