- From: Bumblefudge <bumblefudge@learningproof.xyz>
- Date: Thu, 08 Feb 2024 02:37:09 +0000
- To: public-swicg@w3.org
- Message-ID: <0ac8bec3-78a2-43cb-918d-99df3c581a1e@learningproof.xyz>
On 2/7/2024 5:04 PM, Bob Wyman wrote: > if one assumed a content-addressable, platform-independent data storage mechanism, such as that implemented by [IPFS](https://en.wikipedia.org/wiki/InterPlanetary_File_System) (The Interplanetary File System), then it would be possible to implement much of what SocialWeb interactions require without any particular platform. I think Mitra might be the pioneer here, but actually integrating this kind of portability/platform-agnostic storage for easier migration (and server-agnostic/content-addressed `id`s, etc) is a bit of a lift for most other server codebases, and they won't arrive to a place of portable/interoperable IPFS-addressed content without a lot of alignment on planning and user stories and the like. I have a WIP meta-FEP trying to tease out this alignment, but it's early days! Any help appreciated: https://codeberg.org/fediverse/fep/src/commit/255deda07555f5ce188c13821edb9091f394dab0/fep/cd47/fep-cd47.md > While data-portability will solve some problems associated with binding to a specific SocialWeb platform, it won't solve them all. Agree-- easier to decompose the goals into little incremental features and tweaks that can be combined and roadmapped one minor version at a time...
Received on Thursday, 8 February 2024 02:37:31 UTC