LinkedIn API version expiry silently breaks integrations with no code changes

·1 views

A developer in Assis, São Paulo, discovered that her LinkedIn content-publishing script stopped working despite no changes to the codebase. The culprit was LinkedIn's REST API requirement for a rolling date-based version header in YYYY-MM format, which expires after a set support window. Once the pinned version 20250601 fell outside that window, the API returned a 426 error rejecting all calls, even with a valid token and correct payload. The error message itself identified the exact problem, allowing a quick fix by simply updating the version header value. The incident highlights a broader lesson: integrations relying on expiring external dependencies — API versions, certificates, or similar — can break without any change to your own code.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

ALICE: A Modular Local AI Architecture Built Around the Qwen Language Model

ALICE is a local artificial intelligence system documented in a reference architecture dated August 28, 2026, designed around a combination of components including a language model, router, memory, tools, and learning mechanisms. The system uses Qwen2.5-3B-Instruct as its language model, but ALICE's identity is defined by the full architecture rather than the model alone. A central router orchestrates all requests by consulting a live knowledge map, querying a SQLite memory database, and only invoking Qwen for complex tasks that cannot be handled by existing procedures. ALICE follows a core operational principle of knowing, doing, learning only when necessary, retaining, and reusing — avoiding redundant problem-solving when a verified procedure already exists. The architecture also includes reinforcement learning capabilities, an OCR tool, a web control dashboard, and reusable operational circuits stored in memory with statuses such as VERIFIED.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Independent Tech Newsletter Smarterarticles Reaches 100,000 Readers in 456 Days

The independent technology publication Smarterarticles.co.uk has reached a milestone of 100,000 readers after 456 days of operation. The outlet operates without a traditional newsroom or formal growth strategies, relying solely on consistent long-form writing. The publication focuses on the real-world impact of technology and broader questions of human responsibility in the digital age. The milestone was acknowledged with gratitude to readers who engaged with, shared, or debated the content. The team has signaled its intent to continue growing, describing the achievement as the start of the next phase.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

A 'Fix' Commit That Introduced the Very Flaw It Claimed to Resolve

On August 25, 2026, a commit pushed to a self-correcting integration repository closed four legitimate automated review findings while simultaneously introducing a new vulnerability on a single line of code. The added line allowed a receipt to supply its own deciding fields to the validator, meaning a receipt with failing checks but an empty deciding_fields value would recompute over nothing and pass validation — the exact flaw the commit claimed to fix. The misleading commit message 'stop trusting the receipt' gave reviewers a false sense of confirmation, making the diff less likely to be scrutinized closely. A commenter named pm25coder had independently described this failure class a day earlier — where authority migrates one level down and a subject ends up supplying the terms by which it is judged — in a different project, not this repository. A separate incident on August 29 involved a submission document that correctly stated a comment count but defined an incomplete universe, with the denominator excluding the very pull request that merged the sentence.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How JavaScript Converts Text to Binary and Back Using UTF-8 Encoding

Every character a computer stores is ultimately represented as a sequence of ones and zeros, with each character mapped to a numeric code point that becomes a byte of 8 bits. In JavaScript, the TextEncoder API reliably converts any string into its raw UTF-8 binary representation, handling standard ASCII as well as accented characters and emoji. Reversing the process involves stripping spaces, splitting the binary string into 8-bit chunks, parsing each chunk as a base-2 integer, and decoding the resulting bytes with TextDecoder. A key implementation detail is padding each byte to exactly 8 bits, without which the binary string cannot be cleanly split back into characters. Older approaches using charCodeAt can silently corrupt non-ASCII text, making the TextEncoder and TextDecoder pair the recommended modern solution.

0 comments Read more at DEV Community