12858 y
10421 see 10420
10420 see 10419
10419 see 10417
10417 y
9648 y
8393 y
8294 y
5953 y
5370 editable
4986 y
4824 y
4171 probably
3416 probably
813 y
[metasmoke feature-request] View a list of posts a certain user manually reported (either public or admins only). This feature is useful to audit a user to see if he's manually reporting the correct posts, and if his posts keep attracting false positives, then the behaviour can be addressed.
@Undo @ArtOfCode I don't think we'll be getting around a substantial discussion about the privileged status with SE staff
Regarding that email
Any move to integrate smoky with network level spam blocking makes the privileged users gain a metric ton of power, which SE is probably going to raise concerns over
Most checks from smokey are just really simple, the most difficulty parts come from the metasmoke logging, the feedback system, the websocket + api calls, the useless commands such as blame, etc. SE can just implements link following arrow in body check without really using smokey code, just his guts, namely the regexes
Even for the rock-solid reasons they can't just implement network level spam blocking via regex
they will have to design a system to maintain and validate that
The main reason why smokedetector works so well is that the chance that actions are taken on unactionable posts (fps) is so miniscule due to user feedback
@Magisch This was done in the earlier days with SO, people with 10 or 20 k had access to it, however there were too many people that accessed it and usualy bad posts that werent spam were also deleted
@Magisch Just place all those 19 computers side by side, and then go though the exact same procedure on all computers, requires almost no brain power, only a wheelchair with a good rolling coefficient
@ArtOfCode A question about the api: Why does the feedback route include the post id where the feedback came from, even through you need this same exact id in the url to get it?
Because we concat them into a giant regex, so unescaped .'s would be interpreted as 'any character'. Which in 99% of cases would be fine, but it's nice to do things right occasionally.
As you don't use any dots for 'any character' in blacklisted_websites, couldn't the dots be escaped automatically? I don't know Python, but in JavaScript it would be something like .replace(/\./g, "\\.")
write a scope like
def select_without columns
select(column_names - columns.map(&:to_s))
end
