# peer-to-peer Published articles for peer-to-peer. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## I Rebuilt a Minimal BitTorrent Client in Go to Understand Peer-to-Peer Choking Algorithms DevFeed: [I Rebuilt a Minimal BitTorrent Client in Go to Understand Peer-to-Peer Choking Algorithms]() Original publisher: [Read original article]() Author: hello@ankit-rana.com Published: 2026-08-02T00:00:00Z Content type: tutorial Language: en Sources: [Ankit Rana | Mechanical Sympathy]() Topics: [Algorithms](), [P2P](), [Go Language](), [Programming](), [Network]() Tags: [algorithms](), [bittorrent](), [distributed-systems](), [go](), [golang](), [network](), [networking](), [p2p](), [peer-to-peer](), [protocol](), [system-design]() ### AI overview A hands-on explanation of BitTorrent choking algorithms through rebuilding a minimal client in Go. The article describes choking as a decentralized bandwidth-allocation mechanism, explains the choked and interested states, and shows how upload capacity affects peer prioritization. ### Source excerpt The BitTorrent spec explains choking in two paragraphs; implementing it in Go and watching every peer choke you within 60 seconds is what makes it stick. Choking is a bandwidth allocator running independently on every node, not a courtesy flag. Upload is the scarce resource on an asymmetric link, and each connection carries just two booleans, choked and interested, whose four combinations drive the entire fairness policy of the swarm. ## Content-Addressing: A Year In Review DevFeed: [Content-Addressing: A Year In Review]() Original publisher: [Read original article]() Author: Robin Berjon Published: 2026-01-15T00:00:00Z Content type: opinion Language: en Sources: [IPFS]() Topics: [content addressed store](), [IPFS](), [P2P]() Tags: [2025](), [content](), [decentralized](), [ipfs](), [object-object](), [peer-to-peer](), [review](), [year-in-review]() ### AI overview A 2025 year-in-review of content addressing describes its role in data verification and independence from centralized authorities. It highlights IPFS community progress toward a more modular technology suite, including standards, specifications, and purpose-built libraries. ### Source excerpt Let's take a look at what happened in content addressing in 2025 -- it's a lot! ## Shipyard 2025: IPFS Year in Review DevFeed: [Shipyard 2025: IPFS Year in Review]() Original publisher: [Read original article]() Author: lidel; Shipyard Published: 2025-12-19T00:00:00Z Content type: article Language: en Sources: [IPFS]() Topics: [IPFS](), [Self-hosted](), [releases](), [browser](), [HTTP]() Tags: [2025](), [boxo](), [browser](), [decentralized](), [dht](), [distributed](), [dweb](), [ecosystem](), [helia](), [http](), [ipfs](), [kubo](), [libp2p](), [p2p](), [peer-to-peer](), [rainbow](), [releases](), [review](), [self-hosted](), [storage](), [web](), [web3](), [year-in-review]() ### AI overview A review of IPFS developments in 2025, highlighting seven Kubo releases and related ecosystem updates. It focuses on DHT Provide Sweep, AutoTLS, HTTP retrieval, and Helia-based browser retrieval as improvements for self-hosted nodes and trustless access. ### Source excerpt Seven Kubo releases made self-hosted IPFS practical. Highlights: DHT Provide Sweep, AutoTLS, HTTP retrieval, and Helia for trustless browser retrieval. ## Provide Sweep: Solving the DHT Bottleneck for Self-Hosting IPFS at Scale DevFeed: [Provide Sweep: Solving the DHT Bottleneck for Self-Hosting IPFS at Scale]() Original publisher: [Read original article]() Author: guillaumemichel; Shipyard Published: 2025-11-26T00:00:00Z Content type: article Language: en Sources: [IPFS]() Topics: [IPFS](), [Scalability](), [Self-hosted](), [networking](), [Raspberry Pi]() Tags: [boxo](), [decentralized](), [dht](), [distributed](), [dweb](), [ecosystem](), [helia](), [ipfs](), [kubo](), [libp2p](), [p2p](), [peer-to-peer](), [performance](), [rainbow](), [raspberry-pi](), [routing](), [scale](), [self-hosting](), [storage](), [web](), [web3]() ### AI overview This article explains how Kubo v0.39's Provide Sweep becomes the default provider system for IPFS. By batching CIDs associated with the same DHT servers and systematically sweeping keyspace regions, it reports a 97% reduction in DHT lookups for a node providing 100,000 CIDs, alongside smart resume capabilities and memory optimizations. ### Source excerpt Provide Sweep: Solving the DHT Bottleneck for Self-Hosting IPFS at Scale ## Faster Peer-to-Peer Retrieval in Browsers With Caching in the Delegated Routing HTTP Server DevFeed: [Faster Peer-to-Peer Retrieval in Browsers With Caching in the Delegated Routing HTTP Server]() Original publisher: [Read original article]() Author: Daniel Norman Published: 2025-09-05T00:00:00Z Content type: article Language: en Sources: [IPFS]() Topics: [IPFS](), [networking](), [HTTP](), [browsers](), [Mobile]() Tags: [caching](), [helia](), [http](), [ipfs](), [mobile](), [object-object](), [peer-to-peer]() ### AI overview The article explains how Someguy, IPFS's Delegated Routing HTTP API, uses cached provider addresses and active DHT peer probing to improve provider discovery. The changes increase the share of providers returned with addresses and support faster IPFS content retrieval in browsers and mobile applications. ### Source excerpt How caching and active peer probing in the Someguy, the Delegated Routing server accelerates peer-to-peer content retrieval in browsers and mobile applications. ## The Static Website Manifesto DevFeed: [The Static Website Manifesto]() Original publisher: [Read original article]() Author: Justin Hunter Published: 2025-03-06T00:00:00Z Content type: opinion Language: en Sources: [IPFS]() Topics: [IPFS](), [Website](), [P2P](), [Web Development](), [web-standards]() Tags: [css](), [html](), [ipfs](), [javascript](), [modern-web-development](), [object-object](), [open-web](), [peer-to-peer](), [website]() ### AI overview The article presents a manifesto for making website publishing simpler and more enjoyable. It argues that IPFS is a natural fit for open websites because content addressing can provide peer-to-peer access, availability when a node serves the data, and built-in versioning for site content. It also criticizes the complexity of modern web development and advocates the continued usefulness of HTML, CSS, and JavaScript. ### Source excerpt Building websites used to be fun. Let's bring back the joy of putting your work online by using open protocols like IPFS. ## What is WebRTC? Post on LincolnLoop's blog DevFeed: [What is WebRTC? Post on LincolnLoop's blog]() Original publisher: [Read original article]() Author: Graham King Published: 2012-09-12T16:33:05Z Content type: article Language: en Sources: [Graham King]() Topics: [WebRTC](), [browser](), [JavaScript](), [P2P](), [webcam](), [real-time]() Tags: [browser](), [javascript](), [lincolnloop](), [peer-to-peer](), [real-time](), [software](), [video](), [web](), [webcam](), [webrtc]() ### AI overview The article introduces WebRTC as a specification and project that adds browser-based JavaScript APIs for accessing webcams and microphones and connecting directly to other browsers. It highlights video calling and the potential for peer-to-peer, serverless browser applications. ### Source excerpt I blogged What is WebRTC over on Lincoln Loop's blog: WebRTC, short for Web Real Time Communications, is a specification and project adding JavaScript APIs in the browser to: - Access a user's webcam and microphone: getUserMedia. - Connect directly to another browser: PeerConnection and DataChannel. Being able to do video calling in the browser is exciting, but to me the most exciting part of WebRTC is the prospect of peer-to-peer apps in the browser, and server-less applications.