HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Azure
peerd
Go2025–2025
Azure / peerd

peerd

Peer to peer distribution of Azure Artifact Streaming.

12Distinct people
14Mentions
0Explicit recommenders
135GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Peer to peer distribution of Azure Artifact Streaming.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 9:01:12 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval14 dated mentions

Observed mentions: 2025-04-21 11:45:09 UTC to 2025-04-23 01:32:57 UTC.

012342025-04-21 09:00:00 UTC to 2025-04-21 12:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsApr 21, 09:002025-04-21 12:00:00 UTC to 2025-04-21 15:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-04-21 15:00:00 UTC to 2025-04-21 18:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-04-21 18:00:00 UTC to 2025-04-21 21:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-04-21 21:00:00 UTC to 2025-04-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-22 00:00:00 UTC to 2025-04-22 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-22 03:00:00 UTC to 2025-04-22 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 22, 03:002025-04-22 06:00:00 UTC to 2025-04-22 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-22 09:00:00 UTC to 2025-04-22 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-22 12:00:00 UTC to 2025-04-22 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-22 15:00:00 UTC to 2025-04-22 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-22 18:00:00 UTC to 2025-04-22 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-22 21:00:00 UTC to 2025-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-23 00:00:00 UTC to 2025-04-23 03:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 23, 00:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Apr 21, 09:002025-04-21 09:00:00 UTC2025-04-21 12:00:00 UTC202
Apr 21, 12:002025-04-21 12:00:00 UTC2025-04-21 15:00:00 UTC404
Apr 21, 15:002025-04-21 15:00:00 UTC2025-04-21 18:00:00 UTC303
Apr 21, 18:002025-04-21 18:00:00 UTC2025-04-21 21:00:00 UTC404
Apr 21, 21:002025-04-21 21:00:00 UTC2025-04-22 00:00:00 UTC000
Apr 22, 00:002025-04-22 00:00:00 UTC2025-04-22 03:00:00 UTC000
Apr 22, 03:002025-04-22 03:00:00 UTC2025-04-22 06:00:00 UTC000
Apr 22, 06:002025-04-22 06:00:00 UTC2025-04-22 09:00:00 UTC000
Apr 22, 09:002025-04-22 09:00:00 UTC2025-04-22 12:00:00 UTC000
Apr 22, 12:002025-04-22 12:00:00 UTC2025-04-22 15:00:00 UTC000
Apr 22, 15:002025-04-22 15:00:00 UTC2025-04-22 18:00:00 UTC000
Apr 22, 18:002025-04-22 18:00:00 UTC2025-04-22 21:00:00 UTC000
Apr 22, 21:002025-04-22 21:00:00 UTC2025-04-23 00:00:00 UTC000
Apr 23, 00:002025-04-23 00:00:00 UTC2025-04-23 03:00:00 UTC101

What Hacker News says

4 sources
Forking might be the wrong word, what happened here looks more like (somewhat obfuscated) plagiarism. I analyzed the 2 repositories for copy/pasted lines using PMD's CPD (copy/paste detector) - using the first commit of peerd and one from spegel that was from around the same time. There are some clear duplications, e.g. 178 lines here: https://github.com/Azure/peerd/blob/64b8928943ddd73691d0b5d8... correspond to this: https://github.com/spegel-org/spegel/blob/ed21d4da925b9a179c... Also 44 lines here: https://github.com/spegel-org/spegel/blob/ed21d4da925b9a179c... and https://github.com/Azure/peerd/blob/64b8928943ddd73691d0b5d8... but the full files are almost identical, only a few edits that break the complete equality. Also https://github.com/spegel-org/spegel/blob/ed21d4da925b9a179c... matches https://github.com/Azure/peerd/blob/64b8928
Read the rest
943ddd73691d0b5d8... I haven't looked deep enough to see how much of the differences are obfuscation and how much are meaningful changes. File names are all changed, many structs and variable names as well. See this gist for full list of duplications: https://gist.github.com/corneliusroemer/c58cf0faf957d9001b58...
In Getting forked by Microsoft
Very possible, from the in repo documentation (which credits Spegel yet again) https://github.com/Azure/peerd/blob/main/docs/design.md it seems like there was a particular engineer at Microsoft who was working on Azure Container Registry who found it useful to integrate Azure Container Registry. If they contributed it upstream, would we be discussing a blog post "how dare evil megacorp submit a PR that only implements their API! embrace extend extinguish!"? Probably.
In Getting Forked by Microsoft
The commit histories for the LICENSE files in the two repositories are rather interesting. The original author placed a single copyright notice in that file. Microsoft on the other hand published it with their copyright notice and a Apache 2.0 license in place of the original copyright notice and MIT license. They also put copyright Microsoft and license apache 2.0 headers on all files. They then changed the Apache 2.0 license to MIT, but left their copyright notice in place of the original copyright notice in LICENSE: https://github.com/Azure/peerd/commit/473a26c808907f2d9f7b7f... Unless they forked a very early version that did not even have the LICENSE file, such that they never removed the original notice, this looks like copyright infringement to me. That said, I am not a lawyer.
In Getting forked by Microsoft

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.