:wtf: How can this be so wrong??? (AKA the Discopocalypse thread)
-
@Dreikin Nah, I check certificates occasionally.
-
I'm on the list
-
@Boner
You're not welcome anymore.
-
@Boner said in How can this be so wrong??? (AKA the Discopocalypse thread):
I'm on the list
YOUR FAMOUS NOW
-
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
@Boner said in How can this be so wrong??? (AKA the Discopocalypse thread):
I'm on the list
YOUR FAMOUS NOW
@boner IS HUGE!
-
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
@remi said in How can this be so wrong??? (AKA the Discopocalypse thread):
And the typo part is hilarious also, because people that tend to swear a lot also usually don't write very well and do a lot of typos, while people that write very well usually tend to use precise words for precise reasons. So a filter like this will prevent a well-mannered person from using one banned word in a non-offensive context (e.g. "How can I determine the sex of my chickens?") while a ranting lunatic serial-offender will be able to pass all its hate without even noticing the filter because of the typos (e.g. "fuk u all niigers faggs").
Those who don't learn from 1995 AOL are doomed to repeat it.
More like ONLINE FAP OVER 'BREAST'
-
@Jaloopa said in How can this be so wrong??? (AKA the Discopocalypse thread):
More like ONLINE FAP OVER 'BREAST'
You're fapping to the red boob? Dude…
-
And how did they miss that mistake given all the stress testing we gave that feature with Belgium/elgiu?
Given that the original censor code respected word boundaries, my guess is that the new code was written from scratch without reference to the original code (in core) which would have been simply deleted.
Oh - and you're assuming they test things.
I believe it was initially implemented as a plugin. It sounds like there was enough demand and it's now a core feature.
No - the original was definitely in core, with talk of moving it to a module.
it never catches all variations of a single word (nigger is not OK but niggers is OK, buttuming they fix the "non-whole words" thing, but you could imagine other simple ways/typos to work around any other regexp);
:snigger:
Those who don't learn from 1995 AOL are doomed to repeat it.
-
Now I want to link to loads of articles about Scunthorpe on any Discourse forum I can find
-
@Jaloopa Don't forget Penistone and Cockermouth ;)
Edit: Oh, and this place in the Orkneys.
-
@PJH said in How can this be so wrong??? (AKA the Discopocalypse thread):
Like AOL in 1996, or Google in 2004?
Several websites running rudimentary obscenity filters have replaced the word "ass" with "butt", resulting in "clbuttic" for "classic" and "buttbuttinate" for "assassinate"
Is It Okay To Buttbuttinate a Nazi?
-
@RaceProUK said in How can this be so wrong??? (AKA the Discopocalypse thread):
Edit: Oh, and this place in the Orkneys.
Or you could talk about your holiday in Germany
-
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
Is It Okay To Buttbuttinate a Nazi?
Only with prior written consent.
-
@svieira This error....
Even ignoring the formatting, the list of words is stupid.
Also (and possible ) they're censoring queer?! UH OH!
-
@cartman82 said in How can this be so wrong??? (AKA the Discopocalypse thread):
wat?
Why is zip hard on linux?Because Jeff.
-
@boomzilla said in How can this be so wrong??? (AKA the Discopocalypse thread):
I believe it was initially implemented as a plugin. It sounds like there was enough demand and it's now a core feature
As expected, REimplementing it as a core feature improved the quality significantly...
-
@Jaloopa said in How can this be so wrong??? (AKA the Discopocalypse thread):
Now I want to link to loads of articles about Scunthorpe on any Discourse forum I can find
Meanwhile I wonder if gaming forums running Discourse have trouble talking about the Assassins Creed series...
Filed under: Now waiting for Buttbuttins Creed
-
@JBert said in How can this be so wrong??? (AKA the Discopocalypse thread):
Meanwhile I wonder if gaming forums running Discourse have trouble talking about the Assassins Creed series...
Knowing Discourse they probably get one toaster for each instance of ass.
-
@PJH said in How can this be so wrong??? (AKA the Discopocalypse thread):
@RaceProUK said in How can this be so wrong??? (AKA the Discopocalypse thread):
Edit: Oh, and this place in the Orkneys.
Or you could talk about your holiday in Germany
I see they decided the name wasn't enough to get their point across.
-
GItHub Issues not good enough? Why not Discourse?
Makes a change from introducing Discourse issues to GitHub, I guess.
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
@svieira This error....
Even ignoring the formatting, the list of words is stupid.
Also (and possible ) they're censoring queer?! UH OH!
But is WTF censored?
-
That part could probably be solved with a bot, like this2. (more examples).
@discoursebot move to #featureI don't think @discoursebot signed up to that!
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
GItHub Issues not good enough? Why not Discourse?
Makes a change from introducing Discourse issues to GitHub, I guess.
Woah, that's some great quote material:
While the idea seems simple, I don't understand why you would want to do this. The GitHub issue tracker is ... an issue tracker, with
- issue numbers
- milestones
- open/closed states (that don't block discussion)
- issues that can be referred to and marked as closed from commits
- automatic links to and from pull requests
- etc
Discourse is a forum. Why would you want to import issues into it?
No, the whole idea is to take discussion off site, so there are less bike shed discussions. Decisions can be carried forward without distractions.
It's possible that we've seen this before: it dates back from June 2016.
-
@JBert Yeah I noticed the date after posting.
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
@PJH said in How can this be so wrong??? (AKA the Discopocalypse thread):
Like AOL in 1996, or Google in 2004?
Several websites running rudimentary obscenity filters have replaced the word "ass" with "butt", resulting in "clbuttic" for "classic" and "buttbuttinate" for "assassinate"
Is It Okay To Buttbuttinate a Nazi?
-
@loopback0 speaking of
Did you see the last bit?
The site for this plugin is currently a dead link. Where are the installation instructions for this plugin?
Wups! It hasn't been put out to pasture so we'll eventually get it back up and running again. Any idea what happened here team? Did the DO droplet for this get caught in the recent purge?They went 80% of the way, but the last 20%, which might have made it work (having a bot which would do the migrate-this-issue-to-my-discourse-instance if someone on the right team pinged it) was too hard and fell by the wayside. Then this languished and dropped off of everyone's radar until someone came by to use it and noticed that it was +
-
@ben_lubar Great examples, but what's it from?
I'm not going to scour the Internet for Breastans...
-
@JBert My 30 seconds of search didn't bear much fruit, but I found this off some random blog:
(Again in the last full line ^)
-
@JBert said in How can this be so wrong??? (AKA the Discopocalypse thread):
@ben_lubar Great examples, but what's it from?
I'm not going to scour the Internet for Breastans...
I opened Dota 2's translation file and did a bunch of find and replace like two years ago.
-
Wait a second!
Mutual ass Pbuttion
-
@aliceif said in How can this be so wrong??? (AKA the Discopocalypse thread):
But is WTF censored?
Nah, just banned until 2990!
-
@svieira said in How can this be so wrong??? (AKA the Discopocalypse thread):
They went 80% of the way, but the last 20%, which might have made it work (having a bot which would do the migrate-this-issue-to-my-discourse-instance if someone on the right team pinged it) was too hard and fell by the wayside.
I'm sure we could figure something out for them... Hell, maybe they could pay for some hosting in return, so @accalia doesn't have to foot all the bills...
-
-
@aliceif said in How can this be so wrong??? (AKA the Discopocalypse thread):
The Great Leader's Greatest Fan?
-
speaking of, Meta decided to email me for some reason (not like I've been on the site since I made an account):
-
@Zecc said in How can this be so wrong??? (AKA the Discopocalypse thread):
Wait a second!
Gotta keep the swears out of your gay/tranny porn. Family friendly!
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
g
ay/tranny porn. Family friendly!
-
Today, on Bug Fixing with Jeff!
So, I've noticed that when using tags in Discourse, Google is getting confused and caching multiple different pages for the same tag, which is impacting search results
Hm, is this similar to <other report>?
No, I'm not trying to block all tag indexing, just eliminate the duplicates so I'm not pushing good results off the first page with bad duplicate results
Yeah, I think we should block all tag indexing
Where's a redshirt! We need to make this so, intern!
but, but...
-
Typical Discofix.
The first link goes to a blank page with JS enabled
I don't follow why there is a page indexed with match_all_tags=true... Did you figure out where Google is finding that link? It's not a valid query parameter, so it's thrown away. Is it from a plugin?A DISCODAY LATER
-
https://meta.discourse.org/t/502-bad-gateway-when-sending-pm-to-20-000-users/56801
I tried to PM all 20000ish of my TL0 users and it threw an error
PMing more than 100 users sounds dangerous
Export a list of users for this
That's the correct way to do it
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
@JBert said in How can this be so wrong??? (AKA the Discopocalypse thread):
Meanwhile I wonder if gaming forums running Discourse have trouble talking about the Assassins Creed series...
Knowing Discourse they probably get one toaster for each instance of ass.
I'm sure they complained, but "you can always just use custom CSS to hide those toasters, :not_welcome_here:"
-
@Tsaukpaetra said in How can this be so wrong??? (AKA the Discopocalypse thread):
speaking of, Meta decided to email me for some reason (not like I've been on the site since I made an account):
But did the email contain everyone's credentials?
-
"You are not permitted to view the requested resource" strikes again.
-
Discourse lets you have oneboxes as descriptions but then these break things later.
- https://meta.discourse.org/t/the-bulk-actions-dialog-in-the-moving-topics-scenario-shows-a-github-onebox-content-as-an-empty-rectangle/56788
- https://meta.discourse.org/t/updating-a-category-topic-fails-with-the-message-nomethoderror-undefined-method-inner-html-for-nil-nilclass-when-the-topics-contents-starts-with-a-github-onebox/56785
Not supported so we're not fixing it.
*CLOSED*
Now I have no idea why you'd use a GItHub onebox for a description, but if it's not supported then maaaaaaybe handle users trying it a bit better?
-
@loopback0
Heh, I didn't even notice that guy had multiple recent bug reports open. I guess we have another name for the anonyomizer pool
-
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
PMing more than 100 users sounds dangerous
HOW? WHY?
insert into pms (from, user_id, message) SELECT @fromUser, user_id, @message FROM user_id_split(@user_id_array)
Dangerous maybe to let a rando tl0 have access to bulk PMs, sure. But the act of sending out bulk PMs should not, in of itself, be dangerous.
You clueless dumbfuck poopsticks.
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
@loopback0 said in How can this be so wrong??? (AKA the Discopocalypse thread):
PMing more than 100 users sounds dangerous
HOW? WHY?
insert into pms (from, user_id, message) SELECT @fromUser, user_id, @message FROM user_id_split(@user_id_array)
Dangerous maybe to let a rando tl0 have access to bulk PMs, sure. But the act of sending out bulk PMs should not, in of itself, be dangerous.
You clueless dumbfuck poopsticks.
I mean, it could be dangerous, but shouldn't be dangerous to the forum software.
I'd be worried about whatever method you're using to send emails though - you're either gonna rack up charges or get your IP blacklisted for spam...
-
@Lorne-Kates said in How can this be so wrong??? (AKA the Discopocalypse thread):
But the act of sending out bulk PMs should not, in of itself, be dangerous.
It's probably not, but likely it is that discourse is processing each PM individually (including seeing if that user is online to send them a notification) and hitting an execution timeout limit.