[Din] Sidemeeting Today at IETF 121 Dublin

bumblefudge von CASA <bumblefudge@learningproof.xyz> Thu, 07 November 2024 09:55 UTC

Return-Path: <bumblefudge@learningproof.xyz>
X-Original-To: din@ietfa.amsl.com
Delivered-To: din@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0D31C1D4A9D for <din@ietfa.amsl.com>; Thu, 7 Nov 2024 01:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.905
X-Spam-Level:
X-Spam-Status: No, score=-1.905 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MAwoP9Xko2Nx for <din@ietfa.amsl.com>; Thu, 7 Nov 2024 01:55:49 -0800 (PST)
Received: from mail-40136.proton.ch (mail-40136.proton.ch [185.70.40.136]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8151C1D4A85 for <din@irtf.org>; Thu, 7 Nov 2024 01:55:48 -0800 (PST)
Date: Thu, 07 Nov 2024 09:55:42 +0000
To: "din@irtf.org" <din@irtf.org>
From: bumblefudge von CASA <bumblefudge@learningproof.xyz>
Message-ID: <eFRFdC5TslNbLz7537VHyd4PgwodquA5EHjSiWBY7kjNzVHj_3zxptmMXBiYOFMqc-ADKf7JyZBwPqW-LkIjL3ks4gKI1QmAmeMoanFjNn0=@learningproof.xyz>
Feedback-ID: 85909410:user:proton
X-Pm-Message-ID: e4dee3d0fc4d877eec083adfaf33974b4b4405ba
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: IUOHSIFWK2TMHHKIQ25JYY6CDSJDLQPB
X-Message-ID-Hash: IUOHSIFWK2TMHHKIQ25JYY6CDSJDLQPB
X-MailFrom: bumblefudge@learningproof.xyz
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-din.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Din] Sidemeeting Today at IETF 121 Dublin
List-Id: "Discussion of distributed Internet Infrastructure approaches, aspects such as Service Federation, and underlying technologies" <din.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/din/hpowO2AFfZEfjvFBj4MLrskr43U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/din>
List-Help: <mailto:din-request@irtf.org?subject=help>
List-Owner: <mailto:din-owner@irtf.org>
List-Post: <mailto:din@irtf.org>
List-Subscribe: <mailto:din-join@irtf.org>
List-Unsubscribe: <mailto:din-leave@irtf.org>

Dear DINRG:

As mentioned yesterday in the meeting, I'm hosting a
drop-in session today where people interested in the possible applicability of the Multiformats WG primitives to their use-cases can come chat. If you've been following the list and you have questions about what's possible, feel free to come by! I've made an .ics for people which includes the teleconferencing link:

https://wiki.ietf.org/121/ietf121-multiformats-sidemeeting.ics

It may be of interest to fans of RFC 6920 (NIH), self-describing data formats more generally, and alternate file systems, but I'm hoping a different combination of these kooky primitives could have utility in various other local-first systems, public-data systems with similar properties to BlueSky (which leans heavily on [CIDs][^1] for edge verifiability), etc.

Thanks!
--bf

[^1]: https://github.com/multiformats/cid?tab=readme-ov-file#how-does-it-work
---
bumblefudge
janitor @Chain Agnostic Standards Alliance, IPFS Foundation
contractable via learningProof UG
mostly berlin-based