Hacker GitHub

← All repos

Azure/peerd

View on GitHub ↗ ★ 135 Go

Peer to peer distribution of Azure Artifact Streaming.

14 mentions on Hacker News by 12 people: 0 stories, 14 comments · first 2025-04-21 · latest 2025-04-23

Mentions per year 14 mentions · busiest year 2025 (14)
20082026
  1. …community goodwill by "releasing" an open source tool) is not the same thing as generating revenue. https://github.com/Azure/peerd does not have a "pricing" section.
    comment by philsnow · 2025-04-23 · in Getting forked by Microsoft
  2. …at MS. This might have been brushed under the carpet and due to sheer luck it reached HN frontpage. https://github.com/Azure/peerd/commit/64b8928943ddd73691d0b5...
    comment by throwaway642012 · 2025-04-21 · in Getting forked by Microsoft
  3. They just updated the license and attribution. https://github.com/Azure/peerd/pull/110/files . Overall, it does not sit right with me. How can you be at the position you are and make a very obvious non-attribution mistake. I want to side…
    comment by detective_bosch · 2025-04-21 · in Getting forked by Microsoft
  4. …, let you know what we’re doing, and address a few points. We’ve just raised a pull request https://github.com/Azure/peerd/pull/110 amending the license headers in the source files. We absolutely should have done better here: our company…
    comment by lachie83 · 2025-04-21 · in Getting forked by Microsoft
  5. https://github.com/Azure/peerd/pull/110 > fix: amend copyright attributions #110 > > This commit amends copyright attributions that were omitted due to an oversight on part of the Peerd authors. Copyright header attributions in a few files…
    comment by joshka · 2025-04-21 · in Getting forked by Microsoft
  6. …you need to put the license in the header of each file as a best practice. Like Microsoft did here https://github.com/Azure/peerd/blob/main/api/docs.go#L1 spegel did not follow best practices to put the copyright in the file itself:…
    comment by firesteelrain · 2025-04-21 · in Getting forked by Microsoft
  7. …the line "Copyright (c) 2024 The Spegel Authors" in the main license file. Now that it's brought up https://github.com/Azure/peerd/issues/109 that'll probably be fixed. What remains after full compliance with the MIT license choince will…
    comment by zamadatix · 2025-04-21 · in Getting forked by Microsoft
  8. …matter that they replaced MIT with MIT, because they stripped the author and attribution from it. https://github.com/Azure/peerd/blob/main/LICENSE If you read that file you'd think that Microsoft was the copyright holder, but they very…
    comment by tedivm · 2025-04-21 · in Getting forked by Microsoft
  9. Yep, there's an issue with 200+ reactions: https://github.com/Azure/peerd/issues/109
    comment by croemer · 2025-04-21 · in Getting forked by Microsoft
  10. …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/ed21d4da925b9a1…
    comment by croemer · 2025-04-21 · in Getting forked by Microsoft
  11. 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…
    comment by Maxious · 2025-04-21 · in Getting forked by Microsoft
  12. …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,…
    comment by ryao · 2025-04-21 · in Getting forked by Microsoft
  13. …to have tried to relicense this to Apache 2.0 before backpedaling and reinstating the MIT license: https://github.com/Azure/peerd/commit/473a26c808907f2d9f7b7f... Unless they forked from a very early version of the project that did not…
    comment by ryao · 2025-04-21 · in Getting forked by Microsoft
  14. https://github.com/Azure/peerd/blob/main/LICENSE I don't see "Copyright (c) 2024 The Spegel Authors" (the "above copyright notice" in https://github.com/spegel-org/spegel/blob/main/LICENSE ) anywhere. Where do you see it?
    comment by Zambyte · 2025-04-21 · in Getting forked by Microsoft