# Time Published articles for Time. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Libreboot 20230413 released! DevFeed: [Libreboot 20230413 released!]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: release Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [boot](), [Embedded Software Dev](), [x86]() Tags: [bios](), [boot](), [canoeboot](), [coreboot](), [debian](), [error-handling](), [firmware](), [free-software](), [hardware](), [libre](), [libreboot](), [opensource](), [release](), [time](), [uefi]() ### AI overview Libreboot 20230413 is a testing release and bugfix release relative to Libreboot 20230319. The article highlights build-system fixes, code cleanup, improved error handling, and build testing on Debian Sid. It also describes Libreboot's firmware support for selected x86 and ARM machines. ### Source excerpt Article: Libreboot 20230413 released! Web link: https://libreboot.org/news/libreboot20230413.html ## GNOME 51 Released With Improved Frame Scheduling, Many App Improvements DevFeed: [GNOME 51 Released With Improved Frame Scheduling, Many App Improvements]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-16T16:25:21Z Content type: news Language: en Sources: [Phoronix]() Topics: [releases](), [Wayland](), [Release notes](), [Software](), [ui](), [legacy](), [Nvidia]() Tags: [desktop](), [desktop-linux](), [driver](), [experience](), [faster](), [improvements](), [legacy](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [notes](), [nvidia](), [offline](), [open-source-graphics](), [other](), [phoronix](), [phoronix-test-suite](), [protocols](), [release](), [release-notes](), [settings](), [software](), [time](), [ubuntu](), [ubuntu-benchmarks](), [ubuntu-hardware](), [ui](), [wayland](), [workstation]() ### AI overview GNOME 51 has been released with improved frame scheduling and desktop responsiveness, new Wayland protocol support, removal of legacy NVIDIA EGLStreams driver support, and updates to several GNOME applications and settings. ### Source excerpt Right on schedule and in time for appearing in the likes of Ubuntu 26.10 and Fedora Workstation 45, the GNOME 51 desktop is officially released... ## Working Remotely DevFeed: [Working Remotely]() Original publisher: [Read original article]() Author: Khan Academy Published: 2017-10-02T22:00:00Z Content type: opinion Language: en Sources: [Khan Academy]() Topics: [Job]() Tags: [engineering](), [news](), [remote](), [remote-work](), [time](), [web-frontend](), [work]() ### AI overview Scott Grant reflects on working remotely after moving from Silicon Valley to Kingston, Ontario. He explains how remote work expands access to technology jobs outside major hubs and discusses the discipline and routine needed to work effectively. ### Source excerpt By Scott Grant When my wife and I left Silicon Valley in sunny California to return to my ... Read more ## iGaming Fraud Prevention: Key Strategies to Implement DevFeed: [iGaming Fraud Prevention: Key Strategies to Implement]() Original publisher: [Read original article]() Author: Ben Price Published: 2026-09-14T21:00:00Z Content type: article Language: en Sources: [Sift Science]() Topics: [Security, Privacy and Abuse Prevention](), [Exploit](), [math]() Tags: [2025](), [2026](), [acquisition](), [bonus-abuse](), [customer](), [fraud-prevention](), [gaming-fraud](), [igaming](), [igaming-fraud](), [igaming-fraud-prevention](), [industrial](), [marketing](), [multi-account-abuse](), [multi-accounting-detection](), [multi-accounting-fraud](), [network](), [prevent-fraud](), [revenue](), [synthetic](), [time](), [trust-and-safety](), [verification](), [volume]() ### AI overview This article explains how bonus abuse and multi-accounting have become major sources of iGaming fraud. It describes fraudsters exploiting promotional offers through repeated registrations, synthetic identities, stolen credentials, device farms, residential proxies, and synthetic documents, and argues that operators should justify prevention spending by measuring protected revenue. ### Source excerpt While every operator budgets for promotions as a customer acquisition cost, very few budget for the version of that cost that never converts into a real player. Bonus abuse and multi-accounting now account for the single largest fraud category in iGaming, making up 64% of fraud according to a recent study. But unlike chargebacks or [...] The post iGaming Fraud Prevention: Key Strategies to Implement appeared first on Sift. ## A Backward NTP Clock Step Delayed a Python Scheduler's Measurements by Nine Days DevFeed: [A Backward NTP Clock Step Delayed a Python Scheduler's Measurements by Nine Days]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-14T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [Python](), [Linux](), [systemd](), [Single Board Computer]() Tags: [embedded](), [linux](), [ntp](), [python](), [reliability](), [scheduler](), [single-board-computer](), [systemd](), [time](), [wall-clock-time]() ### AI overview A Python scheduler on an embedded Linux device silently stopped running after NTP corrected the system clock backward by about nine days. Because it used wall-clock time to measure elapsed time, the scheduler waited roughly nine days before running again. The article explains why a monotonic clock is the appropriate fix and mentions testing with an injected clock jump. ### Source excerpt time.time() vs time.monotonic() in a Python scheduler: a backwards NTP step delayed runs by nine days. Monotonic durations and a jump-injecting test. ## A File Existence Bug Caused by Checking Its Timestamp DevFeed: [A File Existence Bug Caused by Checking Its Timestamp]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-14T06:30:00Z Content type: article Language: en Sources: [The Daily WTF]() Topics: [bug](), [Development](), [Windows]() Tags: [bug](), [code](), [codesod](), [development](), [files](), [function](), [time](), [windows]() ### AI overview A Pascal system library implements FileExists by checking whether FileAge returns -1. Because FileAge depends on a valid last-write timestamp, files without that timestamp are incorrectly reported as missing. The underlying failure is also not checked for its error code. ### Source excerpt In addition to using an ancient development environment, with terrible UX, Greta also has the misfortune of working in Pascal. Recently, she was diagnosing a bug. The program was reporting that files didn't exist when they definitely existed. She traced the problem down into the system library. Let's see if you can spot what's wrong: { Delphi / Kylix Cross-Platform Runtime Library } { System Utilities Unit } { } { Copyright (c) 1995-2001 Borland Softwrare Corporation } ... function FileAge(const FileName: string): Integer; {$IFDEF MSWINDOWS} var Handle: THandle; FindData: TWin32FindData; LocalFileTime: TFileTime; begin Handle := FindFirstFile(PChar(FileName), FindData); if Handle <> INVALID_HANDLE_VALUE then begin Windows.FindClose(Handle); if (FindData.dwFileAttributes and FILE_ATTRIBUTE_DIRECTORY) = 0 then begin FileTimeToLocalFileTime(FindData.ftLastWriteTime, LocalFileTime); if FileTimeToDosDateTime(LocalFileTime, LongRec(Result).Hi, LongRec(Result).Lo) then Exit; end; end; Result := -1; end; {$ENDIF} function FileExists(const FileName: string): Boolean; {$IFDEF MSWINDOWS} begin Result := FileAge(FileName) <> -1; end; {$ENDIF} The first function here is FileAge, which returns the last modified timestamp on a file. Note the use of FileTimeToDosDateTime, which is a Windows API function. It converts LocalFileTime and stores the date part in the first output parameter (LongRec(Result).Hi) and the time part in the second output parameter (LongRec(Result).Lo). Result, in this case, is our return value. If anything goes wrong, we return -1. The FileExists function then, simply calls FileAge. If it doesn't return a -1, there must be a file there. That's an awkward, weird solution to the problem. There has to be a system call that can answer that question more obviously. But it doesn't seem like it should be blowing up- it looks like it should work. But note that FileTimeToDosDateTime also returns a boolean value. If it succeeds, great, but if it fails, it returns false ## HeyGen x Google Cloud: Bringing Avatar IV to TPUs DevFeed: [HeyGen x Google Cloud: Bringing Avatar IV to TPUs]() Original publisher: [Read original article]() Published: 2026-09-12T11:04:33.891311Z Content type: article Language: en Sources: [Google Developers Blog]() Topics: [Google](), [Cloud](), [Artificial Intelligence](), [Optimization](), [AI Infrastructure](), [Transformer](), [PyTorch](), [Compiler](), [Streaming](), [real-time](), [Hardware](), [API]() Tags: [ai](), [ai-infrastructure](), [api](), [cloud](), [code](), [compiler](), [engineering](), [generation](), [google](), [hardware](), [model](), [optimization](), [performance](), [pytorch](), [real-time](), [streaming](), [time](), [tpu](), [transformers](), [video]() ### AI overview HeyGen and Google Cloud describe porting the 18B+ parameter Avatar IV talking-head video generation pipeline to an eight-chip Trillium TPU host. Using torchax, JAX, XLA, FSDP sharding, Ulysses sequence parallelism, and custom Pallas kernels, the team improved performance by 1.86x for real-time chunked streaming while preserving output quality through strict quality gates. ### Source excerpt HeyGen ported their 18B+ parameter Avatar IV video generation model to Google Cloud's Trillium (v6e) TPUs via torchax and XLA, utilizing FSDP and Ulysses sequence parallelism across an eight-chip mesh. To achieve a 1.86x speedup for real-time streaming, the engineering team pipelined exposed all-to-all collectives, aligned sparse attention block sizes to eliminate mask padding, and bypassed softmax serial dependencies using a precomputed Cauchy-Schwarz upper bound. These custom Pallas kernel and compiler optimizations were deployed only after passing rigorous two-tier quality gates to guarantee byte-identical or mathematically equivalent pixel outputs. ## KDE Plasma 6.8 Remote Desktop To Enjoy Lower Latency Performance DevFeed: [KDE Plasma 6.8 Remote Desktop To Enjoy Lower Latency Performance]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-12T10:07:48Z Content type: news Language: en Sources: [Phoronix]() Topics: [Latency](), [client](), [Wayland](), [Protocol (disambiguation)](), [configuration](), [GUI]() Tags: [configuration](), [desktop](), [desktop-linux](), [image](), [latency](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [performance](), [phoronix](), [phoronix-test-suite](), [release](), [remote](), [switching](), [time](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview KDE Plasma 6.8 improves KRDP remote desktop latency by dropping incoming frames when the encoder outpaces the client. The release also includes input-method, clipboard, Wayland protocol, wallpaper dialog, and XWayland session configuration fixes. ### Source excerpt Along with KDE Plasma 6.8 beta releasing this week, there were some other interesting Plasma changes this week worthy of a shout-out... ## 8 Reasons Your Raspberry Pi Wi-Fi is Slow (and How to Fix it) DevFeed: [8 Reasons Your Raspberry Pi Wi-Fi is Slow (and How to Fix it)]() Original publisher: [Read original article]() Author: Thomas Dyan Published: 2026-09-12T05:00:00Z Content type: tutorial Language: en Sources: [RaspberryTips]() Topics: [Network](), [Network Configuration](), [Linux](), [Command-line interface](), [ssh](), [Terminal](), [Operating system]() Tags: [command-line](), [how-to](), [how-to-tutorials](), [linux](), [network](), [network-configuration](), [raspberry-pi](), [raspberry-pi-os](), [ssh](), [time]() ### AI overview A practical guide to diagnosing and fixing slow Raspberry Pi Wi-Fi. It focuses on common causes such as Wi-Fi power-saving settings, weak signal, incorrect country code, older hardware, and network configuration issues, with initial troubleshooting steps and command-line guidance. ### Source excerpt Whenever my Raspberry Pi is slow over Wi-Fi, I've learned that the problem is usually not the Wi-Fi network itself. Most of the time, it comes down to the Pi's setup. And when you look into it, it's often one of the same few causes. If you're having the same issue, here are the first... ## What It Takes to Run a Mobile App Beta with Real Customers DevFeed: [What It Takes to Run a Mobile App Beta with Real Customers]() Original publisher: [Read original article]() Author: Renee Liken Published: 2026-09-09T12:00:46Z Content type: tutorial Language: en Sources: [Atomic Object]() Topics: [Mobile](), [Testing](), [App]() Tags: [customer](), [delivery-practices](), [features](), [mobile](), [mobile-app-deployment](), [survey](), [testing](), [time]() ### AI overview This tutorial explains how to run focused mobile app betas with real customers before a full release. It recommends testing one feature at a time, keeping the customer request small, recruiting and incentivizing a limited group, and collecting focused feedback through screenshots, recordings, and surveys. ### Source excerpt Earlier this year, our team shipped two mobile app features for BIGGBY® COFFEE that both touch real money: applying loyalty rewards to an order at checkout, and adding a tip when you pay. These are exactly the kinds of features you don't want customers discovering bugs in via one-star reviews. So before each one released [...] The post What It Takes to Run a Mobile App Beta with Real Customers appeared first on Atomic Spin. ## Quiz: Python 3.15 Preview: Lazy Imports DevFeed: [Quiz: Python 3.15 Preview: Lazy Imports]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-09T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Python](), [.NET 11]() Tags: [module](), [python](), [time]() ### AI overview An interactive 12-question quiz tests understanding of Python 3.15 Preview lazy imports, including the lazy keyword, __lazy_modules__, deferred module loading, startup-time savings, restrictions, older-Python alternatives, and imports that must remain eager. ### Source excerpt Test your understanding of Python 3.15 lazy imports, from the lazy keyword and __lazy_modules__ to the imports that have to stay eager. ## Quiz: Python Timer Functions DevFeed: [Quiz: Python Timer Functions]() Original publisher: [Read original article]() Author: Real Python Published: 2026-09-08T12:00:00Z Content type: article Language: en Sources: [Real Python]() Topics: [Python](), [Code]() Tags: [code](), [python](), [time]() ### AI overview An interactive eight-question quiz tests understanding of Python timer functions, including choosing the right timer function and measuring a block of code with a context manager. ### Source excerpt Check what you know about Python timer functions, from picking the right time function to timing a block of code with a context manager. ## Rebuilding a 1995 GPS Time Server so I don't get Telstra'd DevFeed: [Rebuilding a 1995 GPS Time Server so I don't get Telstra'd]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-09-04T14:00:00Z Content type: article Language: en Sources: [Jeff Geerling]() Topics: [Hardware](), [Server](), [configuration](), [Network](), [data]() Tags: [australia](), [data](), [daytime](), [gps](), [hardware](), [network](), [ntp](), [raspberry-pi](), [raspberry-pi-5](), [server](), [symmetricom](), [time](), [truetime](), [usb]() ### AI overview The article documents the restoration of a 1995 TrueTime GPS time server using a Raspberry Pi 5 and GNSS HAT. It explains the hardware integration and configuration of the Pi as a stratum 1 NTP server, including Chrony, LCD and LED status displays, and timing protocols. ### Source excerpt In June I purchased this TrueTime XL-AK time server, so I could learn more of the history of GPS-based time. I received it on June 22, and just 16 days later a similar GPS time server took down Australia's cell service for 12 hours! I made a short video about it but put off digging into the TrueTime... until now. Over the past couple weeks, I've 'restomodded' this device with a Raspberry Pi, to build a stratum 1 NTP Time server, which I'd like to eventually add to the NTP Pool. I found a way to drop in a Pi 5 and GNSS HAT, display the time and GPS status on the built-in 16x2 LCD, show the status on the bicolor LED, and make this box useful again. ## Community consultation on increasing diversity in APNIC community leadership: Stage 1 report released DevFeed: [Community consultation on increasing diversity in APNIC community leadership: Stage 1 report released]() Original publisher: [Read original article]() Author: Kenny Huang Published: 2026-09-04T05:34:12Z Content type: news Language: en Sources: [APNIC Blog]() Topics: [Internet](), [Network]() Tags: [apnic-62](), [apnic-ec](), [community](), [diversity](), [emerging-leaders](), [governance](), [guest-post](), [leadership](), [remote](), [survey](), [time]() ### AI overview The APNIC Executive Council has released the Stage 1 report from a consultation on increasing diversity in APNIC community leadership. The consultation gathered input from 49 participants across 21 economies and identified themes including leadership pathways, election barriers, and the time and support required for participation. A second consultation is planned at APNIC 62, followed by a final report. ### Source excerpt The APNIC Executive Council has released the Stage 1 report on APNIC's community consultation on increasing diversity in APNIC community leadership. The discussion will continue at APNIC 62 in Mumbai, with remote participation available. ## AWS Launches Graviton5-Based EC2 R9g and R9gd Memory-Optimized Instances DevFeed: [AWS Launches Graviton5-Based EC2 R9g and R9gd Memory-Optimized Instances]() Original publisher: [Read original article]() Author: Harold Fritts Published: 2026-09-01T18:42:59Z Content type: news Language: en Sources: [StorageReview.com]() Topics: [Amazon Web Services](), [Amazon EC2](), [Arm](), [cpu](), [Hardware](), [Nitro System](), [virtualization](), [Nitro Isolation Engine](), [Database](), [Caching](), [Kubernetes](), [Formal verification]() Tags: [amazon-ec2](), [amazon-eks](), [arm](), [aws](), [c-plus-plus](), [caching](), [cloud](), [database](), [docker](), [enterprise](), [formal-verification](), [go](), [hardware](), [java](), [microservices](), [nitro-isolation-engine](), [nitro-system](), [node-js](), [nvme](), [processors](), [python](), [time]() ### AI overview AWS has generally released the Amazon EC2 R9g and R9gd instances, powered by AWS Graviton5 processors. These Arm-based, memory-optimized instances offer higher per-vCPU performance, faster memory, larger cache capacity, and increased networking and Amazon EBS bandwidth for database, caching, analytics, container, and microservices workloads. R9gd adds local NVMe SSD storage for low-latency local capacity. Both families use the AWS Nitro System and Nitro Isolation Engine, with AWS citing formal verification for the isolation properties. ### Source excerpt AWS has made its Amazon EC2 R9g and R9gd instances generally available, introducing memory-optimized systems powered by AWS Graviton5 processors. The new Arm-based instances target database, caching, analytics, container, and microservices workloads that require high memory bandwidth and improved per-vCPU performance. Compared with Graviton4-based R8g instances, AWS states that R9g can deliver up to 25% The post AWS Launches Graviton5-Based EC2 R9g and R9gd Memory-Optimized Instances appeared first on StorageReview.com. ## Sega-owned Rovio is shutting down its Copenhagen studio DevFeed: [Sega-owned Rovio is shutting down its Copenhagen studio]() Original publisher: [Read original article]() Author: Diego Argüello Published: 2026-09-01T15:37:36Z Content type: news Language: en Sources: [gamedeveloper]() Topics: [Mobile]() Tags: [acquisition](), [company](), [context](), [mobile](), [news](), [project](), [time]() ### AI overview Sega-owned Rovio is closing its Copenhagen studio after canceling the mobile game Sonic Blitz. The exact number of redundancies has not yet been confirmed. ### Source excerpt The closure follows the cancellation of Sonic Blitz and the exact number of redundancies are yet to be confirmed. ## Nitpicking in code reviews wastes time DevFeed: [Nitpicking in code reviews wastes time]() Original publisher: [Read original article]() Author: Dan Lew Published: 2026-09-01T13:00:13Z Content type: opinion Language: en Sources: [Dan Lew Blog]() Topics: [Code](), [code productivity](), [Software Engineering](), [Development]() Tags: [bugs](), [code](), [code-reviews](), [development](), [features](), [problems](), [refactor](), [software-development](), [time]() ### AI overview An opinion article argues that nitpicking minor issues in code reviews wastes time. Small problems usually have limited impact, may never cause trouble, and can often be fixed later, so review effort should prioritize major problems, bugs, and features. ### Source excerpt I once wrote about how I've stopped nit-picking in code reviews, which improved the signal-to-noise ratio and helped everyone get along better. I'm back with a third reason to ditch the practice: nit-picking wastes time. By definition, nitpicks are about minor problems: ## The invisible heartbeat of our networks DevFeed: [The invisible heartbeat of our networks]() Original publisher: [Read original article]() Author: Luca Cicchelli Published: 2026-08-31T23:03:47Z Content type: article Language: en Sources: [APNIC Blog]() Topics: [Networks](), [distributed-systems](), [Critical Infrastructure](), [Security](), [5G](), [Cybersecurity](), [cloud-infrastructure](), [AI Infrastructure]() Tags: [5g](), [ai](), [ai-infrastructure](), [critical-infrastructure](), [cybersecurity](), [data](), [distributed-systems](), [engineering](), [gnss](), [gps](), [guest-post](), [hardware](), [network](), [networking](), [networks](), [outage](), [outages](), [post](), [servers](), [systems](), [tech-matters](), [time](), [transactions]() ### AI overview The article examines how accurate time synchronization underpins modern networks and distributed systems. It uses the Telstra outage to show how misaligned time servers can disrupt communications and rail services, and discusses resilient time sources, terrestrial backups, local atomic clocks, and synchronization requirements for finance, 5G, cloud, and AI infrastructure. ### Source excerpt Guest Post: The recent Telstra outage highlighted a critical but often overlooked dependency in modern networks: Accurate time synchronization. ## Before NTP there were Time and Daytime DevFeed: [Before NTP there were Time and Daytime]() Original publisher: [Read original article]() Author: jeff@jeffgeerling.com (Jeff Geerling) Published: 2026-08-30T22:09:00Z Content type: article Language: en Sources: [Jeff Geerling]() Topics: [networking](), [Protocol (disambiguation)](), [Unix]() Tags: [apple](), [bug](), [daytime](), [history](), [network](), [ntp](), [rfc-867](), [rfc-868](), [server](), [time]() ### AI overview The article examines the pre-NTP Time and Daytime protocols, RFC 868 and RFC 867, and explains how they provided simple network-based time retrieval. It describes the protocols' low overhead and limitations, including one-second resolution, lack of network-delay measurement, and the 2036 32-bit rollover bug. ### Source excerpt In building an NTP time demo on old Macs for VCF Midwest, I came across RFC 867 and RFC 868, for the 'Daytime' and 'Time' Protocols, respectively. My first exposure to any form of network time was when I upgraded from a used PowerBook 180c to my first 'new' computer, a Power Mac G3, in 2000. With the introduction of Mac OS 8.5, Apple added a 'Network Time Server' option in the Date & Time Control Panel. ## Adventures in Daylight Saving, Norfolk Island, and Time Zone Math (in Ruby) DevFeed: [Adventures in Daylight Saving, Norfolk Island, and Time Zone Math (in Ruby)]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-08-28T00:00:00Z Content type: article Language: en Sources: [Daniel Doubrovkine]() Topics: [Ruby](), [DateTime](), [bug]() Tags: [bug](), [code](), [open-source](), [ruby](), [time]() ### AI overview This article explains how several bugs in the Ruby gem distance_of_time_in_words were caused by incorrect assumptions about daylight-saving transitions and time-zone offsets. Fixes replaced DST checks and one-hour special cases with comparisons of actual UTC offsets, handling Europe/Dublin and Norfolk Island correctly. ### Source excerpt distance_of_time_in_words is a small Ruby gem that turns two Time objects into a human-readable string like "3 days and 4 hours". Several separate bug reports against it turned out to be variations on the same theme: computing a duration between two timestamps is not the trivial subtraction it looks like, the moment time zones are involved. The first two fixes shipped in dotiw 5.6.0; four more followed shortly after in dotiw 5.6.1. Bug 1: dst? Lies When You Least Expect It #63 reported that a duration of one minute was rendered as "less than 1 second" for users in Europe/Dublin. The gem's TimeHash had a DST correction that looked reasonable: d = largest - smallest d -= 1.hour if smallest.dst? && !largest.dst? d += 1.hour if !smallest.dst? && largest.dst? The idea: if a DST transition happened between the two times, Time subtraction already accounts for the wall-clock jump, so cancel it back out before splitting the duration into calendar units. That works everywhere except Ireland. Europe/Dublin uses an inverted DST scheme: its winter time is legally defined as "standard time minus one hour" rather than the more common "standard time is winter, summer is +1". Depending on whether a Time was constructed via Time.at(seconds) or datetime.to_time, dst? could report different values for the exact same instant, even though utc_offset agreed. The correction fired when it shouldn't have, and a real one-minute gap got silently zeroed out. Reproducing it doesn't even require mocking dst? -- just running the example with the right TZ set is enough: ENV['TZ'] = 'Europe/Dublin' start = Time.at(DateTime.now) finish = DateTime.now + 1.minute # => "less than 1 second" # expected: "1 minute" distance_of_time_in_words(start, finish) The fix (PR #152) was to stop asking "is this DST?" and just compare the actual offsets: def offset_decreased?(smallest, largest) smallest.utc_offset > largest.utc_offset end def offset_increased?(smallest, largest) smallest.utc_offset < largest.utc_offset ## CircleCI Smarter Testing: Stop running tests that don't matter DevFeed: [CircleCI Smarter Testing: Stop running tests that don't matter]() Original publisher: [Read original article]() Author: Nathan Fish Published: 2026-08-26T19:00:00Z Content type: article Language: en Sources: [The CircleCI Blog Feed | CircleCI]() Topics: [Testing](), [CI/CD]() Tags: [accelerate](), [auto-rerun-failed-tests](), [ci-cd](), [circleci](), [circleci-news](), [developer-productivity](), [dynamic-test-splitting](), [engineering-productivity](), [flaky](), [intelligent-test-selection](), [parallel](), [pipeline](), [quality](), [reduce](), [smarter-testing](), [test-impact-analysis](), [testing](), [tests](), [time]() ### AI overview CircleCI describes Smarter Testing, a set of features designed to reduce CI/CD test execution time by skipping tests unaffected by changes, balancing parallel nodes, and retrying flaky tests. The article says early users have seen test runs up to four times faster. ### Source excerpt Testing eats up to half your pipeline time. See how CircleCI Smarter Testing skips unaffected tests, rebalances parallel nodes, and retries flaky tests. ## Postgres + ClickHouse Architectural Patterns DevFeed: [Postgres + ClickHouse Architectural Patterns]() Original publisher: [Read original article]() Author: Agus Syafaat Published: 2026-08-26T08:08:43Z Content type: article Language: en Sources: [SeveralNines]() Topics: [clickhouse](), [PostgreSQL](), [Databases](), [Architecture & Design](), [data-platforms](), [real-time](), [Transactions](), [Low Latency](), [dashboards]() Tags: [analytics](), [architecture](), [clickhouse](), [clustercontrol](), [database-general](), [hybrid-operations](), [latency](), [olap](), [postgres](), [postgresql](), [real-time](), [time](), [transactions]() ### AI overview This article explains architectural patterns that combine PostgreSQL and ClickHouse. PostgreSQL serves as the authoritative transactional system for OLTP workloads, while ClickHouse handles large-scale analytical queries and real-time analytics. Continuous Change Data Capture synchronization connects the systems and separates transactional and analytical workloads. ### Source excerpt The role of databases has shifted significantly as modern applications must deliver real-time analytics, dashboards, and machine learning alongside low-latency transaction processing. Handling these diverse demands with a single relational database has become unsustainable under growing data volumes. Consequently, organizations are adopting specialized database architectures where multiple engines work together based on their strengths, allowing [...] The post Postgres + ClickHouse Architectural Patterns appeared first on Severalnines. ## Speed Insights now has a free tier DevFeed: [Speed Insights now has a free tier]() Original publisher: [Read original article]() Author: Chris Widmaier Published: 2026-08-25T16:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [Vercel](), [dashboards](), [Command-line interface](), [data]() Tags: [cli](), [free](), [performance](), [product](), [speed](), [time](), [upgrade](), [vercel]() ### AI overview Vercel Speed Insights now offers a free tier on every plan for any number of projects, including 10,000 events per team every 30 days. The paid tier is now called Speed Insights Plus and adds deeper diagnostics, historical data, Drains, and Vercel CLI access. Existing paid customers keep the same capabilities and price. ### Source excerpt Speed Insights now has a free tier that gives you a high-level performance overview from your real users. The new free tier: Is available on every plan, for any number of projects Includes 10,000 events per team, every 30 days Install Speed Insights: Previously, free Speed Insights was limited to a single project on Hobby, and upgrading to Pro meant losing access unless you paid for the add-on. Now your free tier carries over, and you only pay if you upgrade. The paid product, now called Speed Insights Plus, includes deeper diagnostics and historical data. If you were already paying for Speed Insights, only the name has changed, and your capabilities and price are the same. Install @vercel/speed-insights in your project to start reporting real-user data, or open the Speed Insights dashboard to view your results. Learn more in the Speed Insights documentation. Speed Insights reports how real visitors experience your pages, using live traffic rather than lab conditions. Speed Insights Plus adds slow-route diagnosis and detailed breakdowns for finding where pages get slow, and historical data to track performance over time. It also provides access to Drains and the Vercel CLI for working with performance data outside the dashboard. Read more ## IPFS is moving beyond the sponsored gateways DevFeed: [IPFS is moving beyond the sponsored gateways]() Original publisher: [Read original article]() Published: 2026-08-25T00:00:00Z Content type: release Language: en Sources: [IPFS]() Topics: [IPFS](), [gateway](), [P2P](), [browser]() Tags: [distributed](), [gateway](), [ipfs](), [object-object](), [open-web](), [self-hosted](), [time]() ### AI overview IPFS is changing how the ipfs.io and dweb.link gateways operate, shifting content retrieval from centralized servers toward service workers that connect directly to peers and verify content in the browser. The article also describes self-hosted gateways, browser-based IPFS nodes, and paid pinning and retrieval providers as alternatives. ### Source excerpt How IPFS is shifting from centralized public gateways to distributed infrastructure and client-side retrieval. [Next page]()