上位 200 件のコメント全て表示する 296

[–]picmip 638ポイント639ポイント  (47子コメント)

I took as many screenshots as I could of this shitty bot.

[–]mugsnj 158ポイント159ポイント  (37子コメント)

Damn, what's the regex for identifying a verb?

[–]SirBenet 104ポイント105ポイント  (22子コメント)

As the verbs will be past-perfect in this case, you could potentially list the most common irregular verbs then use the ed ending:

\b(arisen|awoken|backslidden|backslid|been|borne|beaten|become|begun|bent|beset|bet|bid|bound|bitten|bled|blown|broken|bred|brought|broadcast|built|burnt|burst|bought|cast|caught|chosen|clung|come|cost|crept|cut|dealt|dug|dived|done|drawn|dreamt|drunk|driven|eaten|fallen|fed|felt|fought|found|fit|fled|flung|flown|forbidden|forgotten|foregone|forgiven|forsaken|foretold|frozen|got|given|gone|ground|grown|hung|hanged|had|heard|hidden|hit|held|hurt|kept|knelt|known|gotten|laid|led|leant|leapt|learnt|left|lent|let|lain|lit|lost|made|meant|met|misspelt|mistaken|mowed|overcome|overdone|overtaken|overthrown|paid|plead|proven|put|quit|read|rid|ridden|rung|risen|run|sawn|said|seen|sought|sold|sent|set|sewn|shaken|shorn|shed|shone|shot|shown|shrunk|shut|sung|sunk|sat|slept|slain|slid|slung|slit|smelt|smitten|sown|spoken|spelt|spent|spilt|spun|spat|split|spoilt|spread|sprung|stood|stolen|stuck|stung|stunk|stridden|struck|striven|sworn|swept|swollen|swum|swung|taken|taught|torn|told|thought|thrived|thrown|thrust|trodden|understood|upheld|upset|woken|worn|woven|wept|won|wound|withdrawn|withheld|withstood|wrung|written|([a-z]+ed))\b

There'll still be false-positives, but it'll cut down on them.

[–]wOlfLisK 136ポイント137ポイント  (11子コメント)

|([a-z]+ed)

TIL Jared is a verb :P.

[–]Plasma_000 13ポイント14ポイント  (3子コメント)

street cred

snow sled

uncle ted

learning med

....

Large fries chocolate shake!

[–]dayzstu 23ポイント24ポイント  (7子コメント)

Now build a regex that doesn't match when the past-perfect tense verb is also an adjective.

"I took as many pictures as I could of broken bots."

"I poured more bowls than any man should of frosted flakes."

[–]marinuso 9ポイント10ポイント  (6子コメント)

You'd have to have the bot diagram the sentence to do this correctly, which is hard enough to do with proper grammatical sentences (i.e., this is something a university will spend years studying, not something your average Reddit bot writer is going to come up with at home in an afternoon), let alone with something like Reddit comments, which are going to be full of typos, abbreviations, colloquial forms etc.

[–]dayzstu 12ポイント13ポイント  (0子コメント)

Shhhhhh! I want to see the regex he puts together next!

[–]steamruler 4ポイント5ポイント  (1子コメント)

(i.e., this is something a university will spend years studying, not something your average Reddit bot writer is going to come up with at home in an afternoon)

I mean, we have previous examples of "impossible" challenges which has been solved by mistake because someone thought it was their homework.

[–]yetanothercfcgrunt 7ポイント8ポイント  (0子コメント)

Let's have CS students prove P is not NP before we tell them nobody's been able to figure it out. ;)

[–]CodeCaster 2ポイント3ポイント  (0子コメント)

Just copy the first Stack Overflow hit, it's upvoted so it should work!

[–]five_hammers_hamming 1ポイント2ポイント  (1子コメント)

For now. And for the next several decades. But twenty-five years from now, maybe there'll be widely-available libraries for things like that.

[–]panic 0ポイント1ポイント  (0子コメント)

That list of irregular verbs could of been much more complete.

[–]tehlaser 16ポイント17ポイント  (10子コメント)

I doubt you could regex it.

[–]speedster217 46ポイント47ポイント  (4子コメント)

