This is still very much early-days, but I’m thinking about building a distributed link aggregator. Some notes: - no servers (all P2P) except to connect peers - no “instances” so everything is in one namespace (so like reddit /r/community, not lemmy instance/c/community) - everyone is a moderator - moderation based on a web of trust type system - desktop first, mobile/web later - web would require servers, mobile may have platform-specific issues - no plans to integrate with fediverse, but could be possible - initial intent is to be text-only - file storage could be supported later in an opt-in basis (for now, just link to an external img host), but I’m worried about disk storage since there’s no central data lake and everyone needs to chip in some storage space Some technical details: - written in Rust and ReactJS - Tauri-based - uses Iroh [https://iroh.computer/] for data synchronization - looking into Appleseed [https://github.com/cblgh/appleseed-metric] and maybe TrustNet [https://github.com/cblgh/trustnet] for moderation Current status: - rewrote Appleseed and part of TrustNet to Rust for perf testing last weekend (Rust is waaay faster) - will probably rewrite again once I finish reading the paper (current code is a direct port) - have basic Tauri+Iroh app, but it’s a glorified chat app w/ no syncing between peers (a peer can join a chat, but will lose access if the host goes down) - reading source code for SimpleX [https://simplex.chat/] (re-learning Haskell too) - could be interesting for DMs or something I’m not sure how long I’ll work on this, but I’ll probably release some libraries under a relatively liberal license, so something like LGPL at the most stringent, but probably Apache/MIT (depends on if I need to clean-room the appleseed implementation). So, if there’s interest here, I’m happy to post updates for discussion periodically.

Meta wants to make Threads posts available on services that use ActivityPub, a social networking protocol. Here's how the testing is coming along.

Mastodon is an example of a decentralized social media platform — it doesn't rely on one single company and its server. But it comes with privacy and content moderation concerns.

This post will compare several peer to peer protocols by looking at how they work and the tradeoffs that one should consider when choosing one of them. We will specifically be looking at [BitTorrent](https://www.bittorrent.org/index.html), [IPFS](https://ipfs.io/), [Secure Scuttlebutt (SSB)](https://scuttlebutt.nz/) and [Hypercore](https://hypercore-protocol.org/).

Within the Next Generation Internet Initiative, we have been working towards alternative futures for the internet to create a resilient, trustworthy and sustainable internet. These alternate futures have one thing in common: they are based on technology commons: open standards, free and open