• #AI costs how much? #GitHub #Copilot users react to new #usage-based #pricing system.
    https://arstechnica.com/ai/2026/06/ai-costs-how-much-github-copilot-users-react-to-new-usage-based-pricing

    Some report burning through their whole monthly “AI credit” allotment in a single day.

    In April, GitHub announced that it was moving subscribers from request-based billing to a usage-based model for its AI-powered Copilot service. As that new pricing model goes into effect today, many GitHub Copilot users are reporting some extreme sticker shock as they realize just how quickly their previous “normal” usage is burning through their newly limited monthly allotment of AI credits.

    #IA

    • Dès le premier jour, la facture à l’usage de GitHub Copilot interroge les devs
      https://next.ink/240147/des-le-premier-jour-la-facture-a-lusage-de-github-copilot-interroge-les-devs

      GitHub vient de changer sa manière de facturer son service Copilot pour les développeurs. Se basant sur l’usage réel, ce nouveau système de facturation a surpris beaucoup de développeurs utilisant l’IA générative dans leur travail au quotidien. L’adoption d’autres approches devient nécessaire.

      Ça devient super-technique de programmer. Faut trouver des prompts optimisés, pour que la facture n’augmente pas. J’ai trop envie de m’inscrire au prochain Mastère d’utilisation des IAgen de programmation, pour découvrir les trucs et astuces qui permettent de maximiser les prompts et les coûts. Assurément, tu as l’impression de te réaliser dans ton métier, à optimiser ton langage naturel.

  • Jeremiah Fieldhaven: #rsync, since 3.4.1, 36 commits by “#tridge and #claude” - Mastodon
    https://mastodon.gamedev.place/@JeremiahFieldhaven/116654345332213390

    So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple —compare-dest= arguments - started to fail on anything but a full backup.

    Revert to 3.4.1 and it works.

    So I go look at the source in #GitHub to see what might have changed, because there doesn’t seem to be anything relevant in the changelog.

    Since 3.4.1, 36 commits by “tridge and claude”

    Oh for fuck’s sakes.

    • Typique de : correlation n’est pas causalité. Et donc ce post ne dit rien d’autre que la panique de son auteur (pour l’instant).

      L’histoire ne dit pas si c’est précisément un commit « tridge and claude » qui provoque le nouveau bug ajouté (il y a aussi plein d’autres commits sans claude, et aussi des commits d’autres que tridge le créateur).

      Ça peut, mais rien ne le montre pour l’instant. Imaginons :
      – tridge, qui n’est pas le premier venu (créateur de rsync…), utilise Claude en relisant super sérieusement le résultat, et ça ne vient d’aucun de ces commits là
      – que le bug vienne en fait d’un commit d’une autre personne OU de tridge sans Claude

      Alors ça ne serait qu’un post de plus de panique moral, et qui ne dit rien de plus.

      Donc attendons le vrai commit fautif exact ?

    • rrsync refuses “absolute” source path (starting with /) · Issue #922 · RsyncProject/rsync
      https://github.com/RsyncProject/rsync/issues/922

      d4c4f67 added a single line to rrsync to “remove multiple leading slashes”. By removing all leading slashes, this line ensures that the test for a leading slash four lines further down never succeeds and “absolute” paths below the rrsync base directory are not appended to that base directory anymore. This breaks rsync calls with, e.g., source path /.

    • jonny (nonvenomous) - Mastodonc
      https://neuromatch.social/@jonny/116657411750038515

      all the criticism has been said, all the takes been had. the only metaphor i have been finding consistently useful for understanding what is happening with people and “AI” is addiction, and specifically gambling addiction.

      i love gambling. i have used “AI” extensively. it feels the same.

      So, look. One shot rewriting the whole test suite in another language is probably not great to do, but what happened here is so much worse than you are expecting.

      https://github.com/RsyncProject/rsync/pull/903

      This does not “translate tests into pytest” or a unit testing framework, it writes its own testing framework where tests are whole python scripts that redefine basic test functions in every script. Surely there would be a single way to “run rsync and get the results” - nope, well, there is, but then every test file will randomly redefine its own _run_and_capture function. So like now rsync needs a test suite for its test suite.

      If instead of telling an LLM to “rewrite the tests in python” you just searched “python testing” you would find the pytest docs. And then you would find examples. And then you could write fixtures to deduplicate all the prior shell script setup and teardown stuff, and so on. But since it was just “rewrite the tests in python” its now worse than before, and the odds of the rewrite actually being a 100% faithful translation are close to 0.

      I think the modal situation here is that the people are reading none or very little of what is being generated by the LLM, so the tests have a special role: Tests function as the pull arm on the slot machine, you just generate until tests pass, and that’s a jackpot. Obviously that’s meaningless when the tests are meaningless, so tests take on a very different meaning and role in slot machine coding.

      Previously we would write careful test conditions that were based off some real problem or an understanding of what the code under test did, and had a specific thing they were intended to protect against. Tests move slow and are designed to protect us against the things we know can go wrong. When we learn of a new wrong thing, we add a test.

      LLM tests have the form of tests but don’t do the same thing. They often test nothing, and are just expressions of truisms that the probabilistic text space explored while generating. They have strongly worded names but end up actually asserting that basic language features work as expected. Because it is not us writing tests for ourselves, where we only harm ourselves by making them weak, they function instead as a passively obfuscated justification for the code that the LLM generates. The user wants the tests to pass. The LLM provides.

      The tests are theater: they are the play field for the slot machine. They are mild, surmountable, need to fail a few times to be plausible, but must eventually pass within the expected generation loop window to deliver the payout.

      Here’s an example from some code that was thrust at me this week. The rest of the tests try a bit harder to look like tests, but this one is perplexing.

      What does it test? The function name suggests its a smoke test. LLMs love to call things smoke tests. That would suggest this would be an early-run test that fails loudly if some basic precondition - like having ffmpeg - fails. Or, I guess we are smoke testing the ensure_ffmpeg function? Anyway who knows. However we first check if ffmpeg or ffprobe are present, which is exactly what ensure_ffmpeg does. If they aren’t present, a warning tells us that ffmpeg/ffprobe are required for the video tests, which makes it seem like this should be a parameterizing test that controls which tests are run, which of course it does not do.

      So the test literally does nothing and cannot possibly fail, but says it does at least two things, because to an LLM something saying it does something is the same thing as it actually doing that thing.

      Edit: I’m seeing some comments that suggest ppl think this example is from rsync, as said at top, this is just an example that came my way in a different project and I’m using it to illustrate a common LLM test problem.

    • rsync and outrage. I gave up blogging a long time ago… | by Andrew Tridgell | Jun, 2026 | Medium
      https://medium.com/@tridge60/rsync-and-outrage-d9849599e5a0

      I gave up blogging a long time ago (apart from an occasional thing about ArduPilot), I tend to just write code and hope people find it useful, so it feels a bit odd to be writing this, but given the volume of rage posts I’ve been on the receiving end of lately I thought maybe I should post something.

      Like many developers of open source packages I’ve been hit by a flood of security reports lately in my role as the rsync maintainer. Many of those reports are AI generated (not all though, there are some notable ones with very careful and high quality manual analysis).

    • I’m retired (though my wife may dispute that!) and I’d rather be out sailing than working on rsync security issues, so I have reached for several AI tools to help with what needs to be done. I have absolutely no regrets about doing that, although from the storm of anti-AI rage it’s clear that many people think I should be hung up by my toe nails and flogged for even considering doing this.

      […]

      I did the design for that myself (and I’m really quite pleased with it), but used claude with cross-checks from codex and gemini to do the grunt work. I did not just vibe-code “convert test suite to python”. I’m a software engineer with 40 years experience (yeah, I’m OLD!), so I did a design first and had a plan for how to validate it. I used AI tools to do the grunt work because they are good at that. I reviewed every part of it myself and ran through a huge amount of CI time getting it right (I’m since moved to having a bunch of local VMs to do most testing to reduce the CI wait time). What you see in the commit history with co-authored by claude is the tip of the proverbial software engineering iceberg.

      […]

      for the people saying things like “I’m a PhD from xyz uni and I’m telling your LLMs are just stochastic tools that make everything up and the world will fall apart if you use them”, I’m here to tell you that you are out of date. The world of software engineering has changed dramatically in the last few months. The world of IT security and maintaining software in the face of the flood of reports has completely and utterly changed just in the last few weeks. Anything you learned about this stuff last year might as well be from another planet.

      […]

      Bottom line is I do know (well, roughly!) how LLMs work, but that doesn’t make them not useful. It does mean you have to be cautious, but I am being cautious, or as cautious as I can be given my desire to be sailing and not dealing with a flood of gunk from so-called internet experts.

    • A un moment, il met le doigt sur un point, qu’on peut considérer sans intérêt. Mais.

      I’m trying to decide at the moment between a 3.4.4 release that softens some of the regressions and going for the 3.5.0 that I had planned with much larger changes. The 3.5 release will raise the bar enormously with regards to rsync security, but it is a huge change. The large change set that is needed was a big motivation for the effort on the test suite rewrite — you can’t do a rapid large change to a piece of software like rsync without a really comprehensive test suite. I thought it would be a good idea to do the core structure for the new test suite in public on master first though given all the rage that has generated maybe that was a bad idea. Anyway, the new test suite has helped a lot, and I have a big pile of additional tests for security related issues that you can all enjoy reading when 3.5 comes out.

      Ces projets essentiels ne devraient pas reposer uniquement sur la bonne volonté d’un seul gars, même hyper-doué.

      Le projet curl est exemplaire à cet égard. Daniel Stenberg s’en sort plutôt bien. Au moins, il communique. Et il n’est pas seul.

    • Rsync opens the slopgates, regressions and bugs ensue – OSnews
      https://www.osnews.com/story/145198/rsync-opens-the-slopgates-regressions-and-bugs-ensue

      Andrew Tridgell, developer of rsync, has published a blog post addressing the massive surge in “AI” code submissions and the string of regressions supposedly caused by them. He explains rsync was flooded with “AI”-generated security reports, and he couldn’t handle the volumes anymore.

      (...)

      Tridgell’s blog post already has all the usual talking points from “AI” techbros about how the tools sucked last [year][month][week] but they’re good now, trust me I know how these tools work, humans are actually the same as these “AI” tools, really what is intelligence anyway, and yeah we got a whole slew of new issues caused by the “AI” code but more “AI” code will surely fix that, and so on. There’s some red flags that give me the ick, because I’ve seen them all before from people entirely losing themselves in “AI” hype.

      Tridgell also takes pot shots at openrsync, a reimplmentation of rsync developed by the OpenBSD team, also shipped by default on macOS. Openrsync has nothing to do with any of the current issues rsync is facing, as the project was started way back in 2018 or so. Taking pot shots at this project in this particular blog post feels childish and unnecessary, and reeks of insecurity; focus on the issues your own project is facing before attacking some other project. This feels like another red flag.

      (...)

    • [object Object] - Mastodon
      https://mas.to/@zzt/116689607026693907

      computer fuckers really will swoon about the nuanced position taken by the author of a blog post that declares that all of the PhDs who disagree with them are wrong and LLMs work exactly like human brains because they said so and also help help they’re the victim of an online hate mob because they did something fucked up and someone else noticed

      maybe keep the word nuance out of your fucking mouth if your version of nuance is indistinguishable from being a contrarian asshole

      you really don’t have to tie your brain into knots to make this into the kind of story where a person you already lionized was the victim of an unthinking angry mob, but you will because doing analysis is much harder than just claiming nuance

      within the past 24 hours I’ve watched two people claim there was nuance to the rsync story that made tridge right, and after not too much discussion they admitted they didn’t know rsync’s slop code only got noticed after a severe breakage occurred, or that people have evaluated the slop commits and found them to be of extraordinarily poor quality (including rendering rsync’s test suite ineffective by translating it from bash into broken python). the story they heard is that someone saw Claude in the commit log and freaked out and directed harassment towards tridge. they seemed to be under the false impression that rsync still worked fine.

      how is it that the members of the supposed angry mob are doing deeper analysis than the people claiming nuance?

      (...)

      there might well be people who legitimately went overboard on the guy and that’s awful

      what I’ve seen is exactly along the lines of what you described though: people are exhausted and filled with anxiety because a core tool broke and is promising more breakages. it keeps happening and it happened yet again, to a tool that was previously understood to be done. it’s both insult and injury.

      what’s interesting in this case is how many distro maintainers responded negatively but reasonably: first with exhaustion, then with a concrete plan to either pin or replace rsync. that feels to me like it might be what’s prompting the accusation that there’s a hate mob. rsync is losing its position, and this is damage control.

    • Réécrire tout un pan d’un logiciel, avec ou sans IA, ça ne s’improvise pas dans un commit non-annoncé au sein d’une version mineure. Les jeux de test, ce ne sont pas des parties mineures d’un projet. Et le burn-out n’excuse ni n’explique pas tout.

      Quand on dit qu’on a plusieurs dizaines d’années d’expérience, on ne se permet pas ce genre d’amateurisme, en expliquant qu’on maîtrise la bête et que si on n’est pas d’accord avec lui, on est des gros nuls.

      Sa communication, dans le fond, est catastrophique.

      Il fait partie des gens tombés dans le côté obscur de l’IA, à la façon Star Wars.

  • Scandale #GitHub #Copilot : #Microsoft injecte de la #pub dans votre #code
    https://goodtech.info/github-copilot-publicite-pull-requests-scandale-adware

    C’est la goutte d’eau qui fait déborder le vase du côté des développeurs sur Github ce mardi matin. Zach Manson, un ingénieur logiciel, vient de lever le lièvre sur une pratique pour le moins douteuse : GitHub Copilot, l’outil phare de Microsoft, s’est permis de modifier le descriptif d’une #Pull_Request (#PR) pour y injecter de la #publicité non sollicitée.

    Microsoft Copilot is now injecting ads into pull requests on GitHub - Neowin
    https://www.neowin.net/news/microsoft-copilot-is-now-injecting-ads-into-pull-requests-on-github-gitlab

    Over 1.5 million GitHub pull requests have had ads injected into them by Microsoft Copilot’s #coding_agent.

    Nous vivons dans une #dystopie de série B.

  • (1) Open Letter to Satya Nadella, CEO of Microsoft on the Future of GitHub, Trust, and Digital Sovereignty | LinkedIn
    https://www.linkedin.com/pulse/open-letter-satya-nadella-ceo-microsoft-future-github-dion-wiggins-f2yic

    Dion Wiggins
    Dion Wiggins
    CTO at Omniscien Technologies | Board Member | Strategic Advisor | Consultant | Author
    16 août 2025

    16 August 2025

    Dear Mr. Nadella (Satya Nadella) ,

    As a developer of more than 40 years, across 33+ programming languages and even more platforms, I have seen the rise and fall of countless technologies, communities, and ecosystems. While I cannot speak for the global developer community as a whole, it is clear that a very large number of us feel the same deep sense of betrayal and alarm over Microsoft’s actions regarding GitHub. This letter is written not only from decades of professional experience and personal investment, but in solidarity with the thousands of developers, project maintainers, community leaders, and digital sovereignty advocates who have raised these same alarms. The issues are systemic, not individual.

    Satya Nadella (2018): “We recognize the responsibility we take on with this agreement. We are committed to being stewards of the GitHub community, which will always remain open to all developers.”

    In the above Microsoft Blog post, you promised that “GitHub will operate independently and remain an open platform for all developers,” and committed to “keeping GitHub independent and developer-first.” GitHub leadership assured the world that “GitHub will operate independently… That means GitHub retains its developer-first values, distinctive spirit, and open extensibility.”

    Public promises on the Github website at the same time made simpler promises that have now been broken.

    Nat Friedman (2018): “GitHub will operate independently… That means GitHub retains its developer-first values, distinctive spirit, and open extensibility.”

    While Microsoft continues to highlight its open source credentials and assure developers that “nothing has changed” for users, the core issue is not superficial continuity, but the structural and strategic shift of GitHub from a genuinely independent, community platform to a fully integrated corporate asset. This is not about branding, but about irreversible changes to control, incentives, and accountability.

    Microsoft Press Release (2025): “This transition enables us to accelerate GitHub’s contributions to Microsoft’s AI ecosystem.”

    Today, those commitments are in question. As TechRadar reports: “Rather than appoint a new GitHub CEO, Microsoft will integrate GitHub more directly into CoreAI, led by Jay Parikh… GitHub will now report directly into its CoreAI division.” (TechRadar)

    This reporting is echoed by The Verge, which noted that “Microsoft isn’t replacing Dohmke’s CEO position, and GitHub will be fully part of Microsoft instead of being run as a separate entity.” (The Verge)

    These moves directly contradict the 2018 promise of independence and stewardship. They are not continuity but consolidation. For many in the community, this is not simply a broken promise but an outright lie. Your words from the past: “We recognize the responsibility we take on with this agreement. We are committed to being stewards of the GitHub community, which will retain its developer-first ethos, operate independently and remain an open platform”, now stand exposed as empty assurances at best, or an intentional lie at worst.

    I repeat these phrases because you have not lived up to them and they seem unimportant to you today. Just a tool of the past, discarded once the acquisition goals were complete.

    Microsoft’s decision to absorb GitHub into its CoreAI division, eliminate its independent leadership, and embed it deeply within the company’s AI and cloud business directly contradicts these promises. The official press release states this is to “accelerate GitHub’s contributions to Microsoft’s AI ecosystem.” Microsoft executives openly describe how “GitHub’s vast code corpus is foundational for the next era of Copilot and AI model development.”

    This is not just a broken promise. It is an assault on open source itself. A collapse of credibility with the global developer community, and a direct threat to technological self-determination for every contributor, organization, and nation that depends on independent infrastructure.

    Here is just a small sample of the many negative reactions to this announcement. These articles show a clear consensus across reputable tech publications: GitHub’s absorption into CoreAI is widely seen as a major structural shift, and for many, a direct betrayal of its once independent and developer-first identity:

    The Verge – “GitHub just got less independent at Microsoft after CEO resignation”

    Discusses how GitHub’s autonomy ends as leadership shifts under Microsoft’s CoreAI structure, posing a clear signal of deeper absorption. (The Verge)

    TechRadar – “GitHub CEO resigns – is this the latest sign of its Microsoft absorption?”

    Highlights the absence of a successor and emphasizes the strategic assimilation into Microsoft’s AI ecosystem. (TechRadar)

    IT Pro – “What Thomas Dohmke’s departure means for GitHub”

    Analyzes how the CEO’s exit signals major governance changes and closer alignment with Microsoft’s AI strategy. (IT Pro)

    Windows Central – “GitHub Just Got Assimilated—CEO Out, Copilot In, Microsoft All Over It”

    Signposts the end of GitHub’s independence and elevated priority of AI within Microsoft’s internal structure. (Windows Central)

    Tom’s Hardware – “GitHub folds into Microsoft following CEO resignation—once independent programming site now part of ‘CoreAI’ team”

    Explicitly frames the move as ending GitHub’s independence and compares it to other Microsoft acquisitions that lost identity over time. (Tom’s Hardware)

    The Collapse of Trust: Big Tech’s Greed, Digital Sovereignty, and Its Consequences

    Trust is the foundation of every open source project, community, and movement. Open source cannot function without the assumption that platforms and stewards act in good faith, respect contributors, and put the long-term health of the ecosystem ahead of short-term profit.

    The breakdown of trust caused by the actions of Microsoft and other Big Tech firms is more than a single betrayal. It signals to the entire world that the social contract underpinning open source and digital agency can be bought, sold, and quietly rewritten by whoever controls the infrastructure.

    It is disingenuous to claim that developers are “free to leave” when practical migration is obstructed by technical and network effects, and when so much of the world’s open source and digital sovereignty ecosystem is already tied into GitHub’s infrastructure. Genuine freedom requires open exit, true interoperability, and transparent guarantees. None of these can exist in an environment of creeping lock-in and vertical integration.

    When companies that present themselves as stewards of community assets choose instead to exploit those assets for proprietary gain, they undermine not just their own credibility, but the very possibility of global cooperation in technology. Each time a platform is captured, centralized, or redirected to serve corporate interests, it pushes developers and innovators away from openness and into silos of mistrust and fragmentation.

    No security, compliance, or anti-abuse argument can justify stripping developers, organizations, and nations of their digital sovereignty, or transferring unilateral control over critical digital assets to a single commercial actor. Security and compliance can and must be implemented in ways that preserve agency, transparency, and open governance.

    Digital sovereignty is not a slogan. It is a core policy objective of governments, regulatory agencies, and open source communities worldwide, with documented legal frameworks and active enforcement across the EU, China, India, and many others. The concerns raised here are not hypothetical or parochial. They are echoed by policymakers, technologists, and civil society leaders globally.

    This is not an isolated incident. The industry has seen similar betrayals before: Oracle’s handling of Java, Google’s abrupt shutdown of Google Code, and previous pivots by Microsoft itself. Each time, the developer community paid the price: wasted effort, lost code, broken commitments, and a new wave of skepticism toward platform promises.

    The long-term impact is already visible:

    Developers are increasingly hesitant to share their best work on public platforms for fear it will be extracted, repackaged, and monetized by corporate actors without consent or fair return.
    Communities fracture, as trust erodes and contributors seek alternative venues or attempt to rebuild trusted enclaves outside Big Tech’s reach.
    Innovation slows, as the collaborative advantage of open source is replaced by guarded, siloed development and legal maneuvering to prevent exploitation.
    Governments and institutions start to question whether global digital infrastructure can be trusted at all, leading to regulatory walls, data localization, and a new era of digital sovereignty where nations must assert control over their technology dependencies to protect their agency and interests.

    This is not just about code or business models. It is about the collective investment of millions of developers worldwide—years of unpaid, voluntary, and mission-driven work that made GitHub the backbone of modern software. That trust, once lost, cannot be restored by marketing or legal boilerplate. It is about digital agency and the fundamental right to control one’s own digital assets, collaborations, and infrastructure choices without the threat of unilateral interference, commercial extraction, or external lock-in.

    Big Tech’s willingness to break trust for short-term advantage is sowing the seeds for a world where the promise of open, global collaboration and shared digital sovereignty is replaced by suspicion, legal battles, and technical walls. The more platforms like GitHub are captured and redirected for private enrichment, the less likely it is that the next generation of developers, communities, or nations will believe in or participate in open source at all.

    Without trust, open source collapses. Without sovereignty, collaboration corrodes. And once credibility is gone, it is almost impossible to rebuild.

    The world is watching, not your assurances, but your actions.

    These concerns are not academic or hypothetical. They reflect the real and growing alarm expressed by thousands of developers, project leaders, digital sovereignty advocates, and policymakers worldwide. Digital sovereignty is not a slogan, but a legal and strategic reality, shaping government, enterprise, and technical policy from the European Union to Asia and the Global South. No reassurances, PR statements, or cherry-picked open source releases can substitute for the specific, transparent, and enforceable commitments demanded here. The complexity and length of this letter are necessary because the stakes—for global innovation, autonomy, and trust—could not be higher.

    The following questions must be answered directly, with transparency, not PR spin. This is about the survival of open source as a trusted, collaborative foundation for global innovation, and about the preservation of digital sovereignty and agency for everyone who relies on these platforms.

    1. Do you acknowledge that folding GitHub into Microsoft’s CoreAI division and revoking its independence directly contradicts your explicit public commitments to keep GitHub open and independent? If not, what specific facts justify your claim that these moves are not a corporate takeover and betrayal?

    Microsoft pledged that GitHub would remain independent, open, and developer-first. Integrating GitHub into CoreAI, eliminating operational independence, and repurposing it as a pipeline for Microsoft’s AI ambitions is the very definition of a corporate takeover.

    2. What concrete, legally binding measures will you implement, beyond policy statements, to guarantee that GitHub will never be used as a captive data source for Microsoft’s proprietary AI models or to lock developers and organizations into your ecosystem, undermining their digital sovereignty and agency?

    The world sees this as a strip and extract operation: first mining community content, then enclosing it, and finally locking developers, communities, and entire organizations into Microsoft’s ecosystem, which is the opposite of open source and sovereign control.

    3. What immediate, auditable steps will Microsoft take to repair the breach of trust with developers and platform stakeholders—including independent oversight and enforceable guarantees—to prove that GitHub will not be exploited for Microsoft’s commercial gain or to undermine the digital sovereignty of its users?

    Repeated public promises were made that GitHub would retain its developer-first values and open extensibility. The loss of trust is not just about business decisions—it is about whether open source contributors, organizations, and governments can ever again believe in the commitments of those who control their code, collaboration, and infrastructure.

    4. Will Microsoft commit, by enforceable policy and public documentation, that no public GitHub repositories will be used for training proprietary AI models or commercial products without explicit opt-in consent from project owners, thus protecting the digital agency and autonomy of all contributors?

    Developers globally are concerned that their open source contributions are being silently harvested for commercial AI without consent, attribution, or compensation.

    5. Will Microsoft provide developers and organizations with granular, real-time tools to track and control every instance where their code or metadata is accessed, processed, or used for AI or commercial purposes, along with a public log of such activity—empowering all users to exercise digital agency over their work and assets?

    Developers have a right to track and control use of their code in AI and data pipelines. Sovereign organizations and communities have an equal right to transparent control over their assets and digital infrastructure.

    6. Will Microsoft legally guarantee that all GitHub users retain unrestricted rights and technical means to export or migrate their code, data, and issue history at any time, without penalty or delay, and that no feature or license changes will restrict this freedom or diminish their digital sovereignty?

    The health of the open source ecosystem depends on freedom of movement, agency, and interoperability—not closed integration with any vendor’s stack or barriers that undermine organizational or national self-determination.

    7. Will Microsoft commit, by contract and technology, to never implement, enable, or cooperate in any form of kill switch, access denial, or politically motivated censorship affecting GitHub projects, regardless of pressure from governments or commercial interests—thus respecting the digital sovereignty and agency of all users worldwide?

    Centralization amplifies the risk of politically or commercially motivated interference in developer access, especially during periods of geopolitical tension. Digital sovereignty means ensuring no single entity can unilaterally block, censor, or deny access to critical digital assets.

    8. Will Microsoft agree to continuous, binding, independent audits of GitHub’s operations, with real enforcement power and board representation for open source foundations such as the Linux Foundation, FSF, or OSI, to safeguard the sovereignty and agency of the broader community?

    A platform of GitHub’s global importance cannot be accountable only to its corporate owner. Recognized foundations must be invited to participate in this oversight. No internal Microsoft committee or advisory board can substitute for independent, enforceable, foundation-driven oversight with real transparency, developer representation, and binding authority. Only governance with teeth can rebuild trust and protect digital agency.

    9. Will Microsoft publish a full, advance public record of all technical, legal, and policy changes that affect GitHub’s integration with Microsoft’s AI and cloud infrastructure, including any changes to data access, contributor rights, or project governance—providing all stakeholders with the information they need to protect their digital sovereignty and agency?

    Developers, organizations, and governments need to understand the real scope of integration, dependencies, and any hidden impacts on autonomy, sovereignty, or compliance.

    10. Will Microsoft publicly accept binding legal and financial liability, including retroactive remedies, if any use of GitHub code, data, or metadata for AI or commercial purposes is found to violate open source licenses, contributor agreements, relevant law, or the digital rights and sovereignty of its users?

    The risk of legal and ethical breach is not theoretical—it is a live issue globally. This letter calls for binding, publicly auditable commitments, not ambiguous legalese, policy footnotes, or unenforceable pledges. The stakes demand real-world, transparent, and contractually enforceable action.

    Specific Remedies the Community Expects

    To ensure that trust is restored and preserved, and to provide the minimum foundation for moving forward in a world where digital sovereignty and agency matter, the following concrete remedies should be enacted:

    Restore an independent GitHub CEO and governance board, separate from Microsoft’s AI, cloud, and product divisions, with real authority and transparency to protect community interests and platform autonomy.
    Publish and enforce a clear, public data use and extraction policy for AI and all other Microsoft product development, including explicit opt-in or opt-out for project owners regarding code, metadata, and issue data, respecting the digital sovereignty of every contributor and community.
    Submit to regular, external audits by recognized organizations such as the Linux Foundation, Free Software Foundation, or Open Source Initiative, with findings published in full to ensure accountability and agency for all stakeholders.
    Contractually guarantee migration and export rights for all repositories and developer data, ensuring there are no technical, legal, or policy barriers to leaving the platform, thus safeguarding the freedom and digital sovereignty of every user.
    Publish quarterly transparency reports detailing code access, AI extraction activity, and all data-sharing between GitHub and Microsoft’s internal systems, giving all users the visibility needed to maintain their own agency and control.

    Pointing to isolated positive actions or PR initiatives does not address the irreversible structural shift underway, nor does it remedy the breach of trust caused by consolidating platform power without transparent, community-backed guarantees.

    What happens next matters. If these concerns are not addressed openly and concretely, many developers, projects, organizations, and even governments will have to reconsider their continued trust in GitHub’s stewardship and Microsoft’s commitments to open source and digital sovereignty. Major voices in the community are already calling for alternatives and greater scrutiny of platform governance. I encourage other developers, open source advocates, digital sovereignty experts, and independent observers to follow this issue closely and demand real accountability for the future of digital collaboration and autonomous control.

    I invite Microsoft, and you personally, to respond to these questions in a public forum or published statement so the entire developer and digital sovereignty community can judge for themselves whether these concerns will be taken seriously and addressed with binding commitments. Setting a clear, reasonable timeline for such a response—for example, within 30 days—would show respect for the global community that helped make GitHub what it is.

    If no substantive answers are provided, many will conclude that Microsoft is unwilling to rebuild trust or respect the values that made open source and digital sovereignty possible in the first place. If silence or spin is all that follows, developers, communities, and national stakeholders will begin organizing alternatives, engaging with independent foundations for oversight, and calling for regulatory scrutiny of platform stewardship on an industry-wide scale.

    What Microsoft does next will set a precedent for all of Big Tech. This moment is about more than one company or one platform. It is about whether open source, digital sovereignty, and the collective trust, investment, and creativity of millions can survive in an era of corporate consolidation and broken promises.

    While I am only one voice among many, thousands of developers, project leaders, and digital-sovereignty advocates echo these concerns. The false assurances made in 2018, documented above, are the root cause of this collapse of credibility. We have no interest in PR spin, empty reassurances, or legal jargon. Only real, specific action and binding commitments will be accepted by the community. Thank you for your attention. The world is watching what you do next.

    Sincerely,

    Dion Wiggins

    A concerned developer of 40+ years, writing in solidarity with the global open source and digital sovereignty community

    #OpenLetter #Microsoft #GitHub #OpenSource #DigitalSovereignty #CoreAI #Developers #Betrayal #Trust #AI

    #Intelligence_artificielle #Emmerdification #GitHub #Microsoft #Logiciel_libre #Economie_numérique

  • (1) GitHub’s Fall: Microsoft’s AI Takeover, Developer Betrayal, and the Next Fight for Digital Sovereignty | LinkedIn
    https://www.linkedin.com/pulse/githubs-fall-microsofts-ai-takeover-developer-betrayal-dion-wiggins-oyetc/?trackingId=9%2BXyAt0nQPavxozgN2eU%2Fw%3D%3D

    Un très bel exemple d’emmerdification.
    L’internet est globalement bâti sur la confiance. Les plateformes ont tué cette confiance. Que reste-t-il ?

    Dion Wiggins
    Dion Wiggins
    CTO at Omniscien Technologies | Board Member | Strategic Advisor | Consultant | Author
    15 août 2025

    Microsoft’s Assimilation of GitHub Is Another Step in the Death of Platform Trust, the Rise of AI Extraction, and the Global Struggle to Reclaim Digital Sovereignty

    TL;DR:

    Microsoft’s full-scale takeover of GitHub is the final blow to developer trust, turning the world’s open source backbone into proprietary AI fuel and erasing any illusion of platform neutrality. Once again, promises were made, trust is broken; just another step in content theft that Big Tech and Big AI think they can get away with. Developers, governments, and organizations worldwide are now at the mercy of corporate and geopolitical power plays. The only way forward is community-led rebellion, a new, truly sovereign commons, before software freedom is lost for good.
    Introduction

    Let’s be brutally clear:

    Microsoft’s decision to fully absorb GitHub into its AI empire marks the end of any pretense of independence, neutrality, or respect for the developer community.

    This is not some routine restructuring. It is a hostile act, engineered by one of the most powerful tech monopolies on the planet, to seize control of the world’s open source infrastructure and weaponize it for corporate AI extraction.

    Long before GitHub, back when I started coding in 1981 on a Sinclair ZX81, sharing code meant something fundamentally different. We passed around code through magazines, printed in HEX or Sinclair BASIC, pages you painstakingly typed in line by line. The real learning didn’t come from retyping the code from the magazine. It came from the hours spent debugging, chasing down errors, and deciphering the logic behind every command until you understood what was really happening under the hood. You had to, because you were almost guaranteed to make a few typos. That shared struggle built a culture of trust, resilience, and real collaboration. We were communities long before platforms, and every bit of progress came from open sharing, not corporate gatekeeping.
    Contenu de l’article
    This is what sharing code looked like when trust was built by communities, not platforms. If you didn’t learn by debugging pages like this, you missed what real collaboration meant.

    Since that time, I have coded in 33 programming languages and on even more hardware platforms. The languages ranged from CICS COBOL on IBM 3090 Mainframes, dBase, Paradox, C, C++, Java, Python, and many more. I have seen, and built for, eras where the stack was closed, open, fractured, and federated. The unifying theme was always the same: community, mutual reliance, and the freedom to learn from and build on each other’s work.

    We moved on to share code via BBS, then floppy disks traded at user groups, Usenet groups, FTP servers, and early web forums. Each shift in medium changed the speed and reach, but not the spirit. Sharing was learning, but the goal was our benefit: we shared because we all gained. The incentive was to solve problems together, to advance our own projects, and to make each other better—not to feed a distant corporate engine or surrender ownership for someone else’s profit cycle.

    As the internet matured, so did the ways we collaborated. We evolved through centralized hosting platforms like SourceForge, Google Code, Bitbucket, and others that tried to streamline sharing and version control for a new generation of distributed teams. Each new tool promised greater freedom and productivity, but also laid the groundwork for new forms of dependency. Progressively, GitHub became the default home of the world’s open source code, a place that was supposed to serve the developer community above all else. For a time, it did.

    GitHub earned our trust through transparency, reliability, and a relentless focus on developer needs. It was a place where anyone, from student to CTO, could contribute, fork, learn, and share. Over time, it took over and became the home of nearly all developers, or at the very least, the place everyone drew from to solve problems, learn new approaches, or see how the best in the field worked. GitHub wasn’t just a platform. It became the backbone of modern software and the largest collective repository of technical knowledge, learning, and creativity the world has ever seen.

    Microsoft acquired GitHub in 2018, and concerns were immediately raised across the developer world. This was the same Microsoft whose executives had, for years, publicly denounced open source—famously calling Linux a “cancer” during the Ballmer era.

    Microsoft promised to behave, swearing public loyalty to open source and pledging non-interference. But we should have known better. If you trusted Microsoft to keep its hands off, you ignored decades of precedent.

    Six years later, that promise is void.

    History shows exactly how this script plays out: trust is extended, compliance is promised, and the moment the calculus changes, those promises are discarded in favor of control and profit.

    On July 3, 2024, GitHub slammed the door on over 8 million developers overnight, limiting access to repositories in sanctioned countries with zero warning and zero recourse. Years of work, public sector infrastructure, and countless collaborative projects were cut off at the stroke of a pen—no appeals, no explanation. One developer’s message summed up the impact: “I woke up and years of work were gone—no warning, no appeal, just a wall.” This wasn’t just a technical incident. This was entire digital economies, civic tech initiatives, and national R&D pipelines unplugged in a single act of compliance theater.

    If you are a developer, founder, policymaker, or anyone who actually cares about digital sovereignty, understand this: what just happened to GitHub is not just a platform betrayal. It is a textbook case of platform capture, content theft, and the industrialization of trust violation at a global scale. Eight million developers, hundreds of thousands of organizations, and entire national digital strategies, locked out with a single boardroom decision.

    This isn’t some far-off warning, it’s reality. If you think your platform, your contract, or your sovereignty is safe, look at GitHub and understand: nobody is immune. This is not only about open source. This is about who controls infrastructure, who sets the terms of participation, and who gets to decide when you are switched off.

    Trust is not eroded over time. Trust is extracted, spent, and discarded the second it gets in the way of a corporate agenda. Microsoft’s move is a warning shot to every government, industry, and developer who still believes in platform neutrality or the fantasy of corporate stewardship. The evidence is in: the era of “safe” digital infrastructure is over, and the price of complacency is total dependency.

    If you’re still betting your future on platform promises, understand: what happened to GitHub isn’t the exception. It’s the new rule.
    The End of GitHub’s Independence: Bait, Switch, and Betrayal

    GitHub was once our home. Developers built it line by line, repo by repo, believing it would always be a place governed by community, transparency, and consent. Microsoft bought it for $7.5 billion in 2018, promising independence and respect for what made GitHub special.

    Satya Nadella stated in June 2018, “GitHub will retain its developer-first ethos and operate independently to provide an open platform for all developers.” Just six years later, that promise is officially void.

    Satya Nadella, Thomas Dohmke, and every exec in sight paraded the same lines:

    "We will keep GitHub separate. We will honor the open source community. We will not interfere.” - They lied!!!

    Anyone who still believes those statements is ignoring the entire playbook of tech consolidation.

    Fast forward: Microsoft tossed those promises aside the second it became profitable to do so. Thomas Dohmke is out. The buffer between the world’s developer commons and a trillion-dollar AI behemoth has been erased. No more “operating as a separate company.” GitHub is now a naked asset on Microsoft’s balance sheet. Your code, your contributions, your project histories, and the entire behavioral exhaust of decades of global software collaboration are now just another dataset for Microsoft’s AI machine. No loyalty, no consultation, no apology.

    This is a direct breach of trust. Microsoft’s assurances were always a lie of convenience. Trust was not eroded over time; it was extracted and spent, then weaponized for shareholder value. If you still think “platform neutrality” exists under corporate ownership, you have not been paying attention.
    Trust Broken Again: If Microsoft Lied About GitHub, What Makes You Think You’re Safe?

    Let’s cut the spin—Microsoft’s betrayal of GitHub isn’t just a footnote. It’s a massive, public display of how little the company values its own commitments, and it should send shockwaves through every organization, government, and IT leader still betting their business on Microsoft’s promises.

    If Microsoft will gut the world’s biggest open source platform for a quick AI land grab, what stops them from doing the same with Azure, Office 365, Teams, LinkedIn, or even Windows? The answer is nothing. When trust is disposable and every “independent” product is one boardroom meeting away from total assimilation, all assurances are worthless.

    This isn’t just about developer tools. Microsoft has a long, ugly track record of buying trust, locking in users, then pulling the rug when convenient: Skype, Yammer, Nokia, LinkedIn, and now GitHub. The real message: user autonomy, sovereignty, and even contractual guarantees are just PR camouflage for an extraction business model. The minute your data, infrastructure, or community is useful to Microsoft’s next product cycle, they will rewrite the rules, lock the doors, and leave you with nothing but a press release and an invoice.

    So ask yourself: if “operational independence” at GitHub was vaporized overnight, why do you think your cloud, your data, or your contracts are sacred? How long before “Azure Sovereign Cloud” or “data residency” are exposed as another bait-and-switch, rewritten in legalese to serve Microsoft’s bottom line?

    Trust is dead. If you’re still handing Microsoft the keys, you’re next in line. Plan your exit, or wait your turn to be betrayed.
    Developer-First Is Dead: Welcome to the Age of AI Extraction

    The narrative shift is complete. The question is no longer “What do developers need?” It is now “What does Microsoft’s AI pipeline need next?” Every signal from the open source ecosystem will now be surveilled, productized, and stripped for anything that can fuel Microsoft’s proprietary Copilot models or whatever AI monstrosity Redmond dreams up next.

    What does this mean in practice? Billions of lines of code, much of it published under licenses like GPL, MIT, and Apache, are being siphoned off for AI training, often in violation of license terms and always without meaningful consent. In November 2022, a class action lawsuit (Doe v. GitHub, Microsoft, OpenAI) was filed accusing Microsoft of “systematically violating open source licenses by using code for AI training without compliance or attribution.” This isn’t just academic: the legal and compliance risks are now headline news, and Microsoft’s only real response has been to double down on integration, not transparency or consent.

    Copilot’s entire existence is a monument to this content heist: scraping, remixing, and monetizing work created by others, then hiding it behind black-box APIs. If you are an artist, writer, or musician, this story should sound familiar. The exact same playbook is being run: take the community’s work, declare it fair game, enclose it in a proprietary system, and dare anyone to fight back in court.
    Big AI’s Pattern: The War on Consent

    Microsoft’s capture of GitHub is not a one-off blunder. It is part of a relentless pattern of Big AI and Silicon Valley platform capture. The sequence never changes:

    Win community trust with promises of independence and “do no evil.”
    Extract maximum value and user data while compliance and transparency are still assumed.
    Change the rules, citing “innovation” or “efficiency” as cover for unilateral decisions.
    Lock in users by making alternatives inconvenient or technically inferior.
    Weaponize user data and contributions as proprietary fuel for corporate AI.
    Rewrite the ethical narrative after the fact, hoping developer outrage will fade.

    Every major tech platform that swore to serve the public now serves its investors and partners, from YouTube to Facebook to GitHub. The result is always the same: creators lose agency and ownership, and their work is turned into untraceable fuel for corporate AI. In the case of GitHub, this theft is not just creative or economic—it is existential. The source code for the world’s infrastructure, supply chains, critical systems, and national digital ambitions is now held hostage to Microsoft’s product cycle and the whims of US law and policy.
    Geopolitics: Software Sovereignty as a National Security Issue

    If you are not worried about the geopolitical dimension, you are sleepwalking into disaster. GitHub is now an explicit US strategic asset, giving Microsoft and the US government de facto leverage over the global software supply chain. Think this is just rhetoric? Ask the countries, companies, and NGOs who have found themselves suddenly cut off from cloud services, developer tools, or code access because they fell on the wrong side of a sanction or export control order.

    Dependency is now risk, and risk is now the default state for anyone outside Microsoft’s immediate reach. This is not theoretical. It is happening in real time. In 2019, GitHub blocked access for developers in Crimea, Iran, and Syria, instantly severing entire regions from open-source collaboration overnight as a result of US government sanctions. Projects, user accounts, and critical repositories were rendered inaccessible without warning, demonstrating exactly how quickly a platform under US control can become a geopolitical chokepoint.

    This is only accelerating as AI becomes the core of economic, military, and political power worldwide.
    The Real Human Cost: Developer Community and Identity Under Attack

    This isn’t just about code. This is about identity. Developers made GitHub what it was. The betrayal here is personal, and it is permanent. This was supposed to be the era of open collaboration and peer-driven software. Instead, we are watching the industrialization of trust violation. The OSS world is being strip-mined for raw material and left with nothing but glossy blog posts and “AI innovation” press releases in return.

    Do not underestimate the irreversibility of this shift. Once a generation of code and developer metadata is absorbed into Microsoft’s AI models, it cannot be reclaimed, re-licensed, or erased. The damage is permanent, not cyclical.
    The Only Real Answer: Wikipedia for Code, Community Rebellion, and True Sovereignty

    There is a way out, but only if the community wakes up. Every monopoly move sows the seeds of its own disruption. The next platform must not be another VC-backed honeypot or government proxy. It must be a real public good, with transparent, democratic governance, legal guarantees against extraction, and technical safeguards against future capture. A Wikipedia for code, built by and for the people who actually write the world’s software.

    This means open governance, clear user ownership, funding models that do not rely on surveillance or advertising, and explicit legal structures to prevent future consolidation. If you care about open source, digital sovereignty, or even basic creative justice, it is time to stop waiting for rescue and start building. The only thing more dangerous than Microsoft’s AI-first strategy is developer inertia in the face of it.
    Bottom Line

    Microsoft’s capture of GitHub is not just another corporate merger. It is a milestone in the ongoing war over who owns the future of software and, by extension, digital society. The era of developer-first collaboration is over. What replaces it depends on what the global community does next. If we let this pass, we are complicit in the theft of a generation’s work and the creation of a world where software freedom is just a nostalgic memory.

    Trust is gone. The buffer is gone. Your code is now their commodity. This is your final warning. Either build the next great commons, or watch everything you created become another trophy for Big AI.

    The takeover of GitHub is not a story about one company or one platform, it is a warning shot fired at the very foundation of modern digital society. Every developer, every business, every government who shrugs this off is handing Microsoft the keys not just to code, but to the future of innovation, collaboration, and control itself. The era of platform trust is over. The game now is raw leverage, forced dependency, and the systematic stripping of everything that made open source powerful in the first place.

    Microsoft is not alone. Big AI and Big Tech across the board have been emboldened by years of weak oversight and complacency. They are moving in lockstep, seizing communities, centralizing infrastructure, rewriting the rules, and building business models on the backs of your labor and your trust. From Google to Amazon to Meta and beyond, the playbook is always the same: capture the commons, extract the value, lock the doors, and dare anyone to challenge the new order. They are not competing for users, they are dividing up the future.

    Access is not a technical privilege, it is a geopolitical weapon. The value created by global contributors can be seized or blocked in an instant, at the whim of corporate or national interests.

    This is the real risk. When access can be blocked or revoked at the whim of a corporation or by the order of a foreign government, sovereignty is a fantasy. Your work, especially in open source, was never meant for just the community that Microsoft or the US government happens to approve of this week. It was meant for the world, for anyone with the curiosity and drive to build. Now, that universal promise is being systematically dismantled and replaced with selective, politicized exclusion. Access, participation, and even recognition itself are now contingent—not on merit, but on compliance with the agenda of whoever holds the keys. When your contributions can be walled off, seized, or deleted by a platform operator or foreign sanction, the danger is not just economic or technical. It is a threat to global collaboration, to knowledge itself, and to the very principle of shared human progress.

    True digital sovereignty means unconditional, universal access and control. Anything less is just dependency, leaving you at the mercy of platform owners or the political whims of their government.

    If we allow this to stand, we are not just complicit in the loss of a generation’s work—we are witnesses to the extinction of software freedom as a living reality. There are no more neutral platforms, no benevolent stewards, and no second chances. Act now. Reclaim your code, build new institutions, and refuse to let Big AI’s hunger write the rules of your world. If you do not, everything you create will belong to someone else, locked away and weaponized against you.

    This is not just the end of an era. It is the start of a new digital regime where trust is dead and sovereignty is what you take back, or you lose forever.

    #GitHub #Microsoft #OpenSource #AIGovernance #Sovereignty #ContentTheft
    About the Author

    About the Author Dion Wiggins is Chief Technology Officer and co-founder of Omniscien Technologies, where he leads the development of Language Studio—a secure, regionally hosted AI platform for digital sovereignty. It powers translation, generative AI, and media workflows for governments and enterprises needing data control and computational autonomy. The platform is trusted by public sector institutions worldwide.

    A pioneer of Asia’s Internet economy, Dion founded Asia Online, one of the region’s first ISPs in the early 1990’s, and has since advised over 100 multinational firms, including LVMH, Intuit, Microsoft, Oracle, SAP, IBM, and Cisco.

    With 30+ years at the crossroads of technology, geopolitics, and infrastructure, Dion is a global expert on AI governance, cybersecurity, and cross-border data policy. He coined the term “Great Firewall of China”, and contributed to national ICT strategies—including China’s 11th Five-Year Plan.

    He has advised governments and ministries across Asia, the Middle East, and Europe, shaping national tech agendas at the ministerial and intergovernmental level.

    As Vice President and Research Director at Gartner, Dion led global research on outsourcing, cybersecurity, open-source, localization, and e-government, influencing top-level public and private sector strategies.

    He received the Chairman’s Commendation Award from Bill Gates for software innovation and holds the U.S. O-1 Visa for Extraordinary Ability—awarded to the top 5% in their field globally.

    A frequent keynote speaker and trusted advisor, Dion has delivered insights at over 1,000 global forums, including UN summits, Gartner Symposium/Xpo, and government briefings. His work has been cited in The Economist, Wall Street Journal, CNN, Bloomberg, BBC, and over 100,000 media reports.

    At the core of his mission:

    “The future will not be open by default—it will be sovereign by design, or not at all.”

    #Intelligence_artificielle #Emmerdification #GitHub #Microsoft #Logiciel_libre #Economie_numérique

  • #github Wants the #EU to Fund #open_source
    https://www.omgubuntu.co.uk/2025/07/github-eu-open-source-funding

    GitHub is urging the EU to create a €350m fund for open source maintenance. But as Big Tech profits, should taxpayers be the ones to pay the tab? You’re reading GitHub Wants the EU to Fund Open Source, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

    #News #foss_fund #Microsoft

  • #Canonical Donating $120,000 to Open Source Projects This Year
    https://www.omgubuntu.co.uk/2025/05/canonical-commits-funds-open-source-devs

    Canonical commits to donating $120k to the open source developers building the projects and tools that help power the Ubuntu ecosystem. You’re reading Canonical Donating $120,000 to Open Source Projects This Year, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.

    #News #github

  • #python is Now the Most Popular Language on #github
    https://www.omgubuntu.co.uk/2024/10/python-most-popular-language-on-github-2024

    Python has overtaken JavaScript as the most-used language on GitHub, according to the code-hosting platform’s latest Octoverse report. The company attributes this momentum to a massive influx of “data science and machine learning on GitHub”, which has seen a 59% increase in the number of contributions to generative AI projects. With Python being heavily used across ML, data science, and related fields, the rise makes sense – it’s less that traditional software developers are switching to Python but more that developers working with AI-related projects are needing to use it. Plus, it’s good #News for open source, with GitHub reporting […] You’re reading Python is Now the Most Popular Language on GitHub, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without (...)

    #developer

  • Tables in Markdown | Codeberg Documentation
    https://docs.codeberg.org/markdown/tables-in-markdown

    documentation de la syntaxe MarkDown pour les tables/tableaux
    NB :
    – à priori fourni en tant qu’extension par la version "GitHub Flavored" MarkDown (GFM) : cf la définition/spécification sur https://github.github.com/gfm/#tables-extension-
    – ne semble pas supporté par la version "Commonmark" MarkDown (cf son absence dans la définition sur https://spec.commonmark.org )
    – ne propose aucune option de fusion de cellules (contrairement à SPIP) : seul MultiMarkdown semble le proposer : cf https://github.com/fletcher/MultiMarkdown/wiki/MultiMarkdown-Syntax-Guide

    #markdown #MD #GFM #GitHub_Flavored #Commonmark #syntaxe #tableau #table

  • Un phénoménal fil de discussion, en anglais, sur la question « Les machines qui pondent du code à la demande en régurgitant du code source digéré dont elles ne sont pas l’auteur et qui initialement était sous licence libre, Microsoft Copilot en particulier, enfreignent elles la loi et la licence libre des logiciels sources qui ont servi à l’apprentissage ? »
    https://news.ycombinator.com/item?id=33240341
    #microsoft #copilot #github #machinelearning #libre #foss #copyright

  • Un assistant dopé à l’IA pour programmer un peu à notre place, avec OpenAI et entraîné sur des milliards de lignes de code par microsoft github. Et on dirait que ça marche : le codeur rédige un prototype de fonction et le commentaire qui décrit ce qu’elle fait (dans Visual Studio ...) et l’assistant rédige le code. Si on lui demande, il propose d’autres versions.
    https://copilot.github.com

    #programmation #IA #deep_learning #github #visualstudio #openAI #text_generation

  • Vous savez, ces insupportables bandeaux cookies trompeurs, mensongers et agaçants que des tas de sites Web affichent ? Microsoft a une excellente solution à ce problème : pas de cookies, donc pas de bandeau cookie.

    https://github.blog/2020-12-17-no-cookie-for-you

    Il faut maintenant espérer (mais ne rêvons pas) que les médias français, tous grands capteurs de données personnelles sur leurs sites Web, suivent cette multinationale étatsunienne sur le chemin de la vertu.

    #informatique_et_libertés #CNIL #GitHub #cookies #RGPD

  • Comment la Chine traque et emprisonne les journalistes citoyens qui racontaient le confinement de Wuhan
    https://www.lemonde.fr/international/article/2020/12/01/coronavirus-comment-la-chine-traque-les-citoyens-enqueteurs_6061721_3210.htm

    Au moins une demi-douzaine de personnes ont été arrêtées. Cette vague de répression révèle la paranoïa de Pékin vis-à-vis de toute version non conforme à la vérité officielle sur le Covid-19. Ils en avaient fait leur passion : archiver sur un système hébergé à l’étranger, la plate-forme américaine GitHub, les contenus – articles de presse ou de réseaux sociaux – qui disparaissent de la Toile chinoise à chaque razzia de la censure. Jamais les autorités n’ont semblé prêter attention à leurs activités, jusqu’à ce (...)

    #GitHub #WeChat #activisme #journalisme #censure #COVID-19 #santé #surveillance

    ##santé

    • Des explications sur : https://docs.radicle.xyz/docs/understanding-radicle/why-radicle
      En raccourci :
      But :

      In a world where nearly all software relies on open source code, maintaining the resilience and health of the free and open source ecosystem is more important than ever. That’s why we believe that dependence on centrally hosted platforms and corporations for the distribution of critical open source infrastructure is unsustainable. Reliance on such centralized services contradicts the values of the free and open source ecosystem and threatens its well-being.

      Principes :

      Designing by principles
      As we set out to build an alternative, we started by thinking about the values that we recognize as integral to free and open source code collaboration. With that said, we developed the following list of guiding principles:
      1. It must prioritize user freedom In the words of the free software movement
      2. It must be accessible and uncensorable
      3. It must be user-friendly
      4. It must be offline-first
      5. It must not compromise on security

      Fonctionnement :

      Radicle’s approach is meant to return to the protocol-first philosophy by focusing on building code collaboration primitives instead of user experiences, and to reject data collection and siloing by intermediaries. This is reflected in the decision to build on and extend git. Having it as the nexus of replication builds on its strengths and decentralized nature. Having issues, pull requests, comments, and reviews locally gives developers the tools to manage and design their workflows without locking them into a new “experience”. Despite any front-end interface that will be built (😉), Radicle exists foremost as an open protocol — not a platform.

      Pour le « comment ça marche » : https://docs.radicle.xyz/docs/understanding-radicle/how-it-works

      #développement #collaboratif #protocole #github #gitlab #bazaar

  • En rentrant dans de prestigieuses bibliothèques, le logiciel libre gagne ses lettres de noblesse
    https://www.lemonde.fr/economie/article/2020/11/19/en-rentrant-dans-de-prestigieuses-bibliotheques-le-logiciel-libre-gagne-ses-

    L’entreprise américaine GitHub, propriété de Microsoft, sauvegarde des millions de lignes de langage informatique, qui vont être accueillies dans les bibliothèques d’Alexandrie, d’Oxford et de Stanford. Véritables temples du savoir, les bibliothèques d’Alexandrie (Egypte), d’Oxford (Royaume-Uni) et de Stanford (Etats-Unis) abritent parmi les écrits les plus précieux de l’humanité, jusqu’aux plus anciens. Mais c’est un véritable bond dans la modernité qu’elles viennent d’effectuer. A l’invitation de (...)

    #Microsoft #GitHub #copyright

  • GitHub Archive Program | Preserving open source software for future generations
    https://archiveprogram.github.com

    The world is powered by open source software. It is a hidden cornerstone of modern civilization, and the shared heritage of all humanity. The GitHub Archive Program is a testament to the importance of the open source community. It is our hope that it will, both now and in the future, further publicize the worldwide open source movement ; contribute to greater adoption of open source and open data policies worldwide ; and encourage long-term (...)

    #Microsoft #GitHub #copyright

  • La clé privée du système de #DRM #Widevine (utilisé notamment par Netflix et le service VOD d’Apple) a fuité. Google (propriétaire du système en question) essaie de boucher les trous, mais, sur Internet, il est difficile de « défuiter » une information.

    La requête DMCA de Google à Github pour demander la censure des dépôts où se trouvait la clé (et le code)
    https://github.com/github/dmca/blob/master/2020/11/2020-11-09-Google.md

    Un résumé de l’affaire : https://torrentfreak.com/google-takes-down-repositories-that-circumvent-its-widevine-drm-201113

    Le site Web officiel https://www.widevine.com

  • #ýoutube-dl est un logiciel libre permettant de télécharger des vidéos depuis plusieurs plateformes de distribution (pas seulement #YouTube). Il était distribué à partir de la plateforme de développement de logiciels #GitHub (le Facebook des geeks), propriété de #Microsoft. Il vient d’être retiré, sans discussion et sans possibilité pour l’auteur de se défendre (à la cow-boy, comme souvent aux États-Unis) suite à une demande #DMCA de la #RIAA, le lobby d’Hollywood.

    L’ancien dépôt : https://github.com/ytdl-org/youtube-dl

    La lettre de la RIAA : https://github.com/github/dmca/blob/master/2020/10/2020-10-23-RIAA.md

    L’article de TechCrunch : https://techcrunch.com/2020/10/23/the-riaa-is-coming-for-the-youtube-downloaders

    Celui de ZDnet : https://www.zdnet.com/article/riaa-blitz-takes-down-18-github-projects-used-for-downloading-youtube-videos

    Un miroir (assez chargé en ce moment mais je pense que d’autres apparaitront) : https://git.rip/mirror/youtube-dl

    #copyrightMadness #appropriationIntellectuelle

  • Dans l’Arctique, une entreprise sauvegarde la culture humaine | korii.
    https://korii.slate.fr/tech/arctique-piql-entreprise-sauvegarde-stocke-donnees-culture-humanite-arct

    L’île norvégienne de Spitzberg abritait déjà la Réserve mondiale de semences du Svalbard ; elle pourrait bientôt héberger une #réserve mondiale de #données. « Gérée par la société […] Piql, l’Arctic World Archive vise à préserver les #matériaux_numériques du monde –musique, littérature et lignes de code– pendant plus de 500 ans », explique The Hustle.

    La plateforme #GitHub, qui permet aux développeurs et développeuses de mettre en ligne et sauvegarder leurs programmes, a déjà confié l’intégralité de son code à l’archive, soit 21 terabits (1.012 bits).

    Mais pour quoi faire ? Il s’agit tout simplement de protéger ces données pour au moins 500 ans contre les catastrophes humaines ou naturelles (et contre tout ce que 2020 nous réserve encore).