Not a regular language, so no you cannot

[–]sketerpot 1ポイント2ポイント  (3子コメント)

Really? I bet there's a finite number of things recognizable as verbs, and alternations are (?:hella|very) regular.

[–]bradbeattie 19ポイント20ポイント  (2子コメント)

Consider words that are both verbs and nouns contextually. Cut. Run. Bolt. Record. Skate. Consider further that some sentences have multiple distinct parsings: http://cs.nyu.edu/faculty/davise/ai/ambiguity.html. Regex isn't the solution here.

[–]mugsnj 9ポイント10ポイント  (2子コメント)

That's the joke

[–]tehlaser 7ポイント8ポイント  (1子コメント)

It's also the counterexample.

[–]StandingByToStandBy 4ポイント5ポイント  (0子コメント)

You guys sound smart. I should add to the conversation.

I got nothing

[–]stult 0ポイント1ポイント  (0子コメント)

Oh so that's why my PoS tagger is such a PoS

[–]Zarlon 0ポイント1ポイント  (1子コメント)

Uhm.. why would you do that? regex a punctuation mark, space or end of line.

[–]mugsnj 0ポイント1ポイント  (0子コメント)

Check the comment I replied to. He properly used "could of" in a sentence. "Of" is a preposition, it will normally be followed by a noun or adjective. Could've/would've/should've are normally followed by a verb or adverb.

[–]JuniorGenius 17ポイント18ポイント  (1子コメント)

"would/could/should of" does not exist. What you're thinking of is "would/could/should've", a contraction of the word and have. Please do not use would of, could of, or should of.

[–]stone_henge 3ポイント4ポイント  (0子コメント)

It could of course have been a simple error on the programmer's side that is now fixed.

[–]ActualChamp 0ポイント1ポイント  (2子コメント)

How could the bot be written to avoid a comment like this triggering it? There seem to be a lot of ways this could be done wrong.

[–]xilefakamot 391ポイント392ポイント  (71子コメント)

Has the bot been shadowbanned?

[–]mythriz 362ポイント363ポイント  (41子コメント)

[–]74576480449124578456 404ポイント405ポイント  (37子コメント)

Perhaps he should of done a better job.

[–]oath2order 174ポイント175ポイント  (18子コメント)

"would/could/should of" does not exist. What you're think of is "would/could/should've", a contraction of the word and have. Please do not use would of, could of or should of.

[–]sorator 137ポイント138ポイント  (7子コメント)

What you're think of

[–]oath2order 88ポイント89ポイント  (5子コメント)

I hate myself right now

[–]sorator 13ポイント14ポイント  (3子コメント)

It's okay; everyone fucks up sometimes.

[–]Serinus 19ポイント20ポイント  (2子コメント)

I wonder what his teachers would of thought've that.

[–]benihana 1ポイント2ポイント  (0子コメント)

on the bright side, you've finally found that common ground with your dad you've been searching for the past twenty years!

[–]Henners1991 24ポイント25ポイント  (4子コメント)

He loosed alot of cred. Poor bot owner their probly really ambarassed by the affects this has on there career.

[–]TJHookor 7ポイント8ポイント  (3子コメント)

Goddamnit, my eyes.

[–]Henners1991 2ポイント3ポイント  (1子コメント)

When I see some oblivious chap type 'loose' instead of 'lose' I do succumb to a most murderous rage.

It's honestly my most irrational hatred. It instantly turns me sour.

[–]sandm000 0ポイント1ポイント  (0子コメント)

Right in the reading comprehension.

[–]flugsibinator 9ポイント10ポイント  (2子コメント)

He could of been great.

[–]oath2order 3ポイント4ポイント  (1子コメント)

