#cbor — Public Fediverse posts

Tired of #JSON eating your bandwidth or latency? Try #CBOR, now with more statistics and figures.

https://doi.org/10.1109/TNSM.2026.3722114

Tired of #JSON eating your bandwidth or latency? Try #CBOR, now with more statistics and figures.

https://doi.org/10.1109/TNSM.2026.3722114

Last day of this #IETF starts and promises to be relaxed: All my currently busy drafts (on #CBOR and #LAKE formerly called #EDHOC) were discussed, #CBOR met and makes progress – now it's about hallway meetings, and finding out about things I missed :-)

Last day of this #IETF starts and promises to be relaxed: All my currently busy drafts (on #CBOR and #LAKE formerly called #EDHOC) were discussed, #CBOR met and makes progress – now it's about hallway meetings, and finding out about things I missed :-)

On my way to the #IETF #hackathon. This time, my focus will be on #EDHOC (key establishment for devices with tiny footprints, trying out the Lakers implementation of the PSK draft) and #CBOR experiments around matching its information model with XSD types (to reduce mismatches with #RDF).

And maybe I'll also show off #IPv6 over #DectNRPlus.

On my way to the #IETF #hackathon. This time, my focus will be on #EDHOC (key establishment for devices with tiny footprints, trying out the Lakers implementation of the PSK draft) and #CBOR experiments around matching its information model with XSD types (to reduce mismatches with #RDF).

And maybe I'll also show off #IPv6 over #DectNRPlus.

A cool recent #Python change is PEP 783 <https://peps.python.org/pep-0783/>. Its practical impact is profound for users of #pyodide (Python running in the browser): They could always just install pure Python wheels from PyPI, but for those backed by C or Rust, they previously used pyodide's built-in distro. While @pyodide did a great job there, using PyPI is less work for everyone.

Consequentially, using #CBOR diagnostic notation from https://pyodide.org/en/latest/console.html is now easier than ever:

A cool recent #Python change is PEP 783 <https://peps.python.org/pep-0783/>. Its practical impact is profound for users of #pyodide (Python running in the browser): They could always just install pure Python wheels from PyPI, but for those backed by C or Rust, they previously used pyodide's built-in distro. While @pyodide did a great job there, using PyPI is less work for everyone.

Consequentially, using #CBOR diagnostic notation from https://pyodide.org/en/latest/console.html is now easier than ever:

Are your interested in #cbor ?
I find it very interesting for #bioinformatics and #proteomics to store any amount of structured data.
As there were no #python library to handle it as a stream (so far), I've started a simple one based on cbor2:
https://codeberg.org/PAPPSO/pycborstream

"at a cost of higher implementation and learning complexity [of YAML]".

What, YAML has high complexity? NO way!

