Editorial policy

How Internet of Things News is produced: AI-drafted content from primary sources, automated checks, one responsible editor, labelled paid placements and a public corrections log.

This page describes how the site is made, in enough detail that you can decide how much to trust it. It is written to match what actually happens, and it is updated when the process changes.

Who is responsible

Internet of Things News is published by ARKé S.r.l., Rome, Italy. The responsible editor is Vito Faga, the firm's owner. He decides what is published, answers for it and handles corrections. There is no editorial staff beyond him.

How content is produced

  • Drafting. Guides, glossary entries, digests and company profiles are drafted with AI tools (large language models with web access) following a written specification: original text, no invented numbers, primary sources, no marketing tone. The specification is part of the site's source code.
  • Sources. Guides work from specifications, RFCs, standards bodies' publications, regulators' texts and vendors' official documentation. Quantitative claims (versions, dates, rates, limits, deadlines) link to the document they come from. Digest items link to the original announcement, release or article, and the commentary is kept in a separate paragraph marked "Why it matters". Company profiles are based on the company's own website; where a profile lists products, pricing and limits, it shows the date they were checked against the official pages.
  • Automated checks. Every build runs the content through a typed schema (a malformed entry fails the build), verifies every internal link against the built pages, checks the directory for duplicate domains and dead websites, and screens the text for formatting and consistency problems. These checks catch structure, not truth.
  • Human review. The responsible editor spot-checks pages before and after publication and reviews everything a reader reports. Review is not exhaustive, and we do not claim that every sentence has been verified by a person.
  • Dates. Every article shows its publication date and, when it has been changed, an "Updated" date. Company profiles show the date their details were last verified, or the date they were added when no verification has happened yet.

Independence and paid placements

  • Editorial coverage, in the digest, the guides and the glossary, is not for sale. Advertisers and sponsors do not see articles before publication.
  • Featured company listings are paid. They are labelled "Featured" everywhere they appear, their outbound links carry rel="sponsored", and paying does not change what the profile says: the text stays in our words and corrections of fact are accepted from any company, paid or not. Links from free listings carry rel="nofollow". We do not sell search-engine benefits.
  • Sponsored mentions in the newsletter are labelled as sponsored. Affiliate links, where used, are disclosed on the page.
  • Company profiles describe real companies with a working official website. We write them ourselves and refuse marketing copy. Companies can claim a profile to correct it; a claim is checked against the work email domain.

Reporting an error

Write to hello@internetofthingsnews.com with the page URL, the passage, what is wrong and, if you have one, a source. We reply to every correction request. When the error is confirmed, the page is fixed, its "Updated" date changes, and the correction is added to the log below with its date. A correction that changes the meaning of a passage is also noted in the text.

Corrections log

  • October 17, 2026, /learn/mqtt-explained/: The Security section said MQTT has no authentication of its own. Corrected: MQTT carries a username and password in the CONNECT packet, and MQTT 5 adds enhanced authentication through the AUTH packet; only encryption is delegated to TLS.
  • October 17, 2026, /companies/pricing/: Featured listings were advertised with a "dofollow" link and "two months free". Removed: outbound links on paid placements are marked rel="sponsored", free listings rel="nofollow", and the yearly saving is now computed from the published prices.
  • October 17, 2026, /news/2026-09-25-issue-1/: Issue 1 was general commentary without dated sources. Rewritten around dated announcements of the week of 21 September 2026, each linked to its original source, with the commentary separated from the news in Why it matters paragraphs.
  • October 17, 2026, /news/2026-10-02-issue-2/: Issue 2 was general commentary without dated sources. Rewritten around dated announcements of the week of 28 September 2026, each linked to its original source, with the commentary separated from the news in Why it matters paragraphs.
  • October 17, 2026, /news/2026-10-09-issue-3/: Issue 3 was general commentary without dated sources. Rewritten around dated announcements of the week of 5 October 2026, each linked to its original source, with the commentary separated from the news in Why it matters paragraphs.
  • October 17, 2026, /jobs/: Four illustrative job entries were counted as open positions. They are now labelled "Example listing", excluded from the counts and from search indexing.
  • October 17, 2026, /about/: The page said every guide was "reviewed for technical accuracy" by editors. Replaced with a description of the actual process: AI-drafted content from primary sources, automated checks, spot-check review, one responsible editor.
  • October 17, 2026, /learn/iot-history-and-key-milestones/: The Carnegie Mellon Coke machine was dated to the early 1980s and attributed to students. Corrected from CMU's own account: members of the computer science department wired it to the departmental PDP-10 in the mid-1970s. The Trojan Room coffee pot is now dated 1991 and the Mirai botnet's size (about 600,000 devices) is given from the USENIX study.
  • October 17, 2026, /learn/iot-security-regulation/: Cyber Resilience Act dates corrected to those in Regulation (EU) 2024/2847: vulnerability and incident reporting obligations have applied since 11 September 2026 and the regulation applies in full from 11 December 2027. PSTI penalties, previously described as scaled to company revenue, are stated as up to 10 million pounds or 4% of worldwide revenue. The Cyber Trust Mark section now records the withdrawal of UL Solutions as Lead Administrator and the FCC's appointment of the ioXt Alliance.
  • October 17, 2026, /learn/iot-in-healthcare/: The page said the EU Cyber Resilience Act interacts with the Medical Device Regulation for connected products. Corrected: devices covered by the MDR are excluded from the CRA's scope and are held to the MDR's own cybersecurity requirements. The FDA requirements are now tied to section 524B of the FD&C Act, in effect since March 2023.
  • October 17, 2026, /learn/thread-explained/: Standard credential sharing between border routers was attributed to Thread 1.3. Corrected: Thread 1.3 (2022) standardized the border router and introduced its certification; the credential-sharing procedure arrived with Thread 1.4 in September 2024.
  • October 17, 2026, /learn/zigbee-explained/: The installed base was given as hundreds of millions of devices and Zigbee 3.0 as released without a date. Corrected: the Connectivity Standards Alliance counts more than a billion Zigbee devices, and Zigbee 3.0 was ratified in December 2015. Zigbee PRO 2023 and Zigbee 4.0 added.
  • October 17, 2026, /learn/lorawan-explained/: The maximum payload was given as roughly fifty bytes at the slowest data rates regardless of region. Corrected from the LoRa Alliance regional parameters: the limit depends on region and data rate, as little as 11 bytes at the slowest North American rate and about 50 bytes in Europe. The unsourced claim that LoRaWAN is the most widely deployed LPWAN technology was removed.
  • October 17, 2026, /learn/nb-iot-and-lte-m-explained/: eDRX cycles were described as running from about a second to minutes. Corrected from 3GPP material: from seconds up to about 44 minutes on LTE-M and about 3 hours on NB-IoT. The 164 dB maximum coupling loss target is now stated with its source.
  • October 17, 2026, /learn/bluetooth-le-for-iot/: Direction-finding accuracy was given as within a meter or so. Corrected to the Bluetooth SIG's own description (centimeter-level), with the source linked. Bluetooth 6.0 Channel Sounding and core specification 6.2 added.
  • October 17, 2026, /ai/tinyml-explained/: microTVM was listed as a current deployment option and STM32Cube.AI as ST's current tool. Corrected: microTVM was phased out of Apache TVM in release 0.19, and ST Edge AI Core is the successor to STM32Cube.AI. An unsourced milliwatt-range power claim was made qualitative.

Changes to this policy

This page was first published on October 17, 2026. Changes to the process are reflected here when they happen.