-
• #16752
We cached page views until someone replies.
The views are recorded, but you don't see them updated until a reply has been made.
-
• #16753
Cheers Boss!
-
• #16754
Cheers for what? I mean for the Twitter rules or for replying?
Just asking ehh, before you may misunderstand me. -
• #16756
Like raaaiiin.
-
• #16757
You're only explaining that because you have fetish dreams about him.
-
• #16758
Could you make the version history viewable?
-
• #16759
Technically yes, but of course it is never that simple.
There are a lot of good reasons people edit things, from removing personal information (a phone number or email left in an advert) to removing an insult said in a moment of heat that they now regret. But perhaps the best reason not to is that people may have indulged in defamation, corrected themselves, but if the historical version were still visible and uneditable then they could continue to be held to account for that.
The only way to protect users from themselves is to visibly treat delete as delete.
Yet, the only way to protect users from other users is to not actually delete in the majority of circumstances, just to hide.
What this ultimately means is that the database table called
comments
doesn't hold the comments themselves just the idea that someone posted a comment at some point in time on some item (conversation, event, etc), and a table calledrevisions
actually contains the comment body itself.That
revisions
table is an append only table, so every edit, every revision of a comment... is stored as a brand new row. And then the latest one is marked as the current one. Whichever one is marked as current is the one shown on the UI. But all of the rest remain along with the IP addresses and user agents used, etc, and if there are disputes about classifieds, or the police get in touch about stolen bike parts being offered, etc... then we have this forensic history of all that was said, by whom, from where, etc.But showing that to the world? It's a different can of worms. I tried to balance it by simply storing it and not showing it.
-
• #16760
makes sense, thanks.
-
• #16761
The first reply is the one that gets emailed out as a notification.
If you're going to do the dance of being offensive and spelling badly, the second edit is the place for that ;)
-
• #16762
Amazing
-
• #16763
so first one nice, 2nd one horrible, 3rd one what you want the world to see. Got it.
-
• #16764
Much like auto erotic asphyxiation.
-
• #16765
haha. rep, etc.
-
• #16766
Hi can someone please change the title of - http://www.lfgss.com/conversations/286433/#comment12968431
to Mixed Campag Groupset and Mavic Wheels . Thanks -
• #16767
go up to first post, look over to the right hand side and hit edit conversation button
you can make amendments that way -
• #16768
Thanks Dicki, all sorted.
-
• #16770
Nah, that's too much like hard work.
I've banned him and deleted all of his adverts.
-
• #16771
@Velocio maybe that RealSteel chap needs a bit of a reminder too?
http://www.lfgss.com/conversations/285781/#comment12968992 -
• #16772
I have "reminded" him too.
By banning him and deleting all of his comments, etc.
-
• #16773
I reminded him in one of his threads a couple of days ago, the silly sausage!
-
• #16774
Shit. Did anyone have the chance to offer him fiddy dorrah for that Leader BSO mountain bike?
-
• #16775
I knocked my mouse when creating a thread, accidentally posting it, then when I tried to edit, a duplicate thread was created.
I thought I could close one thread and re-open, once my text was ready then discovered I couldn't.
Basically: opened two useless threads that never contained anything for sale in them - please delete.
Apologies & Thanks.
Name linking follows Twitter rules... as in, we use the same matching code as Twitter for their matching, and their usernames do not allow anything other than alphabet, numerics and a very small selection of other characters (which doesn't include &).
It was also how some people avoided being @mentioned because they put non-printing unicode in their username (though unfortunately abuse of that has meant I've now disallowed that).