(found while reviewing https://www.ietf.org/archive/id/draft-ietf-cbor-edn-literals-25.html)

#CBOR #YAML

"at a cost of higher implementation and learning complexity [of YAML]".

What, YAML has high complexity? NO way!

(found while reviewing https://www.ietf.org/archive/id/draft-ietf-cbor-edn-literals-25.html)

#CBOR #YAML

People keep reinventing serialisation, generally badly. A year ago I proposed my own as a joke:

https://wiesmann.codiferes.net/wordpress/archives/38143

What I find fascinating, is that I keep seing proposals which are probably worse…

#serisalisation #json #cbor #serialization

People keep reinventing serialisation, generally badly. A year ago I proposed my own as a joke:

https://wiesmann.codiferes.net/wordpress/archives/38143

What I find fascinating, is that I keep seing proposals which are probably worse…

#serisalisation #json #cbor #serialization

I used to not like JSON-LD. And then I got exposed to CBOR. And, since then, I ended up liking JSON-LD more than I did before.

https://j12t.social/@j12t/114581086678041245

...

I was looking for performant ways of storing JSON-LD data, so that it can be looked up, queried, etc.

CBOR might actually be a way of doing that.

...

For me that is an odd realization given me liking JSON-LD is a reaction to CBOR.

#ActivityPub #ActivityStreams #CBOR #CBORLD #FediDev #JSONLD

I used to not like JSON-LD. And then I got exposed to CBOR. And, since then, I ended up liking JSON-LD more than I did before.

https://j12t.social/@j12t/114581086678041245

...

I was looking for performant ways of storing JSON-LD data, so that it can be looked up, queried, etc.

CBOR might actually be a way of doing that.

...

For me that is an odd realization given me liking JSON-LD is a reaction to CBOR.

#ActivityPub #ActivityStreams #CBOR #CBORLD #FediDev #JSONLD

Watched @pid_eins #fosdem2026 presentation record about #Varlink. I think the idea is good, except it should use some binary protocol for communication between services. RFC 8949 #CBOR seems like excellent candidate. Text serialization is not necessary if human is never direct part of a pipeline. Data conversion is not slow, but not necessary between localhost- only services.

Watched @pid_eins #fosdem2026 presentation record about #Varlink. I think the idea is good, except it should use some binary protocol for communication between services. RFC 8949 #CBOR seems like excellent candidate. Text serialization is not necessary if human is never direct part of a pipeline. Data conversion is not slow, but not necessary between localhost- only services.

The sign is a lie (and they knew that advance: train goes only to Köln), but still on my way to #FOSDEM.

Happy any time to talk about #CoAP, #CBOR, #DectNrPlus, IoT security and embedded Rust development, especially on @ariel and @RIOT_OS.

The sign is a lie (and they knew that advance: train goes only to Köln), but still on my way to #FOSDEM.

Happy any time to talk about #CoAP, #CBOR, #DectNrPlus, IoT security and embedded Rust development, especially on @ariel and @RIOT_OS.

Hello #Proteomics !

Thinking about a better mzML to store proteomics data, but not convinced by the #parquet approach, I've converted it into #CBOR :
* Smaller data files (only 66% of the mzML original file) for the exact same data
* Faster to read (25s for a big mzML vs 18s in mzcbor on the same computer)
* Very quick random access to spectra (24.6577 ms for mzML vs 786.731 μs for mzcbor for the same operation using index)

I'd like to share it if you are interested at #eubIC #eubic2026

Проектируем как синьор: универсальная бинаризация

Здравствуйте, меня зовут Дмитрий Карловский и я.. да не важно кто я. Важно о чём я говорю, и как аргументирую. Кто меня знает, тому и не надо рассказывать. А кто не знает — у того есть прекрасная возможность подойти к вопросу с чистым разумом. А это крайне важно, если мы хотим спроектировать что-то по настоящему хорошо, а не как обычно. Что ещё за VaryPack?

https://habr.com/ru/articles/975020/

#VaryPack #MsgPack #CBOR #BSON

JSON? JSONB? BSON? CBOR? MsgPack? А, VaryPackǃ

VaryPack - новый, простой, гибкий, шустрый и компактный формат бинарной сериализации произвольных данных. Что за модная тема?

https://habr.com/ru/articles/966270/

#VaryPack #MsgPack #CBOR #JSON #JSONB #BSON

OH in the #CBOR meeting of #IETF:

Everything you can do on a light bulb, you can do [on a computer] a billion times.

OH in the #CBOR meeting of #IETF:

Everything you can do on a light bulb, you can do [on a computer] a billion times.

@algernon Still undecided, I'm considering #CBOR diagnostic format, but it's not ideal either.

@algernon Still undecided, I'm considering #CBOR diagnostic format, but it's not ideal either.

@lambdageek That's a good observation, and helps me express the troubles I face using it with idiomathc #CBOR

@lambdageek That's a good observation, and helps me express the troubles I face using it with idiomathc #CBOR

CBOR Tag for JSON Number Strings

https://justatheory.com/2025/05/cbor-json-number-string/

#golang #cbor #ietf #iana

CBOR Tag for JSON Number Strings

https://justatheory.com/2025/05/cbor-json-number-string/

#golang #cbor #ietf #iana

I got an IANA assignment registered: “JSON Number String Tag for CBOR.” Useful to preserve string literal representation of JSON numbers, such as those created by Go's json.Number.

https://gist.github.com/theory/ef667af1c725240e6e30d525786d58e6

Will show up on https://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml soonish.

#golang #cbor

I got an IANA assignment registered: “JSON Number String Tag for CBOR.” Useful to preserve string literal representation of JSON numbers, such as those created by Go's json.Number.

https://gist.github.com/theory/ef667af1c725240e6e30d525786d58e6

Will show up on https://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml soonish.

#golang #cbor

Nice new milestone for #embedded #Rust development: defmt 1.0 has been released. The crate enables logging for microcontrollers without text or number formatting on the device – instead, the device sends numbers of interned strings to the host, which composes log messages.
1.0 is not only a stable release, but also enables logging #CBOR data into diagnostic notation on the host.

#RustLang

Nice new milestone for #embedded #Rust development: defmt 1.0 has been released. The crate enables logging for microcontrollers without text or number formatting on the device – instead, the device sends numbers of interned strings to the host, which composes log messages.
1.0 is not only a stable release, but also enables logging #CBOR data into diagnostic notation on the host.

#RustLang

The #IETF122 hackathon starts in a few hours. I will be joining remotely, work on #EDHOC on @ariel (let's see if its out-of-the-box support also interoperates out-of-the-box), and play with #embeddfriendly URIs expressed in #CBOR.

#IETF #IETFHackathon #ArielOS

The #IETF122 hackathon starts in a few hours. I will be joining remotely, work on #EDHOC on @ariel (let's see if its out-of-the-box support also interoperates out-of-the-box), and play with #embeddfriendly URIs expressed in #CBOR.

#IETF #IETFHackathon #ArielOS

RFC 9741: CDDL Additional Control Operators for the Conversion and Processing of Text

Le langage #CDDL, qui permet de créer un schéma formel pour des formats comme #CBOR, peut s'étendre via l'ajout d'« opérateurs de contrôle ». Ce #RFC en spécifie quelques uns, notamment pour agir sur du texte ou convertir d'une forme dans un autre.

https://www.bortzmeyer.org/9741.html

RFC 9741: CDDL Additional Control Operators for the Conversion and Processing of Text

Le langage #CDDL, qui permet de créer un schéma formel pour des formats comme #CBOR, peut s'étendre via l'ajout d'« opérateurs de contrôle ». Ce #RFC en spécifie quelques uns, notamment pour agir sur du texte ou convertir d'une forme dans un autre.

https://www.bortzmeyer.org/9741.html

My recent work on #CBOR diagnostic tools has culminated in the release v0.0.7 of the cbor-edn #RustLang crate, and the cbor-diag v1.1.0 #Python package (which is powered by the former, #maturin and #PyO3).
It is now easy to receive CBOR data structure with internal tags, and have them display like this:
{1: IP'2001:db8::1', 3: DT'2025-01-14T13:27:49Z'}
https://cbor-diag.readthedocs.io/en/latest/
https://docs.rs/cbor-edn/latest/cbor_edn/

My recent work on #CBOR diagnostic tools has culminated in the release v0.0.7 of the cbor-edn #RustLang crate, and the cbor-diag v1.1.0 #Python package (which is powered by the former, #maturin and #PyO3).
It is now easy to receive CBOR data structure with internal tags, and have them display like this:
{1: IP'2001:db8::1', 3: DT'2025-01-14T13:27:49Z'}
https://cbor-diag.readthedocs.io/en/latest/
https://docs.rs/cbor-edn/latest/cbor_edn/

RFC 9682: Updates to the CDDL grammar of RFC 8610

Voici une légère mise à jour de la grammaire du langage de description de schéma #CDDL (Concise Data Definition Language), originellement normalisé dans le RFC 8610. Pas de gros changement.

https://www.bortzmeyer.org/9682.html

#CBOR #RFC

RFC 9682: Updates to the CDDL grammar of RFC 8610

Voici une légère mise à jour de la grammaire du langage de description de schéma #CDDL (Concise Data Definition Language), originellement normalisé dans le RFC 8610. Pas de gros changement.

https://www.bortzmeyer.org/9682.html

#CBOR #RFC

Starting into a busy #IETF121 day: talking about #CoAP in the morning CoRE meeting, IoT lunch, #CBOR in afternoon, and board game night to unwind.
And that's only the Tuesday :-)

Starting into a busy #IETF121 day: talking about #CoAP in the morning CoRE meeting, IoT lunch, #CBOR in afternoon, and board game night to unwind.
And that's only the Tuesday :-)

"ChatGPT can explain it, so it means the spec is fine."

#CBOR #IETF121

"ChatGPT can explain it, so it means the spec is fine."

#CBOR #IETF121

#DNS encoded in #CBOR (for IoT). Two implementations (including one in RIOT.)

(Not related to C-DNS.]

#IETF121

#DNS encoded in #CBOR (for IoT). Two implementations (including one in RIOT.)

(Not related to C-DNS.]

#IETF121

On my way to the #IETF121 hackathon -- I'll be working on packed #CBOR and #CoAP security, but also curious to chat with folks from other projects.

On my way to the #IETF121 hackathon -- I'll be working on packed #CBOR and #CoAP security, but also curious to chat with folks from other projects.

The #RustLang #CoAP example of @RIOT_OS has been updated. Previously you could list processes, access sensors or read the file system. Now, you can blink LEDs, read network settings, send #IPv6 pings, and even see who pinged you.
The data formats will still need some work, right now a lot is just crude #CBOR, but it works.
https://github.com/RIOT-OS/RIOT/tree/master/examples/rust-gcoap

RFC 9581: CBOR Tags for Time, Duration, and Period

Ce #RFC ajoute au format de données binaire #CBOR la possibilité de stocker des données temporelles plus détaillées, incluant par exemple l'échelle utilisée (UTC ou TAI), ou bien ayant une précision supérieure.

https://www.bortzmeyer.org/9581.html

It's been on my mind I wanted to get to understand a few things…

1. #COSE : #CBOR Object Signing and Encryption
2. #X25519KeyExchange

There are a few applications I have in mind for this and I could find no good examples. So, I sat down and nutted out this:

https://gist.github.com/sjlongland/fc2e06cb47543e977440b79d6cf71185

This is a simple demonstration of X25519 and COSE in #Python. The idea being that this allows two peers to mutually authenticate, then establish a shared secret.

I'm still not 100% certain of some X25519 key exchange details, specifically why pycryptography's example does it twice?

https://cryptography.io/en/latest/hazmat/primitives/asymmetric/x25519/#exchange-algorithm

Note: they generate `derived_key`, but never use it. It'd make sense if it were part of the second call to `HKDF` or something, but the result is simply thrown away. Anyone know why that is?

Anyway, maybe the #cryptography gurus might have some ideas, and whether my little toy here actually would work for decent secure comms, or if there's a gaping hole I should look out for.

Getting out of a sidetrack activity: cbor-edn 0.0.3 published. It is both a command line tool and a #RustLang library, and interacts with #CBOR diagnostic notation from plain conversion up to processing of the upcoming application literals:
$ cargo install cbor-edn
$ echo '{4: 1234567890}' | cbor-edn diag2diag --annotate ccs
{/ exp /4: dt'2009-02-13T23:31:30+00:00'},
https://codeberg.org/chrysn/cbor-edn