Skip to content

Feature Request: Mesh Content Sharing #4118

@chapmanjacobd

Description

@chapmanjacobd

IIABs currently operate as isolated knowledge islands with limited ability to share curated content across networks. This differs from #4115 in a similar way that LANs and intranets differ from internetworking.

While traditional client-server sync solutions (rsync) are superior in controlled environments, they aren't designed for content distribution across (and between) many nodes.

This feature promotes the following use cases:

  • Collaborative content curation among educators: agnostic of network topology, conflict resolution: does not clobber concurrent edits
  • Handle distribution to thousands of IIAB servers without centralized bandwidth bottlenecks (and costs!)
  • Delay-Tolerant Networking: Support content sharing across unreliable or intermittent network connections; as long as two nodes in the line are online at the same time--the information flows

Security

  • Device-to-device certificate authentication via Syncthing
  • Selective file sharing between devices; partial content: download only requested files from syncthing folders or torrents
  • Fine-grained folder sharing permissions; Read-only vs read-write access controls

Implementation details

  • Bittorrent for large, static content
  • Syncthing for dynamic, curated content
  • If the above doesn't work out, I'm open to other ideas!

This feature request explores alternative distribution mechanisms complementary to the rsync/mDNS approach, focusing on scalability and decentralization rather than pure network efficiency.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions