home.social

#cbor — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #cbor, aggregated by home.social.

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

    wiesmann.codiferes.net/wordpre

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

    #serisalisation #json #cbor #serialization

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

    wiesmann.codiferes.net/wordpre

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

    #serisalisation #json #cbor #serialization

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

    wiesmann.codiferes.net/wordpre

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

    #serisalisation #json #cbor #serialization

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

    wiesmann.codiferes.net/wordpre

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

    #serisalisation #json #cbor #serialization

  5. 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.

    j12t.social/@j12t/114581086678

    ...

    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

  6. Watched @pid_eins presentation record about . I think the idea is good, except it should use some binary protocol for communication between services. RFC 8949 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.

  7. 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.

  8. Hello !

    Thinking about a better mzML to store proteomics data, but not convinced by the approach, I've converted it into :
    * 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

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

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

    habr.com/ru/articles/975020/

    #VaryPack #MsgPack #CBOR #BSON

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

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

    habr.com/ru/articles/975020/

    #VaryPack #MsgPack #CBOR #BSON

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

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

    habr.com/ru/articles/975020/

    #VaryPack #MsgPack #CBOR #BSON

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

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

    habr.com/ru/articles/975020/

    #VaryPack #MsgPack #CBOR #BSON

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

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

    habr.com/ru/articles/966270/

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

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

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

    habr.com/ru/articles/966270/

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

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

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

    habr.com/ru/articles/966270/

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

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

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

    habr.com/ru/articles/966270/

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

  17. OH in the #CBOR meeting of #IETF:

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

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

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

  20. 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.

    gist.github.com/theory/ef667af

    Will show up on iana.org/assignments/cbor-tags soonish.

    #golang #cbor

  21. 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

  22. 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

  23. 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.

    bortzmeyer.org/9741.html

  24. 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'}
    cbor-diag.readthedocs.io/en/la
    docs.rs/cbor-edn/latest/cbor_e

  25. 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'}
    cbor-diag.readthedocs.io/en/la
    docs.rs/cbor-edn/latest/cbor_e

  26. 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'}
    cbor-diag.readthedocs.io/en/la
    docs.rs/cbor-edn/latest/cbor_e

  27. 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'}
    cbor-diag.readthedocs.io/en/la
    docs.rs/cbor-edn/latest/cbor_e

  28. 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'}
    cbor-diag.readthedocs.io/en/la
    docs.rs/cbor-edn/latest/cbor_e

  29. 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.

    bortzmeyer.org/9682.html

    #CBOR #RFC

  30. 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 :-)

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

    #CBOR #IETF121

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

    (Not related to C-DNS.]

    #IETF121

  33. 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.

  34. 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.
    github.com/RIOT-OS/RIOT/tree/m

  35. 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.

    bortzmeyer.org/9581.html

  36. 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:

    gist.github.com/sjlongland/fc2

    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?

    cryptography.io/en/latest/hazm

    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.

  37. 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'},
    codeberg.org/chrysn/cbor-edn

  38. Are you using #CBOR in data formats you describe, in code, debugging or for examples? During the last #IETF meeting, @cabo gave a 30 minute tutorial on existing and upcoming technologies to make that easier. Watch the recording at <youtu.be/Cr6PeUUm7wY?feature=s>; slides with further links <datatracker.ietf.org/meeting/1>.

  39. And by the way, given that the #YAML follows a #CDDL scheme, this could make a fine use case for some #CBOR-LD experimentation (something something CDDL shaping of triples).
    /ping @cabo

  40. Connaissez-vous la RFC 8949 ? Non ? Jusqu'à ce matin, à ma grande honte, moi non plus... Pourtant le sujet est d'importance : une alternative binaire, compacte, performante, normée et pérenne. Le #CBOR: Concise Binary Object Representation.
    cbor.io/

    Le seul tuto du site renvoie à un article fr de présentation de @bortzmeyer : bortzmeyer.org/7049.html

    #BSON, #protobuf, #MessagePack : chacun a ses avantages (et inconvénients) face à #JSON.
    Le CBOR est une couleur de cette palette.

  41. #COSE (encryption for #CBOR) people posting encrypted content on their slides. Spoiler: it's unreadable.

  42. t-cose ("tea cosy", hence the teapots on the slides) is a C implementation of #COSE (signing #CBOR files). Many new features such as multiple signers, #edDSA, etc.

  43. And of course they have to make their own wire protocol called . 🙃 Using , , , or even directly was too difficult... Have to make it completely new requiring all new libraries and implementions to get something half started. 😮‍💨

    atproto.com/specs/xrpc

  44. is a for parsing -like formats.

    jsoncons has a data model that allows for parsing different formats that resemble JSON, like and , using extensions. jsoncons provides several ways of interacting with parsed data; a query-able structure, a strongly typed C++ class, or a SAX-like parse stream. jsoncons is fast, and has extensions for things like JSONPath.

    Website 🔗️: danielaparker.github.io/jsonco

  45. @alva @dkl even for embedded things... #BSON, #CBOR, #ProtocollBuffers, #UBJSON and "Smile" are existing things.

    Yes you can write your own (or write whatever your env thinks the current binary representation should look like to disk) - but then you have no tooling, no portability and/or no validation/standardisation.