About Our Authors

Every article on AIPress carries a byline. This page explains what those bylines mean, who stands behind them, and the standards each piece is held to.

Our Byline

Most articles are published under the masthead byline AIPress Editorial rather than an individual name. That is a deliberate choice, and an honest one: it signals that the publication as a whole is accountable for the piece. A byline here is a statement of responsibility, not a claim about a particular journalist's personal reporting.

Where an article is the work of a named contributor, that person's name appears in the byline instead.

Jacob Bloom — Editor and Lead Writer

Jacob Bloom is the editor and lead writer behind AIPress, a daily AI news and analysis publication covering model releases, benchmarks, AI infrastructure, safety research, and the policy debates shaping the frontier.

He is a computer science graduate (born 1994) with long-running, hands-on experience in Linux, networking, and cyber-security — a systems-first perspective that he brings to every story. These days, as AI capabilities accelerate week by week, Jacob is fully immersed in tracking, testing, and writing about the latest models, tools, and infrastructure.

His hobbies and interests still revolve around the same core that brought him to the field: computers, networking, programming, IoT, research and development, reading, and gaming. The through-line has always been curiosity about how things work and a taste for digging past the surface.

At AIPress, Jacob covers the full frontier landscape: what the labs ship and why, what the benchmark numbers actually say, company strategy, real safety and misuse incidents, the physical infrastructure behind AI, and the policy and regulation that shape what builders and users can do. His writing favors primary sources — model cards, research papers, official announcements, filings, and transcripts — with named citations where they exist and honest caveats where they do not. Analysis is labeled as analysis, never passed off as fact.

AIPress is published by DevsIsle, a software company that builds and operates web products. DevsIsle is responsible for the publication as a whole, including corrections; Jacob is accountable for the editorial content.

Standards Every Article Is Held To

• Primary sources first. Model cards, research papers, official announcements, filings and transcripts, rather than someone else's summary of them.
• Named citations where they exist. If a claim comes from somewhere, we say where. If it does not, we say that too.
• Honest caveats. Benchmark numbers get the conditions they were measured under. Early results are labelled as early. Where the evidence is thin, the article says so rather than rounding up.
• No recycled press releases. An announcement is a starting point for a piece, never the piece itself.
• Analysis is labelled as analysis. Where we draw a conclusion that goes beyond the reporting, it is presented as our reading of the facts, not as a fact.

Corrections

When we get something wrong we correct it and say so. Corrections are noted at the top of the affected article rather than made silently, so a reader who saw the original can see what changed.

If you spot an error — a wrong figure, a misattributed quote, a missing piece of context — email contact@aipress.blog with the subject line Correction: [article title]. We read every message and act on the ones that are right.

Contacting the Desk

Tips, corrections, questions about a specific article, and requests to be quoted or to remain anonymous all go to contact@aipress.blog. The Contact page has more detail on what to include. Our approach to your data is set out in the Privacy Policy, and more about the publication is on the About page.