Difference between revisions of "Talk:2337: Asterisk Corrections"

Explain xkcd: It's 'cause you're dumb.
Jump to: navigation, search
Line 32: Line 32:
  
 
Is that wrong? --[[User:NeatNit|NeatNit]] ([[User talk:NeatNit|talk]]) 07:27, 27 July 2020 (UTC)
 
Is that wrong? --[[User:NeatNit|NeatNit]] ([[User talk:NeatNit|talk]]) 07:27, 27 July 2020 (UTC)
 +
 +
:It seems to be centred in the more modern messaging environments. Geeks from a time before Twitter (heck, before the Web!) might have used s///-notation because it was (to them, i.e. people like me) clear, unambiguous and directly parsable by many who were using (say) Usenet. Even if they weren't coders themselves, they may have picked it up. And it was probably that little less 'snappy' and high volume. I mean, early days-of-Web wasn't exactly a competitor on those fronts, and old conventions and priorities still applied in spades, whether 'chat', IRC, a telnet/dial-up BBS or whatever.
 +
:Then came the rapid demographic changes of The Eternal September, and social-messaging revolutions zooming through Web 2.0 and (what I call, but I don't think is 'official') Web 3.0 which basically dumped the masses into the scene of the day and had more time to think up their new way of working than adopting or adapting holdovers from the now minority/archaic lines of communication (I still use [''#''] for feetnete, a lot; luckily it seems understandable enough, still).
 +
:For what it's worth, I understand the asterisk to be footnote-like. You can't actually edit in the referer at the typo/thinko (if you could, you would just correct it!) but there's an implicit one there after the eroor* you make. Which is supposed to be obvious at the time or, at least, when subsequently your attention is called to it.
 +
:So the follow-up opportunity notes a back-referenced correction of the *error, simply and sharply. If maybe not as unambiguously as you might imagine, but that's how it rolls in today's world, daddy-o! You grok my jive, good buddy? [[Special:Contributions/141.101.98.96|141.101.98.96]] 08:24, 27 July 2020 (UTC)

Revision as of 08:24, 27 July 2020


I think the only spot of the title text quote into which "witchcraft" makes a decent sentence is to replace "next": "I'd love to meet up, maybe in a few days? Witchcraft week is looking pretty empty" 173.245.54.161 01:02, 25 July 2020 (UTC) Me

I'd go with replacing "meet up". "I'd love to witchcraft, maybe in a few days? Next week is looking pretty empty." Orion205 (talk) 01:14, 25 July 2020 (UTC)
"I'd love to meet up, witchcraft in a few days? Next week is looking pretty empty." would be the third interpretation Multiverse42 (talk) 01:39, 25 July 2020 (UTC)
Or it could be "I'd love to meet up, maybe witchcraft a few days?" Munroe really loves to mess with people. A (talk) 01:43, 25 July 2020 (UTC)
If it can take out a whole sentence, "I'd love to meet up in a few days. [Magic & calendar shredding sounds, first sentence replaced with witchcraft] Next week is looking pretty empty." would be a pretty satisfying way I would do it IRL. My plan canceling capabilities are absolute witchcraft 172.69.71.82 08:53, 25 July 2020 (UTC)
Alternatively, witchcraft replaces maybe: "I'd love to meet up, [how about we practice] witchcraft in a few days?" 162.158.75.66 02:06, 25 July 2020 (UTC)

A splat? I didn't know that. IME it's just the messed up word resurrected to, summon a beech, auto corrected to the same wrong word. BTW the asterisk on an obsolete keyboard looked like a squished spider, thus 'splat.'

Asterisks can replace multiple words, right? Something like "I'd like to meet up, maybe witchcraft? Next week is looking pretty empty" could work, yeah? 108.162.246.135 04:36, 25 July 2020 (UTC)

"I'd like witchcraft? Next week is looking pretty empty." 162.158.159.18 12:35, 25 July 2020 (UTC)

I have to admit, before reading the title text I was expecting him to either have a sentence with a single replacement which could go in several locations (maybe both a noun and a verb), or a followup text implying that the obvious place to put those corrections wasn't the intended one. This time I feel a little disappointed; a sentence which feels natural with the replacement in several places would have been much more satisfying than one where it's a stretch to find any suitable place. Angel (talk) 10:14, 26 July 2020 (UTC)

does it necessarily have to replace a word? i find "I'd love to meet up, maybe witchcraft in a few days? Next week is looking pretty empty." to make more sense. 172.68.174.80 11:30, 26 July 2020 (UTC)


I'd go with replacing "meet". "I'd love to witchcraft up, maybe in a few days? Next week is looking pretty empty." --172.69.34.54 21:22, 26 July 2020 (UTC)

How about including the text before the quote (this is surely cheated a bit, but it's witchcraft so..): I like witchcraft to make it as hard as possible. "I'd love to meet up, maybe in a few days? Next week is looking pretty empty" Maybe someone can even figure out a version, where interpreting the quote after "witchraft", i.e. "witchcraft"", as part of the correction, could make sense. My knowledge of weird english sentence types is limited, since english is not my mother tongue. 162.158.92.146 22:20, 26 July 2020 (UTC) WhoCaresAboutMyNameh

I have NEVER seen splat used this way before. Is it really a thing? I have always used regex (s/wrong/correct). Vampire (talk) 03:28, 27 July 2020 (UTC)

I usually put the asterisk after the word, rather than before. For example:

There's smoke coming out of my cat, is that bad?

car*

Is that wrong? --NeatNit (talk) 07:27, 27 July 2020 (UTC)

It seems to be centred in the more modern messaging environments. Geeks from a time before Twitter (heck, before the Web!) might have used s///-notation because it was (to them, i.e. people like me) clear, unambiguous and directly parsable by many who were using (say) Usenet. Even if they weren't coders themselves, they may have picked it up. And it was probably that little less 'snappy' and high volume. I mean, early days-of-Web wasn't exactly a competitor on those fronts, and old conventions and priorities still applied in spades, whether 'chat', IRC, a telnet/dial-up BBS or whatever.
Then came the rapid demographic changes of The Eternal September, and social-messaging revolutions zooming through Web 2.0 and (what I call, but I don't think is 'official') Web 3.0 which basically dumped the masses into the scene of the day and had more time to think up their new way of working than adopting or adapting holdovers from the now minority/archaic lines of communication (I still use [#] for feetnete, a lot; luckily it seems understandable enough, still).
For what it's worth, I understand the asterisk to be footnote-like. You can't actually edit in the referer at the typo/thinko (if you could, you would just correct it!) but there's an implicit one there after the eroor* you make. Which is supposed to be obvious at the time or, at least, when subsequently your attention is called to it.
So the follow-up opportunity notes a back-referenced correction of the *error, simply and sharply. If maybe not as unambiguously as you might imagine, but that's how it rolls in today's world, daddy-o! You grok my jive, good buddy? 141.101.98.96 08:24, 27 July 2020 (UTC)