Thanks! Fixed with 77982f9e8a92f97a02aea5084f7d475bd9a42354.

There are a number of small unreleased fixes. I think we should slowly
prepare a 1.0.1 release. This would only contain editorial fixes and no
change to the encoding itself.

If you have any further suggestions or find more typos, let them be
known.

-pukkamustard

Bruno Victal <mirai@makinata.eu> writes:

Hello,

I'm very happy to announce the release of version 0.2.0 of ERIStekt - a
Firefox extension for working with ERIS. This version includes support
for an initial peer protocol. Blocks can be transported from remote
peers using the ERIS CoAP protocol over WebSockets.

The extension is available for installation from Codeberg:

https://codeberg.org/eris/eristekt/releases/tag/v0.2.0

Note that ERIStekt is no longer available on the Mozilla store (we can
publish updates quicker and Mozilla is a bit skeptical about our build

Dear followers of ERIS,

I'm happy to announce an initial version 0.1.0 of ERIStekt, a browser
extension for encoding and decoding ERIS content.

The source code is available on Codeberg:

https://codeberg.org/eris/eristekt

The extension can be added to your Firefox-based browser from the
official Mozilla store:

https://addons.mozilla.org/en-US/firefox/addon/eristekt/

Dear followers of ERIS,

I'm happy to announce an initial version 0.1.0 of oebstly, a
command-line tool for working with ERIS encoded content and managing
blocks.

The source code is available on Codeberg:

https://codeberg.org/eris/oebstly

The preferred means of installation is from source. Binaries and Debian
Archives for x86-64 Linux are provided as convenience.

Hello,

I'm very happy to announce the release of python-eris version
1.0.0. python-eris is a Python implementation of ERIS.

Source code: https://codeberg.org/eris/python-eris
Documentation: https://eris.codeberg.page/python-eris/
PyPi: https://pypi.org/project/eris/

To install python-eris with pip:

```
pip install eris

Very nice! Thank you for sharing.

I've added your Common Lisp implementation to the list of
implementations at https://eris.codeberg.page/.

Regards,
pukkamustard


ykonai <mail@ykonai.net> writes:

> Hello,
>

Hello,

On behalf of the ERIS maintainers, it it my great pleasure to announce
the release of ERIS v1.0.0:

https://codeberg.org/eris/spec/src/tag/v1.0.0

ERIS defines an encoding of arbitrary content into a set of uniformly
sized, encrypted and content-addressed blocks as well as a short
identifier that can be encoded as an URN. The content can be reassembled
from the blocks only with this identifier

The rendered specification is available at http://purl.org/eris .

Hi!

I'm a keen follower of the Irdest project and personally interested in
LoRa. Thanks for your mail!

Katharina Fey <kookie@spacekookie.de> writes:

> In the best case Lora radio environment in the case of attempting to
> transmit a standard 1KB ERIS frame over Lora using reasonable framing
> and the maximum permissible 242byte MTU, frame transmission would
> require being split over 5 Lora Messages, which must be separated by
> (at minimum) 2 seconds each. This would require at least 10 seconds to
> transmit any Ratman message regardless of actual size.

Hello ERIS,

The Guile (https://codeberg.org/eris/guile-eris/) and OCaml
(https://codeberg.org/eris/ocaml-eris/) implementations now support
random-access decoding. That means that users can read specific
bytes at given offsets from some encoded content while de-referencing
only a minimal amount of blocks.

Applications include seeking in audio/video or detecting file-type with
some magic bytes at fixed position. See also an initial draft of ERIS-FS
(https://codeberg.org/eris/eer/pulls/2) - an encoding of a file system
that is optimized for ERIS (allows de-duplication of files) which
requires such random-access.

Hello,

It is my great pleasure to announce the release of ERIS v0.4.0:

https://codeberg.org/eris/spec/src/tag/v0.4.0

The rendered version is available at http://purl.org/eris .

This version contains significant changes to the encoding itself and to
the specification document. We hope to have addressed the feedback and
issues brought up towards version 0.3.0 of the specification. In
particular we hope to have addressed the issues raised during the Quick
Security Evaluation by ROS [1].