Quoting: Cheeseness

Quoting: sobkasI don't see any reason to not try it again, but now with a more reputable advertiser(gambling site, really?).

IMO, it's better to chase advertisers who are in-line with the intended audience of the content (in this case gaming and Linux related stuff).

Also, I think I just accidentally reported your post thanks to a misclick >_<

Had this been discussed previously? I was surprised to learn that sponsored articles were being looked at.

I don't actually do any chasing for adverts bar one attempt on digital point which didn't go anywhere. Adsense luckly has picked up recently a little.

Yeah Samsai suggested to move the report link.

It was discussed on IRC, but as stated before it was just an experiment and it didn't work, so thankfully no harm done and lessons learnt.

Looking at modifying gols current design to match this sort of look:
http://i.imgur.com/69unoCI.png

Any suggestions guys? Kinda set on a darker background for better contrast, but need ideas to make it look really good. CSS help appreciated to make it awesome.

Quoting: liamdaweIt was discussed on IRC, but as stated before it was just an experiment and it didn't work, so thankfully no harm done and lessons learnt.

Ah, OK. When I first spotted it, I looked through my IRC logs and couldn't find anything.

Quoting: liamdaweAny suggestions guys? Kinda set on a darker background for better contrast, but need ideas to make it look really good. CSS help appreciated to make it awesome.

I still think some kind of texture on the background might be helpful. Some subtle noise like the Humble site used to have or like we've got on steamlug.org at the moment.

I've been following Liam's problems with Reddit's moderators and today I decided that we should have clear guidelines for our moderators. IMO having these guidelines would give the moderation some consistency and reduce the possibility of "unfair" punishments.

I've created a draft here: [https://dl.dropboxusercontent.com/u/80386521/Moderation%20guidelines.odt](https://dl.dropboxusercontent.com/u/80386521/Moderation%20guidelines.odt)

If you feel like something needs to be changed/added then please tell me. Ideas are always welcome.

I'm fully behind what Samsai is doing FYI guys.

It seems fine to me.

Cheese, Alex, Muntdef and anyone else any thoughts?

I don't really pay much attention to what's going on in the forum/comments unless somebody reports a post. Still, some guidelines are always better then no guidelines, so 'tis fine as far as I'm concerned. I would also add an option for a timed ban.

I'm quite OK with Samsai's guidelines. :)

My personal view is that guidelines 1-3 should be self-evident to anyone who's not a dedicated troll, but nonetheless it's good to have them written down for everyone to see and/or remember.

If anything, I'd modify guideline #6 so any ban/deleted message must be explained to the offender even if an explanation hasn't been requested. It's not a big effort doing so and in my experience it can prevent some kind of people from ***ing around about «how arbitrary moderators are» and how «they deleted my comment withouth even an explanation».

Oh, come on, we cannot say biatch in these forums? :P

Looks good. The only direct feedback I have is that 7a doesn't describe what constitutes spam.

One other thought - in regards to item 2, where the qualifier is that there's no intent to offend, that may not be enough. There are situations where somebody may act in a way that's not intentionally offensive (or offensive to the people they're interacting with), but which are offensive to casual observers, which in turn can lead people who might otherwise have become a part of the community to decide that it's not for them. The classic example is two friends who call each other names for fun end up giving the impression that bigotry is tolerated within the community to people who aren't aware of that relationship.

Another thing I'd suggest adding is that when talking about why something has had to be deleted or locked, or an account has to be banned, behaviours are what should be commented on rather than individuals ("you have acted inappropriately" vs "you are inappropriate"). I talk a little bit about why this is important in my [recent article on community management](http://cheesetalks.twolofbees.com/usergroups.php).

The SSL certificate is now installed, I purchased a domain validation one rather than a simple self-signed cert as people kept asking for one.

Report any issues you find when using https :)

Hey, Liam. I've noticed some things that are a bit off with the admin CP.

When managing articles in dark theme the text box is not accessible:



Also, I noticed when managing articles by category (e.g. Action) the thumbnails are shown, as opposed to when you view all there are none and your left with error messages at the top.





Note: The themes are different because I first thought that was the cause, but that doesn't appear to be the case. I've also tested this both ways with Chromium and Firefox and so it doesn't seem to be browser related.

And can you please put the view all category at the top; we have a lot of categories :)

Oh, and one more thing. The like button doesn't seem to work for me in either browser.

Edit: The like button started working for me suddenly (unless Liam is just that good ;)) I'll just assume I was doing something silly.

I just tried to do some clean up on Xpander's (mostly excellent) Roccat Ryos MK Glow review but found that there was no submit button for changes. Or a comments box for that matter.

@hadbabits: The issues have been fixed apart from the Page 1 issue, you can access it tho just close the tab and open it :)

The like button is probably you have old cache somewhere :)

@Hamish I always forget something, Editing added, comments will take time to put in.

Stellar. Thanks, Liam :)

Okay guys we need a system for the admin review queue and the user submission queue that prevents people from overwriting each-others changes.

Was thinking something similar to what wordpress does and tell you that someone else is editing it along with the time they started with the option of unlocking it if it's really needed.

Although if someone has a better idea I'm all for it.

Just want to prevent wiping each others work.

In a shared calendar system that I wrote once, I implemented a warning if somebody tried to edit a field that somebody else had open, and when saving, showed you both and gave you the option of which one to keep. I don't think that the second part is very useful here, but some kind of notice that the edit page had been loaded by another user might be helpful (I guess this is the same as locking more or less)?

Alternatively, if you're up for some work, it looks like PHP can [patch strings from diffs](http://www.php.net/manual/en/function.xdiff-string-patch.php) and allow you to merge some concurrent changes automatically.

Quoting: CheesenessIn a shared calendar system that I wrote once, I implemented a warning if somebody tried to edit a field that somebody else had open, and when saving, showed you both and gave you the option of which one to keep. I don't think that the second part is very useful here, but some kind of notice that the edit page had been loaded by another user might be helpful (I guess this is the same as locking more or less)?

Alternatively, if you're up for some work, it looks like PHP can [patch strings from diffs](http://www.php.net/manual/en/function.xdiff-string-patch.php) and allow you to merge some concurrent changes automatically.

I would rather not get bogged down with merge systems as they can get rather messy and it could take me too long to get it right, that could be something when I have more free time.

Quoting: liamdaweI would rather not get bogged down with merge systems as they can get rather messy and it could take me too long to get it right, that could be something when I have more free time.

Yep. As I said, they can be a bit of work.