Roku 轉移至 GitLab、GrapheneOS 獲銀行應用支援、丹麥 Office 試點及 RTX 4090 效能解鎖

Four developer stories landed in the same weekend, and they share a question: who holds the switch? Roku moved all of its developer code from GitHub to GitLab, GrapheneOS says a dozen banking apps now permit it, Denmark's digitalisation ministry reportedly shelved its open source Office pilot, and a new GitHub repository claims to double the tensor throughput of an RTX 4090. This roundup reads each primary source, says what it confirms, and says what it leaves open.

TL;DR

Roku's developer blog says it finished moving its documentation, sample apps and tooling repositories from GitHub to GitLab. Repository names are unchanged, only the host differs, and the post gives no reason.
Roku's own warning is the useful part: a stale index does not raise an error, it quietly serves outdated content. When I checked on October 25, 53 of the 58 rokudev repositories on GitHub were archived and the GitLab group listed 57 projects.
GrapheneOS said on October 23 that around a dozen banking apps began specifically permitting it, around 10 percent of banking apps are unavailable because they ban any operating system Google has not approved, and many apps have memory corruption bugs and incorrect anti-tampering code.
Computerworld Denmark (October 20, paywalled) reports the Danish digitalisation ministry quietly dropped its much-discussed pilot of an open source alternative to Microsoft Office. No reason or date is confirmed.
The gpu-unlock-ada README reports about 2x FP16 tensor throughput on an RTX 4090 in an instruction benchmark and 12 to 34 percent in real matrix multiplies, from single matched run pairs.
Verdict: NEEDS REVIEW. Each story is a switch somebody else holds.

1. Roku moves its developer repositories to GitLab

On October 15, 2026, Roku's developer blog announced that it had "completed migrating all developer resources from GitHub to GitLab." The move covers the developer documentation, the sample apps and the tooling repositories, including the open source parts of its SDK. The post says the impact on developers is minimal and that repository names stay the same, so a repository at github.com/rokudev/<repo> is now at gitlab.com/rokudev/<repo>.

The announcement does not say why Roku moved. The Hacker News thread passed 200 comments, and the most common question was that missing reason. Some readers guessed at GitHub outages, which is a guess, and Roku has not said.

I checked both sides through their public APIs on October 25. The GitHub organization listed 58 repositories, 53 of them archived, which means read-only. The GitLab group listed 57 projects. These are point-in-time counts and a migration can still be settling, so treat the exact numbers as a snapshot.

The most practical paragraph in the post concerns anything that reads those repositories automatically. Roku writes that if you index its repositories to ground a retrieval pipeline, an internal assistant or a coding agent, you should update the source URLs and re-crawl, and that raw file URLs move too. Then comes the line worth remembering: "a stale index does not raise an error, it quietly serves outdated content." An archived GitHub copy still answers requests. Nothing fails, so nothing alerts you.

The checklist from the post is short:

Point each existing clone at the new address with git remote set-url origin https://gitlab.com/rokudev/<repo>.git.
Update the URL in .gitmodules, then run git submodule sync.
Search your own repositories for rokudev and work through the hits, including CI pipelines that clone a repository, fetch a release artifact or install a package from a git URL.
Documentation fixes now go through a merge request on GitLab, because the "Suggest edits" feature is not supported there.

2. A dozen banking apps now permit GrapheneOS

GrapheneOS posted on Mastodon on October 23 that most banking apps work on GrapheneOS, and that "around a dozen banking apps began specifically permitting GrapheneOS in addition to a Google-approved OS." It also said around 10 percent of banking apps are unavailable because they ban any operating system Google has not approved. The post does not name the apps. A crowd-sourced list at PrivSec tracks user reports, and the Hacker News discussion ran to 655 points.

The detail I liked is about the apps that do break. According to GrapheneOS, many banking apps have memory corruption bugs and incorrect anti-tampering code, which is why the project ships a per-app switch called exploit protection compatibility mode. In plain terms, some of the most security-minded apps on a phone trip over their own memory bugs when the operating system is strict.

In a later reply, GrapheneOS addressed tap to pay. It said Google Pay bans GrapheneOS and most banks delegate tap to pay to Google Pay, while Curve Pay, PayPal and many European banking apps permit it, and that the European trend of banks moving to Google Pay has largely stopped. GrapheneOS last appeared in our coverage on September 19, when it said Pixels were getting harder to support.

If you ship a finance app, the community list is a record of how your app behaves on GrapheneOS, and it is worth reading what your users report.

3. Denmark's open source Office pilot

In July 2025 the Document Foundation reported that Denmark's digitalisation ministry was moving to LibreOffice, quoting the minister: "We must never make ourselves so dependent on so few that we can no longer act freely."

On October 20, 2026, Computerworld Denmark reported that the ministry has quietly dropped its much-discussed pilot of an open source alternative to Microsoft's Office suite, and its summary names Collabora. The article is behind a paywall. I could read the headline and the first paragraph, and I could not confirm a reason, a date or what happens next. 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.

For comparison, the Dutch NixOS workplace we covered on September 29 was also a pilot, with eight municipalities. Pilots end for many reasons, and a single paywalled report is not enough to pick one.

4. The RTX 4090 unlock: two numbers

A GitHub repository called gpu-unlock-ada appeared on October 23 and had about 2,100 stars two days later. It is a Linux kernel module that sets a speed-select override before the stock NVIDIA driver starts. The README credits a payload analysed in a Hugging Face project and an earlier open source project that it forks.

The headline number comes from an instruction benchmark. On an RTX 4090 the README reports FP16 tensor math with FP32 accumulation going from 165.6 TF/s to 331.6 TF/s, and BF16 from 165.5 to 330.6. That is a doubling.

The second number comes from the same README. In real cuBLAS matrix multiplies, an independent owner run found FP16 gains of 12 to 34 percent and BF16 gains of 16 to 20 percent at two shapes, with essentially no change at a large shape. A single FP8 test on another card moved 0.3 percent. The README calls these single matched run pairs with the desktop active and says they are not whole-application speedups or an extended stability test. It also says other Ada cards are unverified.

This is 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 documentation first. This article gives no installation steps on purpose.

What to do this week

Search your repositories and index configs for rokudev, and re-crawl anything that read the old GitHub URLs.
If you ship a banking or payments app, read the PrivSec list for your app.
If you depend on a pilot to justify an open source move, write down who decides when it ends.
If you benchmark GPUs, measure your real workload and compare it with the instruction rate.

Verdict

NEEDS REVIEW. Each of these stories is a switch somebody else holds: a code host, a phone operating system's approval, a ministry's pilot, and a card's own firmware. Check which of them your own setup depends on.

Sources

This article expands on an episode of **The Daily Diff, a five-minute daily video on what shipped and what broke in tech.
Watch the episode · Subscribe on YouTube · the written diff lands in your inbox every morning at thedailydiff.dev.

Video transcript and primary sources