From: cigar562hfsp952fans@icebubble.org
To: 9fans <9fans@9fans.net>
Subject: [9fans] Re: Plan 9 announcements on twitter
Date: Thu, 03 Dec 2020 03:09:41 +0000 [thread overview]
Message-ID: <86a6uva8lm.fsf@cmarib.ramside> (raw)
In-Reply-To: <864klqb1st.fsf@cmarib.ramside> (cigar562hfsp952fans@icebubble.org's message of "Mon, 16 Nov 2020 00:09:06 +0000")
cigar562hfsp952fans@icebubble.org writes:
> I actually think this is a REALLY good idea. We can use Twitter to
> stir-up mass hysteria about zombies from outer space planning to invade
...
> Sounds like a great way to promote our favorite operating system.
> Wouldn't you agree?
OK, so, obviously, I was joking. But the COVID-19 playbook does suggest
an interesting way to promote Plan 9. The steps required to do this
would be, roughly:
(1) Identify a worm that spreads from computer-to-computer and causes
ZERO harm, 99.9% of the time, but causes TOTAL DESTRUCTION AND DATA
LOSS in 0.1% of the computers it infests.
(2) Get video of people in a panic, screaming and wailing about all
their data being destroyed, and post it on the Internet.
(3) Post lots of tweets about how dangerous the worm is, re-tweet,
share, and generally hype-up the videos, along with dire
predictions about how the worm will destroy the Internet.
(4) Come up with a "test" to "detect" the worm, which has the following
three characteristics:
(A) Has a positive result whenever the worm is present;
(B) Has a positive result whenever the CRC32 of the system's
base-level page tables is less than 210210210; and
(C) Only runs in Plan 9, installed to a vm image or live CD, so
the test can only be run, in person, by a trained Plan 9
technician with physical access to the computer being tested.
(5) Release a new version of 9front named after the dreaded worm, and
tell people that installing it will make their device immune to the
worm.
It would require a little bit of coding, and a LOT of Tweeting, but if
9fans now have a Twitter account... creating a 9-demic is within the
realm of possibility.
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T3fd028fcf2eeb24c-M62191ae5f4fd8b4582fd9b9e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2020-12-03 3:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 21:36 [9fans] " Skip Tavakkolian
2020-11-13 3:50 ` Lucio De Re
2020-11-13 3:55 ` Don A. Bailey
2020-11-13 3:57 ` Calvin Morrison
2020-11-13 6:31 ` sirjofri+ml-9fans
2020-11-16 0:03 ` [9fans] " cigar562hfsp952fans
2020-11-13 18:45 ` [9fans] " Kim Shrier
2020-11-13 19:05 ` Skip Tavakkolian
2020-11-13 19:09 ` Skip Tavakkolian
2020-11-13 23:23 ` Pouya Tafti
2020-11-16 0:09 ` [9fans] " cigar562hfsp952fans
2020-12-03 3:09 ` cigar562hfsp952fans [this message]
2020-12-03 4:01 ` Lucio De Re
2020-12-03 7:25 ` Mart Zirnask
2020-12-03 8:50 ` Lucio De Re
2020-12-03 9:28 ` [9fans] " Bakul Shah
2020-12-04 9:37 ` Lucio De Re
2020-12-04 13:20 ` hiro
2020-12-05 9:12 ` Lucio De Re
2020-12-05 22:25 ` [9fans] " cigar562hfsp952fans
2020-12-06 3:56 ` Lucio De Re
2020-12-07 4:45 ` Devon H. O'Dell
2020-12-06 19:52 ` Ethan Gardener
2020-12-07 4:28 ` Lucio De Re
2020-11-18 2:34 ` [9fans] " ori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a6uva8lm.fsf@cmarib.ramside \
--to=cigar562hfsp952fans@icebubble.org \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).