AI Weekly Malaysia

OpenDLSS-NR is a Vulkan reimplementation of NVIDIA's DLSS 5 Neural Rendering network that claims bit-exact output against DLSS-NR build 310.8.0, matching not just the final image but all 75 block boundaries byte for byte. The network is a 71-block shifted-window Swin/ViT U-net over six pooling levels, 141 MiB of weights, FP8 (E4M3) activations with FP16 accumulation, and it is not an upscaler — it re-renders an already-drawn frame at the same resolution. A second, independent implementation under ports/browser-webgpu/ runs the same bytes in a browser at 2048x1152 with no tensor cores and no FP8 support; users must supply their own weights. The repo has 702 stars, 60 forks and only 4 commits, with a 220-point / 103-comment Hacker News thread.

Why: The browser WebGPU port is the concrete takeaway: the same network runs without tensor cores and without FP8, which means browser-side neural inference at 2048x1152 is demonstrably possible without the hardware features people assume are mandatory — worth testing before you default to server-side GPU inference for a rendering or post-processing feature. Note the practical limits before planning anything: you must supply your own weights (nothing is shipped), the repo is 4 commits deep, and the claims of byte-exactness come from the author, not an independent benchmark. There is no Malaysia or Southeast Asia angle in this item.

Yash Garg documents routing a PS5's broadcast stream to a local machine instead of Twitch, because the PS5 has no native Discord screen sharing and a capture card costs upwards of $100. The key finding is that the PS5 resolves ingest.twitch.tv via DNS on every broadcast, but that host is only a discovery endpoint — it returns a regional ingest hostname like ap-southeast-1.prod.fi.contribute.live-video.net, where the real stream is pushed. Spoofing that ingest host runs into RTMPS (RTMP over TLS on port 443), and the PS5 validates the certificate against trusted CAs, so a self-signed cert fails.

Why: The practical lesson is that hostname secrecy isn't the control — the discovery-then-ingest split plus CA-validated TLS is. If you build a client that pushes to a vendor endpoint, note that a self-signed cert or a DNS override won't get you past it, and that a two-step discovery call means blocking one hostname isn't enough. The write-up is truncated at the certificate-validation failure, so the actual workaround isn't shown in the text we have.

A public GitHub repository, Relapse-Exploit, publishes a working PS5 exploit chain covering firmware versions 7.00 through 13.60, with 1.3k stars and 304 forks. It chains a browser-stage attack using JavaScriptCore info leaks and a structured clone object pool mismatch to corrupt a typedarray, then a kernel stage combining an address leak with an aio_multi_wait use-after-free race to obtain kernel read/write. Delivery is either by setting the console's Primary DNS to 45.56.67.85 or running the included python serve.py / opening the project's GitHub Pages URL, after which an ELF loader listens on port 9021; the README warns the WebKit stage may need several attempts and the kernel exploit may hang or panic the console.

Why: For this audience the practical impact is close to zero: this is a consumer-console jailbreak and nothing here changes what you ship, deploy, or buy. The one transferable detail is the kernel stage's aio_multi_wait use-after-free race combined with an address leak, which is a concrete chaining pattern worth reading if you do low-level or security research. Note also the delivery model - pointing a device's DNS at a third-party server to run unsigned payloads - which is exactly the pattern you should refuse to follow on any machine holding credentials or customer data.

Tom's Hardware reports that Marvel's Wolverine has reached in-game gameplay on KytyPS5, an emulator project, joining Ghost of Yotei as PS5 exclusives that now boot to gameplay — with performance still measured in single-digit frames per second. The visible article text is almost entirely Tom's Hardware membership and newsletter boilerplate, so it carries no version numbers, hardware specs, commit details, or build instructions.

Why: There is nothing here to change in your stack, and the text gives no release artifact, no repo link, and no hardware configuration — so a developer cannot act on it beyond noting that PS5 emulation is still at single-digit FPS and therefore nowhere near playable. If you were hoping for a usable KytyPS5 build or reproducible benchmark, this item does not provide one.

The private PS5 emulator KyTyPS5 now runs Demon's Souls at 40-50 FPS with accurate graphics, according to Tom's Hardware. That is up from an unplayable 1-2 FPS roughly three weeks earlier, when the game could barely boot. The article body available here is mostly subscription/navigation boilerplate, so no hardware specs, build numbers, or release details are given.

Why: Nothing here changes what a Malaysian developer, AI/ML learner, or SaaS founder should build or buy — there is no API, tool, price, or policy attached to it. Treat it as a hobbyist emulation milestone rather than a signal for your stack; the only transferable detail is the reported 1-2 FPS to 40-50 FPS jump in about three weeks, which is a reminder of how fast small reverse-engineering projects can move, not a reason to act.