|
Lots of things can be a signal of an article's popularity. Bookmarks, # comments, # people who have scrolled to the bottom, # downloads, # shares. In the interests of keeping things simple and consistent we've chosen to use rating as a surrogate for all of these since they are (generally) well correlated.
cheers
Chris Maunder
|
|
|
|
|
It would be interesting to see those extra metrics in the left-hand side bar (# shares, #people that scrolled to bottom).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
We are seeing quite a number of new QAs which contain some ordinary text, but no code. The only code to be seen is a single line containing:
#include
so it looks like the < after include is being taken as the start of a tag, but everything following is thrown away.
|
|
|
|
|
Yeah. This one is a bad one and it's related to our decision to switch to using a third party HTML sanitiser. We've relied on our own one for ages but it simply wasn't up to the task. The new one, however, has no patience, no humour, and not hesitation it hunting down and annihilating anything that looks like HTML that it doesn't agree with.
If someone pastes #include <stdio> without escaping the <'s then everything from thereon in will assume it's an HTML tag. It's not a white-listed HTML tag, though, so it gets nuked.
Either the poster needs to encode brackets, or wrap them in PRE blocks (where they get special treatment) or we don't bother and just switch to Markdown and don't allow any HTML at all. (which we briefly tried and everyone hated it.
...or we do what software devs always do and fork the code and hack it to our will. Instead of removing bad tags we'll work out a way to simply HTML encode them and convert blocked HTML tags into harmless Text nodes.
cheers
Chris Maunder
|
|
|
|
|
Is it possible to temporary switch back to previous solution while fixing this one ?
Newbies usually don't know how to use <pre> until their question is edited by someone else.
An Encode would be easier to handle.
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
). Phew.
Closed your unmatched parenthesis.[^]
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
The PRE block is not enough !
All what look like a tag need to be Encoded to prevent nuke.
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
ppolymorphe wrote: All what look like a tag need to be Encoded to prevent nuke
Nearly.
What now happens is that all known tags that are forbidden are removed, but the child nodes of that tag are kept (previously they were nuked). Unknown tags (eg #include <stdio>) will be HTML encoded.
If the tags are in PRE blocks then everything is encoded.
cheers
Chris Maunder
|
|
|
|
|
Looks great
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
#include <stdio> now works as expected.
cheers
Chris Maunder
|
|
|
|
|
I pasted a url to a youtube video into a message and had the normal text added to make it a hyperlink. However, all the letters were made lowercase and for youtube that link becomes invalid.
For example, pasted link:
href="https://www.youtube.com/watch?v=vzl0qrsdy_o"
working link:
href="https://www.youtube.com/watch?v=VzL0qrSDy_o"
Chrome on Win10.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Oh FFS. In 2016.
(And yes I'm aware of the W3C's stand[^]: Quote: URLs in general are case-sensitive (with the exception of machine names). There may be URLs, or parts of URLs, where case doesn't matter, but identifying these may not be easy. Users should always consider that URLs are case-sensitive
My bad. I will fix this up and keep my swearing to a minimum.
(Though I challenge Google to give me a single reason why case sensitivity of URLs has a place in this day and age. grumble grumble grumble)
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: Google to give me a single reason why case sensitivity of URLs has a place in this day and age.
It surprised me too. I suppose with so many videos this way they can reuse characters and get many more links out of the same alphabet.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
Chris Maunder wrote:
(Though I challenge Google to give me a single reason why case sensitivity of URLs has a place in this day and age. grumble grumble grumble)
www.somesite.com/findexactstring?text=AbcXyz&caseSensitive=1
|
|
|
|
|
It you are writing a message, it used to work like this: type away, click the Bold widget, and <b></b> gets inserted, with the input position between the tags - so if you typed, the characters went inside the bold tag. Similarly, if you clicked Bold and then Italic, you got <b><i></i></b> with the input inside both tags.
Now, you click a widget and the tags are inserted, but the input goes to either the beginning or the end of the text box - I'm not sure exactly when it decides which, it's mostly the start, but I got a couple of ends writing this - means that text doesn't appear inside the tags, and Italic isn't inside Bold.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
I agree, it is annoying !
Hope it is fixed soon.
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
All fixed.
cheers
Chris Maunder
|
|
|
|
|
|
I extrapolate results when testing. 
cheers
Chris Maunder
|
|
|
|
|
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
When using the code button to add <pre> tags around a block of code, the page jumps back to the top rather than remaining positioned where the tags are inserted.
|
|
|
|
|
Should be good now.
cheers
Chris Maunder
|
|
|
|
|
It certainly is.
|
|
|
|
|
|
Fixed. Will deploy soon.
cheers
Chris Maunder
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
