WTH is wrong with ■■■■■■■?
-
It seems to me that Belgian should be censored, too; they're highly offensive.
I'm offended by that remark.
-
And here I thought it was done simply because it was funny because of the H2G2 thing, rather than anything else.
After all, we do a lot of things for some definition of fun around here...
... and for
testingabusing new Discohorse functionality.The name of the Glorious Kingdom I call my Homeland was added to the censored word list for both reasons.
-
oh. on closer inspection i see you already found out about that
Hands up, anyone who's surprised that using other characters easily evades the filter.
Thanks for identifying yourself; please report to your local recyling booth ASAP.
-
easily evades the filter.
Note: even Jeff has said that the filter is a bad idea that won't work, but put it in as what I assume was a customer (vs non-paying discourse host) was requesting it (and I can totally see PHBs wanting something like that if they ran a company forum).
-
If you run a site that really wants to censor that sort of thing and people go out of their way to avoid it, they get suspended / banned. They obviously knew what they were doing. Problem solved.
Or you have fun with it like we did.
-
Note: even Jeff has said that the filter is a bad idea that won't work
Right. And anyone here for any length of time should be presumed to be able to figure that out or already know it. Actually testing it seems superfluous.
-
If you run a site that really wants to censor that sort of thing and people go out of their way to avoid it
I found out that in Wizard101, people just used entirely different words. "Crop" looks close enough to "crap" everyone just said that instead.
-
Actually testing it seems superfluous.
but at first word borders weren't enforced, as linked earlier:
https://meta.discourse.org/t/word-censor-butt-vs-button/20968And here is where they started:
https://meta.discourse.org/t/word-censor-butt-vs-button/20968/18
-
but at first word borders weren't enforced, as linked earlier:
Yes, I know. I would thus assume that no attempt was made to stop people trying to evade filters by using pipe instead of lowercase l, or foreign-alphabet characters that look like English ones, and that any such evasion would work.
-
And so another developer fell into making a clbuttic mistake. You'd buttume Jeff, having been around for a while, might have come across this one before...
Or if not the story here, he surely would have heard of S****horpe already?
-
I believe at some point @sam or @riking expressed surprise that this feature was even used here, expecting this to be the last place to use it.
More or less surprised than learning that anybody at all uses this shitty broken forum software?
-
@riking expressed surprise that this feature was even used here, expecting this to be the last place to use it.
Libel and slander
-
Actually testing it seems superfluous.
It was more of finding out which esoteric stuff broke it.
c.f.
fa-spin
.
-
It was more of finding out which esoteric stuff broke it.
No, I meant today, not when you added the filter.
-
Wait, censoring doesn't work in code blocks?
If it did, wouldn't we all be complaining about how Discourse screwed up our code and how it should know better than to apply the censorship filters to code blocks?
-
Of course we would, this is TDWTF!
-
A rollercoaster gives you the illusion of danger without any danger.
The danger might be really small, but there is danger.
There were an estimated 1,415 injuries on amusement park rides in 2011, according to a report prepared by the National Safety Council Research and Statistical Services Group for the International Association of Amusement Parks and Attractions (IAAPA). Park visitors took 1.7 billion rides that year.
Those figures are for fixed amusement park rides, not traveling carnival rides. The number of deaths that year was not available, but one of them occurred at the Darien Lake theme park and resort in Upstate New York when an Iraq War veteran died on the Ride of Steel roller coaster.[1]
The information there puts the risk of injury from a rollercoaster at about 1 in 1.2 million. Though, as noted, that is just for fixed amusement park roller coasters. No idea how roller coasters at carnivals would affect that.
By delving further into his studies, Smith has discovered that injuries from roller coasters are far more common than deaths. With over 52 deaths tied to roller coasters that were logged in reports from the Consumer Product Safety Commission between 1990 and 2004. Unfortunately the Consumer Product Safety Commission no longer tracks data associated with deaths and roller coasters. Therefore it is generally up to media outlets to produce information pertaining to recent deaths from amusement parks.
…
According to the Association of Amusement Parks and Attractions, the chances of dying on a roller coaster fall between 1 in 24 million.[2]
I wouldn't say rollercoasters are risky, but I wouldn't say that they are without danger either.
-
According to the Association of Amusement Parks and Attractions, the chances of dying on a roller coaster fall between 1 in 24 million.
Between 1 in 24 million and what?
-
@abarker said:
According to the Association of Amusement Parks and Attractions, the chances of dying on a roller coaster fall between 1 in 24 million.
Between 1 in 24 million and what?
They didn't specify. I'm guessing they meant, "The odds of dying on a roller coaster are 1 in 24 million." Bad grammar is bad grammar.
-
the chances of dying on a roller coaster fall between 1 in 24 million.[2]
between one in 24 million and what exactly? that's only one endpoint....
-
between one in 24 million and what exactly? that's only one endpoint....
Just shy of an hour before you:
Between 1 in 24 million and what?
no to acknowledge this (to be fair at that amount of time and one post between them is only kinda a hanzo)?
-
-
-
it's certainly an appropriate @accalia coming from the one who started the whole thing
-
@abarker said:
the chances of dying on a roller coaster fall between 1 in 24 million.[2]
between one in 24 million and what exactly? that's only one endpoint....
Probably 1. Possibly 0, though.
-
Between 1/24M if you're only getting on, and roughly 1/1 if you've just skyrocketed out of a loop-the-loop.
-
I used to make things that did that in Rollercoaster Tycoon. The game actually had sufficient smarts to care if you did that.
-
Note: even Jeff has said that the filter is a bad idea that won't work, but put it in as what I assume was a customer (vs non-paying discourse host) was requesting it (and I can totally see PHBs wanting something like that if they ran a company forum).
Our company has quotes in our bugtracker that can be added by the users (dev/qa/etc).
After it existing for ~10 years, some new PHB saw one quote she was offended by (likely containing "crap").
Now there is an "approved" flag and these offensive words are no longer shown.
The PHB is no longer here, so once I find some write credentials to the DB, I'm going to approve them .
-
Note: even Jeff has said that the filter is a bad idea that won't work, but put it in as what I assume was a customer (vs non-paying discourse host) was requesting it (and I can totally see PHBs wanting something like that if they ran a company forum).
And now people are trying to use the censored words to stop spam...
(Someone was really tenacious in posting a particular phone number, but the real fix is sending the title to Akismet)
-
but the real fix is sending the title to Akismet
Wasn't one of the problems that the title of posts wasn't actually being screened?
-
Yeah, it got fixed by adding the title to the response body \n\n.