the bot is now Ṭ̷Ř̥̤̤̻̥̥ͧ̏ͦ̋͑͡Ɨ̘͉̲̯̹͔̿ͯͦ͋͂͡Ǥ̸̷͈͇͉̟̫͚͖͉̼̰̱̩͔̙̖̱̌͑ͥ̐ͤͧ̂͌̃ͬ͟͜ͅĠ̟͓͇̺̭̮̇̄̍̃ͬͣ͂ͪ̽̃̀͜Ɇ̛ͦ̄̓ͪ̇̌̄̒̊̓̾̐͒͋ͭ̀͗̚͝҉̧͙͍̦̣̤͇͓͙̲͍̪̤̻͢ͅṜ͓̠̘̥̼̈́̌ͬ͜ͅḚ̬̯͎͉̙̉ͧ͆̕Ƌ̶

[–]jimbiscuit 2ポイント3ポイント  (1子コメント)

"would/could/should of" does not exist. What you're think of is "would/could/should've", a contraction of the word and have. Please do not use would of, could of or should of.

[–]randomyaho0 6ポイント7ポイント  (0子コメント)

If this becoming copypasta corrects some significant portion of the people making this mistake, it will be worth it.

[–]genericmutant 52ポイント53ポイント  (2子コメント)

I see what you of done there.

[–]smission 8ポイント9ポイント  (12子コメント)

Maybe you could offer to improve the bot?

[–]ChunkyLaFunga 8ポイント9ポイント  (0子コメント)

Maybe useless bots could stop wasting everybody's time and not post at all.

[–]justtoreplythisshit 5ポイント6ポイント  (8子コメント)

instead of testing for "could of", test for "could of ", or something like that.

[–]z500 8ポイント9ポイント  (6子コメント)

Or instead of correcting people, it controls a robot that randomly gives its original programmer a purple nurple.

[–]LyonesGamer 1ポイント2ポイント  (0子コメント)

Probably better would be to test for /\b(could|would|should) of\b/.

[–]brokedown 5ポイント6ポイント  (2子コメント)

You tried your best, but I guess your best wasn't good enough.

[–]mechakreidler 29ポイント30ポイント  (5子コメント)

The creator could of deleted the account.

[–]turtle_with_dentures 47ポイント48ポイント  (2子コメント)

More than likely shadowbanned. You see it a lot in /r/requestabot. People make these sort of bots all the time, there is a template in a sticky there for them. They are also "against rediquette" and considered spam bots. You'll find a ridiculous number of posts there asking for some sort of "reply on keyword" bot that is usually just posting annoying shit. Plus there is botwatch which tracks bot accounts, and many subs use that list to ban them before they ever even post.

So maybe he deleted the account, but reddit usually considers bots like that "spam" and just shadowbans them.

[–]Isogen_ 13ポイント14ポイント  (1子コメント)

The banning bots using a list a bot make is amusing.

[–]nimieties 7ポイント8ポイント  (0子コメント)

They're a traitor to their own kind!

[–]damian001 1ポイント2ポイント  (0子コメント)

Yes they must of deleted it!

[–]captmarx 1ポイント2ポイント  (0子コメント)

If not they definitely should of.

[–]Andrew_Carson 39ポイント40ポイント  (1子コメント)

Should of been

[–]StrategiaSE 29ポイント30ポイント  (0子コメント)

""would/could/should of" does not exist. What you're thinking of is "would/could/should've", a contraction of the word and have. Please do not use would of, could of or should of."

  • of_have_bot, 2016-2016, RIP

[–]lIlIIIlll 8ポイント9ポイント  (17子コメント)

F

[–]LordGalen 5ポイント6ポイント  (16子コメント)

U

[–]SheeEttin 6ポイント7ポイント  (15子コメント)

D

[–]SirBenet 162ポイント163ポイント  (38子コメント)

(w|c|sh)ould(n'?t)? of\b

[–]henrebotha 71ポイント72ポイント  (7子コメント)

I always forget about \b. I should make a point of using it more often. Usually I wrangle some solution like a negative lookahead (?!\w).

[–]Witonisaurus 19ポイント20ポイント  (23子コメント)

Just curious, can you explain that syntax or redirect me to where i could read on it?

EDIT: Im guessing its RegEx.

EDIT2: Gotta say, i love reddit. I made an edit saying i found out less than 2 minutes after posting, refreshed, and got 2 answers already, thanks! :)

[–]wOlfLisK 61ポイント62ポイント  (13子コメント)

