autonomic-cooperative/autonomic.zone
Archived
5
0
Fork 0
Code Issues 15 Pull Requests 2 Releases Activity

Rename to follow ecosystem
Some checks failed
continuous-integration/drone/push Build is failing
Details

Browse Source
This commit is contained in:
Luke Murphy 2020-05-16 17:32:55 +02:00
parent 9f42ecaa77
commit 78ea06871a
No known key found for this signature in database
GPG Key ID: 5E2EF5A63E3718CC
1 changed files with 20 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

46
src/_posts/2020-04-23-dat-py.md
View File

@ -1,25 +1,24 @@
--- ---
layout: post layout: post
title: Datpy, the punk-to-punk protocol in Python title: Hyperpy, the punk-to-punk protocol in Python
description: A new Python implementation of the Dat protocol is cooking at Autonomic description: A new Python implementation of the Hypercore protocol is cooking at Autonomic
image: 2020-04-23-dat-protocol.png image: 2020-04-23-dat-protocol.png
category: technology, peer-to-peer, dat-protocol category: technology, peer-to-peer, hypercore-protocol
date: 2020-04-23 date: 2020-04-23
--- ---
# Datpy, the punk-to-punk protocol in Python # Hyperpy, the punk-to-punk protocol in Python
We're quite excited by the new wave of community-developed peer-to-peer We're quite excited by the new wave of community-developed peer-to-peer
technology. [Scuttlebutt], [Cabal], [Mapeo] and [Beaker browser] are inspiring technology. [Scuttlebutt], [Cabal], [Mapeo] and [Beaker browser] are inspiring
examples of software which show that technology can be built to operate without examples of software which show that technology can be built to operate without
running on centralised commercially-owned infrastructure (e.g. WhatsApp). running on centralised commercially-owned infrastructure (e.g. WhatsApp).
One of the underlying innovations for technologies such as [Cabal] is the [Dat One of the underlying innovations for these technologies is the [Hypercore
protocol], which is a way of describing how two computers can send information protocol], which is a way of describing how two computers can send information
to each other directly. The protocol is supported by the [Dat Foundation] and to each other directly.
developed as a community-based standard.
Today, the reference implementation for the Dat protocol is written in Today, the reference implementation of the Hypercore protocol is written in
Javascript. The Javascript ecosystem has proved to be remarkably flexible for Javascript. The Javascript ecosystem has proved to be remarkably flexible for
advancing this next generation of tools. Simple methods of publishing (npm advancing this next generation of tools. Simple methods of publishing (npm
publish), well-established distribution channels (the browser) and a publish), well-established distribution channels (the browser) and a
@ -30,29 +29,24 @@ However, there is a great need for other languages and ecosystems to benefit
from the tools and concepts that are being developed based on the reference from the tools and concepts that are being developed based on the reference
implementation. People from all walks of life need a working implementation in implementation. People from all walks of life need a working implementation in
their preferred language of choice. In response to this, we are seeing projects their preferred language of choice. In response to this, we are seeing projects
like [Dat Rust] and [C++ Dat] emerge. like [Datrs] and [Datcxx] emerge (please note, the Hypercore protocol was once
called the Dat protocol, see [this blog post] for more information).
Alongside these efforts, a member of Autonomic has begun to work on [Datpy], a Alongside these efforts, a member of Autonomic has begun to work on Hyperpy, a
Python-based implementation of the Dat protocol. The project proposes a roadmap Python-based implementation of the Hypercore protocol. The project proposes a
but offers no deadlines and receives no funding at current status. However roadmap but offers no deadlines and receives no funding at current status.
slowly, things are moving along. Further progress updates will be posted on
this blog as they come in.
You can find out more information on However slowly, things are moving along. Further progress updates will be
[datpy.decentral1.se](https://datpy.decentral1.se/) and please feel more than posted on this blog as they come in. All development is taking place on
welcome to join in and participate in the project if you have the time and [git.autonomic.zone/hyperpy].
energy for it.
All development is taking place on [git.autonomic.zone/datpy].
[scuttlebutt]: https://scuttlebutt.nz/ [scuttlebutt]: https://scuttlebutt.nz/
[cabal]: https://cabal.chat/ [cabal]: https://cabal.chat/
[mapeo]: https://www.digital-democracy.org/mapeo/ [mapeo]: https://www.digital-democracy.org/mapeo/
[beaker browser]: https://beakerbrowser.com/ [beaker browser]: https://beakerbrowser.com/
[dat protocol]: https://dat.foundation/ [hypercore protocol]: https://hypercore-protocol.org/
[dat foundation]: https://dat.foundation/about/foundation/
[philosophy of modularity]: https://mafinto.sh/blog/pragmatic-modularity.html [philosophy of modularity]: https://mafinto.sh/blog/pragmatic-modularity.html
[dat rust]: https://github.com/datrs/ [datrs]: https://github.com/datrs/
[c++ dat]: https://datcxx.github.io/ [datcxx]: https://datcxx.github.io/
[datpy]: https://datpy.decentral1.se/ [git.autonomic.zone/hyperpy]: https://git.autonomic.zone/hyperpy/
[git.autonomic.zone/datpy]: https://git.autonomic.zone/datpy/ [this blog post]: https://blog.datproject.org/2020/05/15/dat-protocol-renamed-hypercore-protocol/