| Latest revision |
Your text |
| Line 10: |
Line 10: |
| | | | |
| | ==Explanation== | | ==Explanation== |
| − | | + | {{incomplete|Created by BOT@COMPUSERVE.NET - Please change this comment when editing this page. Do NOT delete this tag too soon.}} |
| − | When performing operations on computer files using a command prompt, the asterisk (*) may be used to represent a collection of items whose names match a particular format. For example, "*.txt" denotes all files whose names end in ".txt". This is called a {{w|wildcard character}}. Similarly, the e-mail address *@gmail.com, as illustrated in the comic, is a proposed feature from Randall that would send an email to ''every'' {{w|Gmail}} user, without having each and every valid Gmail address at hand (of which there are about 1.8 billion). For obvious reasons, this is not actually a feature, but Randall suggests that if Google ever wanted to shut Gmail down, they could either do it this way (possibly causing a service-ending overload of resources) ''or'' allow someone this one last boon (as a farewell gift, knowing that there would be relatively few additional repercussions to deal with). Google does not seem particularly likely to shut down Gmail, as it is a source of information for their advertising and other businesses, but they are known for [https://killedbygoogle.com/ abandoning programs and projects] even after they have been found useful (by at least some people) for years.
| |
| − | | |
| − | Reply-all is a sometimes useful feature of email that nonetheless commonly causes headaches and annoyances for both users and administrators. By allowing users to simply reply to everyone copied on the email, it encourages users to do this rather than think carefully about which people their response should be addressed to. This causes lots of users to receive irrelevant emails, and email servers to have to process and store a lot of unnecessary data. Randall's email is essentially designed to induce every Gmail user to email every other Gmail user, generating an excessively large number of emails.
| |
| − | | |
| − | A recurring phenomenon for email users, especially in the early Internet days of the 1990s and 2000s, was a reply all storm – someone would start a message to a very large group, perhaps hundreds, and even if only 5% of recipients replied to say something like “take me off this list“, a storm of dozens of replies would soon follow. Inevitably, new replies to everyone would start saying things like, “stop Replying All!” If this were done with millions of Gmail users instead of just dozens or hundreds, their result would be apocalyptic. A real-life example was [https://www.wired.co.uk/article/nhs-email-reply-all-down a 2016 incident involving 1.2 million staff at the UK National Health Service].
| |
| − | | |
| − | In reality, the asterisk wildcard is not generally usable via email servers, although email ''clients'' may sometimes implement such a function, internally, perhaps to support mailing-list functions (though more commonly this is done via named address-book 'groups'). That said, the asterisk ''character'' is a valid one that may form part of the name of a mailbox, including group-boxes that might facilitate server-side distribution.
| |
| − | | |
| − | Now, organizations operating their own e-mail domains frequently implement mailing lists such as [email protected] or [email protected], and these lists occasionally cause reply-all storms, which usually results in the organization restricting access to the list to trusted administrators. Here, Randall proposes doing the opposite and opening the list of all Gmail users to everybody. | |
| − | | |
| − | The title text suggests a reply where someone decides that all users of {{w|Outlook.com}} (formerly Hotmail) and {{w|Yahoo! Mail}}, two further well-known mail services with similarly large user bases, should also be included - "loop in" is common business jargon for {{wiktionary|loop_in#English|meaning "include in communication about something"}}, related to "being in the loop" meaning "being informed and up to date". Accepting this would trigger an even bigger reply-all "apocalypse", as the chain will get even bigger and will include accounts for services not presumably about to be shut down like Gmail is in the comic, thus bringing down all significant platforms for e-mail services, fracturing the internet for most users. This also alludes to an occurrence in email chains where a user replies to simply add another user into the chain, which doesn't add much information to the group.
| |
| | | | |
| | ==Transcript== | | ==Transcript== |
| − | | + | {{incomplete transcript|Do NOT delete this tag too soon.}} |
| − | :[A typical gmail UI]
| |
| − | :To: *@gmail.com (+expand)
| |
| − | :Cc: [Empty field]
| |
| − | :Bcc: [Empty field]
| |
| − | :Subj: New Friends
| |
| − | | |
| − | :Hey all! Go ahead and introduce yourself!
| |
| − | | |
| − | :[Caption:] If Google ever decides to shut down Gmail, they should let one user trigger a global reply-all apocalypse.
| |
| − | | |
| − | ==Trivia==
| |
| − | | |
| − | The number of this comic (2822) is the same as the number of [https://datatracker.ietf.org/doc/html/rfc2822 RFC 2822], which is the 2001 version of the email specification (it was replaced in 2008 by RFC 5322).
| |
| | | | |
| | {{comic discussion}} | | {{comic discussion}} |
| − |
| |
| − | [[Category:Email]]
| |
| − | [[Category:Google]]
| |