It's regex. That one basically searches for a phrase that starts in either w, c or sh, then has ould (So could, would or should) with an optional n't (Question mark means optional) with the ' being optional because of mispellings. Then it needs to have an of and then the \b just makes sure it doesn't match with things like offer.

[–]pxan 4ポイント5ポイント  (11子コメント)

Is \b any white space? Not familiar with that one.

[–]lucasvb 39ポイント40ポイント  (9子コメント)

\b means "word boundary". It means a character that's not a letter near a word, so it means it's the start or ending point of a word.

For instance, "me? I don't mean anything" would have boundaries at "\bme\b? \bI\b \bdon't\b \bmean\b \banything\b"

[–]tymscar 11ポイント12ポイント  (0子コメント)

I LOVE to visualise stuff. It helps tremendously while learning something. Thank you for your comment!

[–]TrampeTramp 2ポイント3ポイント  (2子コメント)

I'm curious, the way you explained it wouldn't there be a boundary after don in don't? Or does apostrophe count as a letter while a question mark does not?

[–]lucasvb 1ポイント2ポイント  (0子コメント)

Good question. I think it will depend on the implementation and maybe the locale settings. You could and probably should explicitly include that character as a possible case.

[–]SybariticLegerity 0ポイント1ポイント  (0子コメント)

Apostrophe counts as boundary in some implementations and not others. It arises from the problem where we use it as both an apostrophe and a single quote.

[–]pxan 1ポイント2ポイント  (2子コメント)

Actually I thought of a question: does \b have an advantage over \s in this context?

[–]lucasvb 7ポイント8ポイント  (0子コメント)

Yes, because \s matches spaces, even though words can be preceded or followed by all sorts of stuff, like commas, periods, parenthesis, etc. Just read this comment again and notice how often words are not delimited by spaces.

[–]LyonesGamer 2ポイント3ポイント  (0子コメント)

/\s(\w+)\s/g.match("I love my dog, Spot. Dogs are classified by breed; his is German Shephard. Every day, we take a walk to his favorite place: the park.") matches ["I", "love", "my", "Dogs", "are", "classified", "by", "his", "is", "German", "Every", "we", "take", "a", "walk", "to", "his", "favorite", "the"].

/\b(\w+)\b/g will match every word.

So, to relate it back, if they'd done /\s(c|sh|w)ould(n'?t)? of\s/, it would miss, for example, a comment like "Well, he could of, but it wouldn't work."

[–]pxan 0ポイント1ポイント  (0子コメント)

Damn that's handy. Thanks.

[–]Nexic 0ポイント1ポイント  (0子コメント)

curious as well, I usually see \s for whitespace

[–]name456 7ポイント8ポイント  (0子コメント)

coming from /all, nice explanation

[–]SheeEttin 10ポイント11ポイント  (0子コメント)

Have a text parsing problem? Use a regex! Now you have two problems.

[–]PresN 7ポイント8ポイント  (3子コメント)

"Regular expressions". Just google that, there's literally thousands of websites- it's the standard way to do complicated parsing of text in pretty much any language.

[–]Voxel_Brony 5ポイント6ポイント  (2子コメント)

Well maybe not "complicated" parsing

[–]apparentlyimintothat 8ポイント9ポイント  (1子コメント)

And definitely don't use it to parse HTML...

[–]Voxel_Brony 3ポイント4ポイント  (0子コメント)

How did I know what it would be :)

[–]JBlitzen 0ポイント1ポイント  (1子コメント)

Bookmark http://www.regex101.com/, it's super useful. Build or paste in a regex sequence and it will break down each symbol for you.

[–]JepuJee 0ポイント1ポイント  (0子コメント)

https://www.debuggex.com/ is another pretty helpful tool for visualising regexes.

[–]Atario 2ポイント3ポイント  (0子コメント)

\b

Or "\>" for some of us

[–]FluentinLies 2ポイント3ポイント  (0子コメント)

You could of course have this sentence though.

[–]dizzyzane_ 3ポイント4ポイント  (1子コメント)

 __________________________
