Urgent.News

What's breaking now, across thousands of outlets.

Tech

Show HN launches now run on repos created days before posting. It used to be months.

Last month I published a dataset of 70,894 Show HN posts. The obvious follow-up was star trajectories: did hot launches keep growing? That study is now impossible for everyone. In July 2026 GitHub restricted the stargazers listing — and with it the star timestamps ( star+json ) and the GraphQL connection — to admins and collaborators, citing spam abuse (changelog 2026-06-30). We measured it live:…

A recent analysis of GitHub's Show HN posts reveals a significant shift in the timeline of project launches. Historically, the top-performing posts ran on repositories that were months old. However, this pattern has changed dramatically. In 2026, the top decile of Show HN launches occurred on repositories that were a median of just 17 days old, a stark contrast to the 70-day median observed in 2024.

This trend is even more pronounced, with 25% of top-decile launches happening on repositories that were 14 days old or less in 2026, up from 37% and 47% in the previous years.

The study, conducted on 430 repositories drawn from 19,983 unique GitHub-linked posts, found that the median time between a repository's creation and a launch has decreased from 322 days in 2024 to just 7 days in 2026. While it's important to note that these are percentile figures and not absolute counts, they highlight a clear trend towards quicker project lifecycles.

Interestingly, even posts with fewer than 200 points, which often indicate less serious projects, show a similar trend, with a median of just 7 days in 2026.

The data also suggests that the composition of top-decile posts has shifted, with a growing emphasis on AI applications rather than traditional development tools. However, it's crucial to note that created_at does not represent work started. Repositories can be transferred, renamed, or have their visibility changed without altering the creation date, which only changes if a repository is deleted and recreated.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

TrailRelay: Offline-First Trail Hazard Reporting with Gemma and Temporal

This is a submission for the Hacktoberfest Open-Source AI Challenge Week 1: Touch Grass TrailRelay: Offline-First Trail Hazard Reporting with Local AI What I Built Imagine hiking in a remote area and…

  • TrailRelay enables offline reporting of trail hazards like fallen trees and flooding.
  • Gemma 3 1B model classifies hazard descriptions locally without hosted AI API.
  • Temporal orchestrates report-processing workflow with GitHub Issues for tracking.

Score Any Public Repository Reproducibly with harness-maturity-analysis

If you are evaluating how well a repository supports AI-assisted development, it is easy to mix two different jobs: measuring one repository quickly and adding a research observation to a maintained…

  • harness-maturity-analysis evaluates public repositories reproducibly
  • Ad hoc command inspects local paths or public repositories
  • Output includes maturity level, point total, dimension percentages

New Platform Needed to Address Shortcomings in Hardware Coding Practice Tools

Introduction The landscape of hardware coding practice tools is, frankly, a wasteland of missed opportunities. Existing platforms, while functional, are riddled with shortcomings that hinder both…

  • Hardware coding platforms suffer from UI inefficiencies and feature gaps.
  • Inadequate UI leads to unresponsive interfaces and user frustration.
  • Feature gaps include lack of modular problem integration and realistic simulations.

More from Sunday 11 October →