Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • jami-project jami-project
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 155
    • Issues 155
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinuxsavoirfairelinux
  • jami-projectjami-project
  • Wiki
  • Technical
  • Name Server Protocol

Name Server Protocol · Changes

Page history
Update Name Server Protocol authored Jun 02, 2020 by Sébastien Blin's avatar Sébastien Blin
Hide whitespace changes
Inline Side-by-side
technical/Name-Server-Protocol.md
View page @ 73689f64
The protocol used by Ring to query and register a name is based on an
The protocol used by Jami to query and register a name is based on an
HTTP
[REST](https://en.wikipedia.org/wiki/Representational_state_transfer)
API answering requests with JSON documents and regular HTTP status
codes.
The public nameserver is hosted at `ns.ring.cx` and uses a blockchain as
The public nameserver is hosted at `ns.jami.net` and uses a blockchain as
its backend. Another implementation could use any other database or
directory service making the nameserver protocol reusable.
......@@ -74,7 +74,7 @@ username is returned if one is registered on the name server.
### Request
A request for the RingID `ring:29347542eb07159f316577e1ae16243d152f6b7b`
A request for the ID `ring:29347542eb07159f316577e1ae16243d152f6b7b`
is a `GET` request with
`/addr/`*`29347542eb07159f316577e1ae16243d152f6b7b`* as the URI.
......
Clone repository
  • 2.6 Displayed status
  • Choosing CRF value for encoder
  • Deprecated documents
  • Group chat feature (design draft)
  • Home
  • chatview i18n (design draft)
  • features
    • All features by client
  • guidelines
    • Banned Contact
    • Coding rules
    • Identifiers
    • Libringclient Coding Rules
    • Qt and QML coding guidelines
    • Qt and QML testing tools
    • UI and UX development
  • others
    • gsoc
View All Pages