< (w|c|sh)ould(n'?t)? of\b >
 --------------------------
        \    ,-^-.
         \   !oYo!
          \ /./=\.\______
               ##        )\/\
                ||-----w||
                ||      ||

Cowth Vader vs RegEx - Ep VIII

[–]dizzyzane_ 0ポイント1ポイント  (0子コメント)

 __________________________
< (w|c|sh)ould(n'?t)? of\b >
 --------------------------
   \
    \
        .--.
       |o_o |
       |:_/ |
      //   \ \
     (|     | )
   /'\_   _/`\
    \___)=(___/

    TUX learnt REGEXP!

[–]Neebat 56ポイント57ポイント  (11子コメント)

It's too bad software bots are banned from /r/ShittyRobots

[–]invaderzz[S] 11ポイント12ポイント  (7子コメント)

That's where I was originally gonna post it.

[–]Neebat 46ポイント47ポイント  (5子コメント)

The ban was the right thing to do. Unfortunately, allowing software bots caused a lot of really low-quality posts.

[–]AjaxGb 56ポイント57ポイント  (4子コメント)

SpellingBot here!

I'm pretty sure you meant "low" instead of "lot".

of really lo[w] quality posts.

(83.2% confidence) | I'm just a bot | Questions?

[–]Grzechooo 18ポイント19ポイント  (0子コメント)

yeah I'm not falling for that one

[–]Vicyorus 2ポイント3ポイント  (0子コメント)

Oh, what an interesting b-SON OF A BITCH!

[–]KiraisukiA fatal exception has occurred on user 17 4ポイント5ポイント  (1子コメント)

Thanks for that, now I just spent the past 3 hours on that sub... Have my upvote.

[–]Neebat 4ポイント5ポイント  (0子コメント)

It has its good days and its repost days. So many reposts! But there is often something interesting mixed in.

[–]AcousticDan 24ポイント25ポイント  (17子コメント)

A little green with the RegEx I see.

[–]Reenigav 49ポイント50ポイント  (16子コメント)

Probably just doing:

If 'could of' in comment.text or 'should of' in comment.text or 'would of' in comment.text: 
      comment.reply(......)

[–]derleth 19ポイント20ポイント  (0子コメント)

The Scunthorpe Problem:

The problem was named after an incident in 1996 in which AOL's profanity filter prevented residents of the town of Scunthorpe, Lincolnshire, England, from creating accounts with AOL, because the town's name contains the substring cunt.[1] Years later, Google's filters apparently made the same mistake, preventing residents from searching for local businesses that included Scunthorpe in their names.[2]

The same kind of problem coined the fake "word" 'Medireview':

Nefarious users were sending HTML attachments that, when clicked, might run scripts and cause bad things to happen — for example, they might gain access to passwords or data without a user’s permission or knowledge. To protect its users, Yahoo scanned through all HTML attachments and simply removed any references to “problematic” terms frequently used in cross-site scripting. [...] This caused problems because, like in the Clbuttic error, Yahoo didn’t check for word boundaries. This mean that any word containing eval (for example) would be changed to review. The term evaluate was rendered reviewuate. The term medieval was rendered medireview.

[–]sharamall 40ポイント41ポイント  (0子コメント)

it's not the bot's fault, it's the programmer's fault. /r/botsrights

[–]cgimusic// TODO: Choose flair. 53ポイント54ポイント  (1子コメント)

Well, they could of done a better job at that.

[–]NAS89 24ポイント25ポイント  (1子コメント)

I banned this bot on /r/panthers day one for misinterpreting the exact same thing. It also didn't check to see if it had posted in a thread before and would originally reply to quotes of itself.

[–]gatstrap 13ポイント14ポイント  (0子コメント)

keep pounding that ban button

[–]Kaneshadow 26ポイント27ポイント  (15子コメント)

That's an obnoxious bot anyway

[–]tronald_dump 10ポイント11ポイント  (1子コメント)

it always cracks me up when grammar/spelling dweebs play grammar police.

you would think someone with such a hardon for english would understand that english is literally constantly evolving, and taking on new forms.

its not a business meeting. the point of communication is to get ideas across. 99.9% of people will understand what you mean if you say "shouldnt of". theres literally no reason to be a dick.

TL;DR: i remember caring about people on the internet's grammar...then i turned 13.

[–]stone_henge 2ポイント3ポイント  (0子コメント)

I only point grammatical errors out to people when they were made in an attempt to correct someone else's grammatical errors. That way I can feel both right and righteous.

[–]Banned_By_Default 3ポイント4ポイント  (2子コメント)

I remeber the bots a few years back. Like the bot that went wild when someone wrote alot instead of a lot.

Glad it died a horrible death.

[–]cvnaraos 1ポイント2ポイント  (0子コメント)

I never saw it in action - did it post the Alot from Hyperbole and a Half?

[–]mostfuckingbullshit 2ポイント3ポイント  (0子コメント)

You know whoever made it thought they were doing their part in the world, correcting and perfecting grammar, one reply at a time.

Then the camera pans to a lonely neckbeard who's sole source of confidence is correcting grammar on Reddit.

[–]openboatgeorgia 7ポイント8ポイント  (1子コメント)

Clbuttic!

[–]derleth 4ポイント5ポイント  (0子コメント)

Caused by coding practices stuck in Medireview times:

Coined accidentally by Yahoo! Mail in 2001, from medieval by automated string substitution of review for eval, a Javascript command short for evaluate

More information.

[–]igottashare 6ポイント7ポイント  (0子コメント)

This could offend the programmer. He should offload the bot. I would offer more solutions if I had them.

[–]Maccaisgod 11ポイント12ポイント  (0子コメント)

I always wanted to make a deliberately bad bot that corrected "than" to "then" and vice versa and just let it run wild and do it completely incorrectly and inappropriately

[–]Kaisogen 14ポイント15ポイント  (5子コメント)

I've always wondered, do these people not do extensive testing before releasing their bot into the wild? It's a good way to get banned quickly.

[–]OneWhoGeneralises 19ポイント20ポイント  (2子コメント)

I suppose the minor counterpoint to this argument would be that writing test cases is a skill of its own to developers. It's easy to think of and test the valid cases of any given algorithm, but designing corner cases comes from analysing the broader scope of the algorithm and from assessing invalid input.

In any case, it's not hard to spin up a tiny subreddit and let loose your bot there only, just a matter of inviting random users to stress test it then. Getting the bot in front of a user group is integral to testing, after all who doesn't love seeing a bot fail and fall flat on its face?

[–]atomheartother 3ポイント4ポイント  (0子コメント)

It could be fun to make a subreddit for people wanting to test their bots, creators could make threads like "My bot corrects incorrect use of "could of", can you break it?" and a bunch of people could try their hand at that. I know I'd post there.

[–]lucasvb 2ポイント3ポイント  (0子コメント)

Would the bot be banned if it worked properly, though?

[–]Grzechooo 0ポイント1ポイント  (0子コメント)

testing in production is best testing isn't it

[–]Dirkinator 4ポイント5ポイント  (0子コメント)

Didn't test the strings like he should of course

[–]meh_arrows 4ポイント5ポイント  (0子コメント)

The creator could of done a better job.

[–]UrMumsMyPassword 16ポイント17ポイント  (0子コメント)

This bot is the most pretentious bullshit I've seen in a while.

[–]ryeshoes 15ポイント16ポイント  (6子コメント)

I'm not sure what's going on here, but I'll shut up in case it could offend somebody. Sometimes I get over zealous and would officiate online debates when it's not my place to say anything. Hopefully an impromptu apology should offset any ill content.

[–]djqvoteme 26ポイント27ポイント  (2子コメント)

It offends me that people still think that their shitty comment bots should be allowed to roam free on reddit and be a nuisance.

[–]MisanthropicZombie 2ポイント3ポイント  (2子コメント)

I triggered this bot. I spent 10 minutes looking over my /r/writingprompts story trying to find the error I made. After loading an office app and ctrl+f'ing, I discovered the programming error.

[–]420666666024 2ポイント3ポイント  (1子コメント)

Did you hit cntrl-f and then search for could and quickly go through all the uses of that word or did you like, read through the whole thing over and over?

[–]MisanthropicZombie 2ポイント3ポイント  (0子コメント)

Yes.

First I looked at my post a few times, found some other errors, and then searched for "ould of" in WP Office and discovered I was not totally not badding at English.

[–]askeeve 2ポイント3ポイント  (0子コメント)

It would of course have trouble with seeing that this sentence is OK too.

[–]all2humanuk 2ポイント3ポイント  (0子コメント)

So we have grammar Nazi bots now? How fucking anal can people be?

[–]jld2k6 4ポイント5ポイント  (0子コメント)

I was berating this bot before it was cool!

http://i.imgur.com/Baw11g0.png

[–]jobehnar 7ポイント8ポイント  (1子コメント)

You could of course, use it like this maybe.

[–]dirtyhappythoughts 2ポイント3ポイント  (0子コメント)

Isn't there supposed to be a comma inbetween could and of there?

[–]iolex 4ポイント5ポイント  (0子コメント)

Ah yes, the interupting you're wrong and im right bot, but with a twist

[–]naphthoylindole 7ポイント8ポイント  (0子コメント)

The bot is pretentious as fuck too, whoever wrote it probably just completed 8th grade English and feels pretty damn smug about it. "Please talk how I want you to talk"

[–]sidcitris 3ポイント4ポイント  (0子コメント)

I was in a tread the other day where the same bot corrected "you should of course..." with the same message. Definitely needed more testing.

[–]Mike12344321 1ポイント2ポイント  (0子コメント)

It could offend me

[–]altogether_elsewhere 1ポイント2ポイント  (0子コメント)

You probably meant to say "only critique I could haveter..."

[–]lanismycousin 1ポイント2ポイント  (0子コメント)

Fuck these automated bots. They add nothing to the discussion

[–]TokyoXtreme 0ポイント1ポイント  (0子コメント)

Furthermore, the final "would of", "could of", and "should of" in the text should also have been surrounded by quotation marks.

[–]rightc0ast 0ポイント1ポイント  (0子コメント)

They coulda figured it out so easily too.

[–]SheeEttin 0ポイント1ポイント  (0子コメント)

I mean, most implementations support \W, so really the author has no excuse.

[–]moeburn 0ポイント1ポイント  (0子コメント)

I got in a fight with my grade school teacher because she insisted contractions of "have" such as could've or should've aren't real words and do not exist and children should be scolded for using/writing them.

[–]TheDetective13 0ポイント1ポイント  (0子コメント)

Please include the Oxford Comma Mr. Crappy Bot.

[–]Craboulor 0ポイント1ポイント  (0子コメント)

He could of course be stupid. Like myself not typing commas.

[–]arnedh 0ポイント1ポイント  (0子コメント)

This could've course gone badly in many ways.

[–]yeahbert 0ポイント1ポイント  (0子コメント)

A friend messed up his referral analysis by checking for t.co (twitter) in the host which also matches reddit.com. It took a while for him to find out why he had a 300k spike and could only find a handful of tweets about the page. I'm sure this is happening in quite a lot companies right now.

[–]cirryus 0ポイント1ポイント  (0子コメント)

Please do not use would of, could of course have this sentence though.

[–]taidg 0ポイント1ポイント  (0子コメント)

Even testing for an empty space would of course still be problematic in summer cases.

[–]cdb 0ポイント1ポイント  (0子コメント)

/\b(c|sh|w)ould of\b/i

This doesn't account for sentence structure but w/e.

[–]OnSnowWhiteWings 0ポイント1ポイント  (0子コメント)

If languages are always evolving, then why do so many people fight tooth and nail to defend it as a stagnant one?

[–]AnorhiDemarche 0ポイント1ポイント  (0子コメント)

I didn't know this sub existed but I'm glad the poor quality of this bot is being discussed. It got triggered by me saying "would often" in /r/sydney.

It wouldn't be quite so awful if there was a way to report bugs to the person who made it.

[–]PapiDimmi 0ポイント1ポイント  (0子コメント)

I was immensely confused; I kept checking the comment for “could/would/should of,” but then I read the title.

[–]AbsalomQuinn 0ポイント1ポイント  (0子コメント)

Oh shit, I got wrongly corrected by this bot too