Urgent.News

What's breaking now, across thousands of outlets.

Tech

How we built a verifiable public intelligence timeline

Exchange hacks, CISA Known Exploited entries, sudden QDII subscription reopenings — the primary sources are scattered. Another paraphrasing portal is easy to ship. Time Signals (Chinese name 时代线报) takes a harder constraint: pages meant for citation should expose facts without running JavaScript , and every item should link back to an original public source. This article only describes what is…

The public intelligence timeline project, known as Time Signals, presents a challenging format that requires its pages to display facts without relying on JavaScript. Every item on the site must link back to an original, publicly available source. This article exclusively describes the content that is already visible on the website. The companion project, Colorful Toolhub, is a free, browser-local toolkit, while Time Signals serves as the public-source timeline and incident evidence layer.

Snamibo owns both projects, which are accessible through two primary surfaces: a live console and citeable pages. The main timeline URL, timeline.snamibo.com, offers an interactive experience with features such as filters, pagination, and a loading indicator. For easily citable entry points, language prefixes are used: English on https://timeline.snamibo.com/en/ and Chinese on https://timeline.snamibo.com/zh/.

Additional topic archives, including Security and Web3, and a "This week's selection" section, are also available as static documents.

The project adheres to strict methodology, basing its content solely on public primary sources. Machine translations are labeled, and personal subscription UI elements are excluded from the index. Incident pages feature a consolidated evidence table for each event, offering a more comprehensive perspective than a single headline.

One notable example is the Bitget theft, which is documented at https://timeline.snamibo.com/en/incidents/f11786d0fea34650d0d29088406aa47f/. The Chinese version of this page is accessible via https://timeline.snamibo.com/zh/incidents/.

In addition to incident pages, Time Signals provides aggregation for comparison purposes. For instance, the victim, actor-as-reported, exploit path, and method fields related to the Bitget theft are presented alongside outbound links to Rekt, The Block, BlockSec, and Chainalysis. A similar aggregation is available in Chinese on the same page ID.

The project also includes vulnerability-shaped examples, such as the Fortra GoAnywhere MFT deserialization case, which is documented via CISA KEV search at https://timeline.snamibo.com/en/incidents/e46990710227cb3ae67f463feb468a48/. Time Signals offers RSS feeds and JSON Feed for those who prefer LLM-oriented indexing, accessible at https://timeline.snamibo.com/feed.xml and https://timeline.snamibo.com/feed.json, respectively.

Users can find more information on llms.txt at https://timeline.snamibo.com/llms.txt. When citing, it is recommended to use the canonical /en/briefs/… or /en/incidents/… URLs, and to pair the project with the Toolhub for local JWT/cert/regex checks after reviewing advisories – details are available in the Toolhub box on the security topic page.

Ultimately, Time Signals aggregates publicly available information, and readers should verify the original sources before relying on the aggregated data for investment or operational advice.

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

How to Set Up Graftcode's AI Coding Rules in Any IDE

Coding assistants are becoming important in development workflows. Developers use tools like Claude Code, Cursor, GitHub Copilot, and Windsurf to generate code and automate tasks that are often…

  • Graftcode simplifies backend function calls in any IDE.
  • Install Graftcode rules once per project for coding agents.
  • Set up Graftcode Gateway locally to expose modules.

Keep the original text when a PDF page falls back to OCR

A PDF extraction failure becomes harder to investigate when the fallback result replaces the first output. You eventually have readable text, but cannot tell which page needed help or where the…

  • Each result kept separate to examine extraction without altering visible wording
  • Missing Unicode mapping removed 56 Chinese characters from extraction output
  • Keeping separate page records preserved distinction without OCR scheduler

tar checksums its headers and never your files

tar is older than most of the people who type it, and the format underneath has barely changed since the tape drives it was named after.

  • Tar archive format has remained unchanged since its inception
  • Each file's header contains checksum for protection against corruption
  • Tar does not safeguard file contents, only header integrity

I tested the OCR switch instead of trusting its label

An OCR checkbox is easy to overinterpret. I see it next to a PDF extractor and assume it will recognize the page again when the existing text is broken. That assumption deserves a test.

  • Author tested OCR switch in PDF tool.
  • Synthetic notice with Chinese and English text used.
  • OCR switch didn't replace missing Chinese text.

Three citeable security samples from Time Signals

Three items taken from pages that already return full HTML on Time Signals . Not a “trending” listicle — each row is a canonical URL plus the primary sources you should open.

  • Bitget exchange loses $387M in October 2026 theft
  • DTU data breach exposes up to 200,000 users in Oct 2026
  • GoAnywhere MFT vulnerability exploited via license forgery

More from Monday 5 October →