From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] 9p.zone: Public 9P Registry Services
Date: Tue, 26 Jan 2021 10:01:35 -0500 [thread overview]
Message-ID: <DA2C51C0-5851-478B-BFC3-C4B0E3FADE52@stanleylieber.com> (raw)
In-Reply-To: <3B6CCB77C6A1EEA232881C2083C929CE@sirjofri.de>
On January 25, 2021 6:50:07 AM EST, sirjofri+ml-9front@sirjofri.de wrote:
>Hello all,
>
>we haven't announced it here, I believe, so here it is:
>
>9p.zone is a public registry service for 9p services, OS agnostic.
>This means, it works for Plan 9, 9front, inferno, basically all 9p
>capable systems can use the registry. The project is public, so it's
>meant for public services and everyone can announce their services in
>this registry.
>
>While the center of 9p.zone is the registry itself (CORE services), we
>also plan to do other services as well (called EXTRA services). This
>services should help others to build great 9p stuff for the community,
>without the need to do everything. For example, we plan to build
>public auth services for free that can be used as a SSO service for
>other 9p services built by YOU.
>
>Furthermore, the old gridchat (from 9gridchan.org, which is basically
>shut down) is also inside this domain (chat.9p.zone). The whole
>9p.zone will become a new grid system that's free and public.
>
>More information about the registry is available via http://9p.zone .
>Feel free to contribute your public services.
>
>
>sirjofri
>
>
this is cool!
suggestion: the main page should explain clearly how to extract information from the registry.
sl
prev parent reply other threads:[~2021-01-27 9:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 11:50 sirjofri+ml-9front
2021-01-26 15:01 ` Stanley Lieber [this message]
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=DA2C51C0-5851-478B-BFC3-C4B0E3FADE52@stanleylieber.com \
--to=sl@stanleylieber.com \
--cc=9front@9front.org \
/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).