9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] The Plan 9/"right" way to do Facebook
Date: Wed, 30 Mar 2016 18:53:58 -0700	[thread overview]
Message-ID: <20160331015358.6866EB834@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Wed, 30 Mar 2016 23:40:03 -0000." <8637r75ycs.fsf@cmarib.ramside>

On Wed, 30 Mar 2016 23:40:03 -0000 cigar562hfsp952fans@icebubble.org wrote:
> The Plan 9 Way
> ==============
>
> So, if social networking were to be re-designed from scratch, all over
> again, "the Plan 9 way", how would it be done?
>
> Obviously, the network would present itself as a file system.  :D  I
> should be able to browse and post content using shell commands at the
> command line.  Or, I could use the Acme plug-in to automate the process,
> just like using Acme Mail.  I'd be able to batch-up incoming or outgoing
> changes using tar(1) or hg, so I could work disconnected from the 'Net,
> too.  But... here's the tricky part...

cd /n/facebook
ls friends
...
cd requests
ls
johndoe
janedoe
...
cat johnedoe/about
ls johnedoe/posts
...
echo confirm > request/johnedoe/outgoing-request/me
echo hello > friends/johnedoe/message

cd /n/facebook/me/newsfeed
ls
1
2
...
cat 1/html 	# display raw html page
...
right-click 1/html	# view html page

# create a page with all your friends' latest posts.
htmlize friends/*/posts/latest | html-view

# look at the latest 10 messages from friends
ls -rt friends/*/messages/me | sed 10q | htmlize | html-view

:-)



  parent reply	other threads:[~2016-03-31  1:53 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-30 23:40 cigar562hfsp952fans
2016-03-31  0:12 ` Winston Kodogo
2016-04-01 17:44   ` cigar562hfsp952fans
2016-03-31  0:23 ` Kurt H Maier
2016-03-31  0:58   ` Winston Kodogo
2016-04-01 17:30   ` cigar562hfsp952fans
2016-03-31  1:53 ` Bakul Shah [this message]
2016-03-31  2:09   ` Lyndon Nerenberg
2016-03-31  2:59     ` Bakul Shah
2016-03-31 19:41     ` Steve Simon
2016-04-01 15:00       ` michaelian ennis
2016-03-31  2:17 ` Staven
2016-04-02  3:02   ` cigar562hfsp952fans
2016-03-31  5:24 ` lucio
2016-03-31  9:03   ` hiro
2016-03-31 10:17     ` David Pick
2016-03-31 11:16       ` Iain Watson Smith
2016-03-31 12:44       ` Kurt H Maier
2016-04-01 20:00   ` cigar562hfsp952fans
2016-04-01 20:40     ` Wes Kussmaul
2016-04-01 20:53     ` Giacomo Tesio
2016-04-02  9:32       ` hiro
2016-04-02  9:58         ` Richard Miller
2016-04-02 10:08           ` hiro
2016-04-03  2:30       ` [9fans] OT: Ubiquitous data vs. Reality, WAS: " cigar562hfsp952fans
2016-04-03  8:13         ` [9fans] OT: Ubiquitous data vs. Reality, Richard Miller
2016-04-08  3:25           ` erik quanstrom
2016-04-03 20:04         ` [9fans] OT: Ubiquitous data vs. Reality, WAS: Re: The Plan 9/"right" way to do Facebook Wes Kussmaul
2016-04-03 21:28         ` Winston Kodogo
2016-04-04 11:37           ` hiro
2016-04-04 23:53             ` Winston Kodogo
2016-04-03  4:42       ` [9fans] " lucio
2016-04-03 11:24         ` Giacomo Tesio
2016-04-03 11:44           ` lucio
2016-04-03  4:22     ` lucio
2016-04-03  4:32     ` lucio

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=20160331015358.6866EB834@mail.bitblocks.com \
    --to=bakul@bitblocks.com \
    --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).