Watch the video, transcript and sources
- Roku: dev code leaves GitHub
+ GrapheneOS: a dozen bank apps
- Denmark: Office pilot shelved
+ RTX 4090: firmware unlockRoku just moved all of its developer code from GitHub to GitLab. The announcement tells you which links to update. It never says why. The fourth story has two numbers that disagree with each other. I will show both near the end. This is a roundup, so think of it as one pull request with four files and no tests. A TV maker's repositories, a phone operating system, a government's office suite and a graphics card's firmware. Each one is a small fight over who holds the switch.
On October fifteenth, Roku's developer blog said it had finished moving its developer resources from GitHub to GitLab. That covers the documentation, the sample apps and the tools, including the open source parts of its SDK. The repository names stayed the same, so only the host in the address changes. When I checked, fifty-three of the fifty-eight repositories on GitHub were archived, which means read-only. The GitLab group lists fifty-seven projects. The post gives no reason for the move. It does include the warning most people will skip. If an index, an internal assistant or a coding agent reads these repositories, a stale index does not raise an error. It quietly serves old content. The Hacker News thread passed two hundred comments, and the favourite question was the one the post skips. Some readers guessed at GitHub outages. That is a guess, and Roku has not said.
The fix is small. Point each existing clone at the new address with git remote set url. Update the dot gitmodules file and run git submodule sync. Then search your own repositories for the word rokudev. Doc fixes now go through a merge request, because the suggest edits button is not supported on GitLab. GrapheneOS posted late on Friday that around a dozen banking apps have begun to specifically permit it, alongside a Google-approved operating system. Most banking apps already work, the project says. Around ten percent are unavailable, because those apps ban any operating system Google has not approved. Here is the part I liked. For the apps that do run into trouble, GrapheneOS says many have memory corruption bugs and incorrect anti-tampering code. That is why it ships a per-app switch, called exploit protection compatibility mode. So some of the most security-minded apps on your phone are tripping over their own memory bugs.
A reader asked about tap to pay, and the project answered. Google Pay bans GrapheneOS, and most banks hand tap to pay over to Google Pay. In Europe, Curve Pay, PayPal and many European banking apps allow it, and GrapheneOS says the move to Google Pay there has largely stopped. Last time GrapheneOS was on this show, on September nineteenth, the topic was Pixel support. If you ship a finance app, the community list at privsec dot dev is a crowd-sourced record of which apps work on GrapheneOS, so your app is probably already on it. It is worth reading what your users report. In July twenty twenty-five, Denmark's digitalisation ministry said it was testing open source in parallel, and the minister wrote that Denmark must never become so dependent on so few that it can no longer act freely. On October twentieth, Computerworld Denmark reported that the ministry has quietly dropped its much-discussed pilot of an open source alternative to Microsoft's Office suite.
The article is behind a paywall, so I can only tell you what the headline and the first paragraph say. The page names Collabora as the pilot. I could not confirm a reason, a date or what comes next, and I will not guess. A Hacker News reader asked whether the pilot was always a bargaining chip in a licensing negotiation. Nobody in that thread had evidence, so it stays a question. Compare the Dutch NixOS workplace from September twenty ninth, also a pilot with eight municipalities. Now the fourth story. A GitHub repository called gpu unlock ada appeared on October twenty third and already has about twenty one hundred stars. It is a Linux kernel module that sets a speed select override before the stock NVIDIA driver starts. The readme credits a payload analysed on Hugging Face and an earlier project that it forks.
Here is the headline number. On an RTX 4090 the readme measured sixteen bit float tensor math at about one hundred sixty six teraflops stock, and about three hundred thirty two after the unlock. Doubled. The bfloat sixteen format did the same. The people side is a relay race. The payload analysis came from a Hugging Face project, the Linux module is a fork of an earlier project, and a Windows port for one MSI card came from Latence dot app. The readme says other Ada cards are unverified. Now the second number. In real cuBLAS matrix multiplies, the same readme reports sixteen bit float gains between twelve and thirty four percent. Bfloat sixteen gained sixteen to twenty percent at two shapes and barely moved at a large one. A single eight bit float test moved three tenths of a percent. The readme describes these as single run pairs that say little about whole application speed.
My advice is to treat this as third party code that changes a setting underneath your driver. If you try it at all, use a spare machine, and read the repository's own testing page first.
Verdict: NEEDS REVIEW — Four switches someone else holds. Check yours.
Sources
https://blog.roku.com/developer/gitlab-move
https://gitlab.com/rokudev/dev-doc
https://api.github.com/orgs/rokudev/repos?per_page=100
https://gitlab.com/api/v4/groups/rokudev/projects?per_page=100
https://news.ycombinator.com/item?id=50222622
https://grapheneos.social/@GrapheneOS/117492375462459244
https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/
https://news.ycombinator.com/item?id=50217495
https://www.computerworld.dk/art/297226/digitaliseringsministeriet-har-i-al-stilhed-droppet-stort-anlagt-forsoeg-med-open-source-alternativ-til-microsoft
https://blog.documentfoundation.org/blog/2025/07/08/danish-ministry-switching-from-microsoft-office-365-to-libreoffice/
https://news.ycombinator.com/item?id=50223844
https://github.com/JustAResearcher/gpu-unlock-ada
https://news.ycombinator.com/item?id=50223787
https://huggingface.co/TOTORONG/AD103_win_unlocker
https://github.com/Zagitta/gpu-unlock
And that's the diff for today. I'm Niko from Axrisi. Merge responsibly.
YouTube · Newsletter · thedailydiff.dev · forward this to the intern who deployed on Friday.