9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Aleksandar Kuktin <akuktin@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Web Gardens
Date: Tue, 13 Oct 2015 00:43:19 +0200	[thread overview]
Message-ID: <20151013004319.11d0e611@ikilid> (raw)
In-Reply-To: <7A773810-49DE-44E8-96D4-8E6F56A247C9@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>On Mon, 12 Oct 2015 17:57:16 +1300
>Andrew Simmons <kodogo@gmail.com> wrote:
>
> As a diversion from the discussion of the existential essence of
> Javascript, could I ask the group for a view on the meaning of the
> term "Web Garden"? I was just asked about this in a job interview.
> Supplementary question - how would you implement a Web Garden in
> Plan9?

How do you call isolated ecosystems put up by the big players
(Facebook, Tweeter and such) that hold all the data within and disallow
linking to that data from the outside? I seem to remember "Web Garden"
was used, but it could also be a "Walled Garden"..

- -- 
Svi moji e-mailovi su kriptografski potpisani. Proverite ih.
All of my e-mails are cryptographically signed. Verify them.
- --
You don't need an AI for a robot uprising.
Humans will do just fine.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBAgAGBQJWHDeHAAoJEKa4cgqNx31/pWcP/3i7rBawmHLFLnl6m5jB6hMb
HDaa2qDGrum3COn94sukeKApcUUmCJcA8HrWZryctfzT+5JAK/1XnfSdi5X3oRJv
hJY2P1a/aW8y9aOXyE6xh4e2h586mU5YOvpN9sY6oltSvB4K+8SgBxQ3ib1KXQtf
2vIuOTpo1d0bvXdI67qbfoj3ewY094FvLkPDDsLTV4f5Qz0ICJYt0o2IdvnUfUtW
isWAA352ujsxrItJ9dvUSSSSRRhIpihKB1ufdIE//DvOEb9ZOcIyXdNYlpOKwHgd
GutOBvj6IakYA6ORZpILCLT93E+iHP83AnLMWq3orW6X32hkQHQoWlxzASDN0TtS
zFork2otQnaQImgZtSukH4aBlYemqvZqkqz07haleSEJIuuZgZM/geBmLLZgFTA7
W0QPsP7vEfbm7uGFGtu7oEzdNMLQNiFTtpKQo4f70WGBjOQpcddAPVnbilXcLTnv
wYs+U0k1pBRMyLtHMhWza2elx6D96AmahMr1AaSjskPvDVaGMcvyP9NkAGny9C7x
/ma1D1N995YWuPU8QEK9uXR0j2owBPp5Oh3mv2Eoy9GIpMjTNXRJNRGD3RUATjYm
jtiBWbd0C3EpIHx11ucJ3/lr6vxE8PHGjih2Vp20J7vkbYQHRaF8NXoDsKXObnFw
aC7pcWHF0eUln9KxQtl+
=KDva
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2015-10-12 22:43 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12  4:57 Andrew Simmons
2015-10-12  6:55 ` Skip Tavakkolian
2015-10-12  8:18   ` hiro
2015-10-12  9:49   ` Staven
2015-10-12 10:11     ` Charles Forsyth
2015-10-12 10:55     ` Steve Simon
2015-10-12 12:29     ` Anthony Sorace
2015-10-12 16:13 ` Kurt H Maier
2015-10-12 20:02   ` Andrew Simmons
2015-10-16  2:10   ` erik quanstrom
2015-10-16  3:48     ` Kurt H Maier
2015-10-16  3:53       ` Prof Brucee
2015-10-17  1:51         ` Jeff Sickel
2015-10-17  4:44           ` Winston Kodogo
2015-10-18 15:41       ` erik quanstrom
2015-10-18 18:11         ` hiro
2015-10-12 22:43 ` Aleksandar Kuktin [this message]
2015-10-13  8:15   ` Charles Forsyth
2015-10-14  3:29     ` Lyndon Nerenberg
2015-10-14  8:32       ` Charles Forsyth
2015-10-14  8:35         ` Charles Forsyth
2015-10-14 15:25           ` Andrew Simmons
2015-10-14 16:34             ` Skip Tavakkolian
2015-10-15  6:22           ` Lyndon Nerenberg
2015-10-15  6:21         ` Lyndon Nerenberg

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=20151013004319.11d0e611@ikilid \
    --to=akuktin@gmail.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).