# issue Published articles for issue. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## ThinkPad X201 support removed from Libreboot DevFeed: [ThinkPad X201 support removed from Libreboot]() Original publisher: [Read original article]() Author: Leah Rowe Published: 2026-09-17T04:32:50.666044Z Content type: news Language: en Sources: [News about Libreboot releases and development]() Topics: [libreboot](), [coreboot](), [rsync]() Tags: [article](), [bios](), [canoeboot](), [coreboot](), [free-software](), [issue](), [libre](), [libreboot](), [news](), [opensource](), [rsync](), [safety](), [thinkpad](), [uefi]() ### AI overview Libreboot removed support for the ThinkPad X201 and other older Arrandale machines after discovering that fan controls fail when using a neutered Intel ME image. Coreboot remains possible with the full Intel ME image, but Libreboot will not support these platforms unless further testing resolves the issue. ### Source excerpt Article: ThinkPad X201 support removed from Libreboot Web link: https://libreboot.org/news/x201.html ## datasette 0.65.5 DevFeed: [datasette 0.65.5]() Original publisher: [Read original article]() Author: Simon Willison Published: 2026-09-16T23:51:08Z Content type: release Language: en Sources: [Simon Willison's Weblog]() Topics: [Security](), [Authorization]() Tags: [bypass](), [datasette](), [datasette-1-544](), [issue](), [permissions](), [release](), [security](), [security-636]() ### AI overview Datasette 0.65.5 is a security release fixing an issue in which a trailing newline in a requested table name could bypass table permissions and expose private rows. ### Source excerpt Release: datasette 0.65.5 Security fix for an issue where a trailing newline in a requested table name could bypass table permissions and expose private rows, reported by dpfkdlemtp in GHSA-h547-rmjf-5m2m. Tags: security, datasette ## jetc.dev Newsletter Issue #331 DevFeed: [jetc.dev Newsletter Issue #331]() Original publisher: [Read original article]() Author: CommonsWare Published: 2026-09-15T14:00:00Z Content type: article Language: en Sources: [jetc.dev | Issues]() Topics: [Jetpack Compose](), [compose-for-desktop](), [servo](), [WebView]() Tags: [bug-fixes](), [chromium](), [compose-for-desktop](), [issue](), [jetpack](), [jetpack-compose](), [release-notes](), [webview]() ### AI overview This newsletter reviews recent Jetpack Compose release changes and highlights related developer content. It covers Compose BOM updates, Material3 and other Compose library versions, a keyboard focus bug and workaround, keyed composition, dialog background blurring, and Compose for Desktop libraries including a CEF-based option and window chrome controls. ### Source excerpt SideEffect keys! CEF-based WebView and window chrome controls for desktop apps! And... why does the keyboard flicker?!? ## Linux Patch Coming To Fix Under-Reported AMD Zen 5 TLB Sizes DevFeed: [Linux Patch Coming To Fix Under-Reported AMD Zen 5 TLB Sizes]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-15T10:05:51Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux](), [cpu](), [x86](), [Kernel]() Tags: [amd](), [cpu](), [desktop-linux](), [issue](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-kernel](), [linux-performance](), [linux-server-benchmarks](), [open-source-graphics](), [phoronix](), [phoronix-test-suite](), [processors](), [reporting](), [ubuntu-benchmarks](), [ubuntu-hardware](), [x86]() ### AI overview A Linux kernel patch corrects under-reported Translation Lookaside Buffer sizes for AMD Zen 5 EPYC and Ryzen processors. The change also supports Zen 6 and future AMD CPUs using the same reporting bit. ### Source excerpt A minor reporting issue on Linux that has gone unaddressed until now is for properly conveying the Translation Lookaside Buffer (TLB) sizes on AMD Zen 5 processors... ## Meta AI builds detailed profiles of children from years of family posts DevFeed: [Meta AI builds detailed profiles of children from years of family posts]() Original publisher: [Read original article]() Author: Danny Bradbury Published: 2026-09-15T09:44:10Z Content type: news Language: en Sources: [Malwarebytes]() Topics: [Artificial Intelligence](), [Meta](), [Instagram]() Tags: [ai](), [automated](), [facebook](), [family-and-parenting](), [information](), [instagram](), [issue](), [location](), [meta](), [photos](), [privacy](), [profile](), [social-media](), [statement]() ### AI overview A mother says Meta AI assembled detailed profiles of her young daughters by connecting names, birth details, photos, videos, and location information from family posts across Facebook and Instagram. Meta acknowledged that the feature should not have prompted questions about personal topics and said it fixed the issue. ### Source excerpt A mother says Meta AI pieced together names, birth details, photos, and location information about her young daughters from years of family posts. ## Cellular Network Infrastructure - Removal of binary package feeds for Debian 11 (bullseye) DevFeed: [Cellular Network Infrastructure - Removal of binary package feeds for Debian 11 (bullseye)]() Original publisher: [Read original article]() Author: osmith Published: 2026-09-07T13:01:53Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [Debian]() Tags: [2026](), [bug](), [debian](), [end-of-life](), [issue](), [os](), [packages](), [repositories](), [tracker]() ### AI overview Osmocom plans to stop building binary packages for Debian 11 in its repositories on December 7, 2026, because Debian 11 has reached end of life. Customers needing continued access can contact sysmocom about commercial long-term support. ### Source excerpt Debian 11 has reached its End Of Life. We plan to stop building Osmocom packages for it in our binary package repositories in three months (2026-12-07). If you are still continue to require Debian 11 binary packages, please contact sales sysmocom.de to discuss commercial terms for long-term support. ## How To Get Apple To Respond In Days On AppStore Issue DevFeed: [How To Get Apple To Respond In Days On AppStore Issue]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-08-26T10:40:01Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [iOS](), [Mobile](), [Development]() Tags: [app-development](), [apple](), [developer](), [how-to](), [ios-app-development](), [ios-development](), [issue](), [mobile](), [mobile-app-development](), [software-development]() ### AI overview The article describes an App Store submission issue in which the Submit spinner stops and the process cannot continue. It presents this as a practical account of what to do when Apple does not respond for weeks. ### Source excerpt A True Story: What To Do When You're Stuck With AppStore Issue for Weeks Continue reading on Mobile App Development Publication " ## Cellular Network Infrastructure - August 2026 Osmocom CNI releases DevFeed: [Cellular Network Infrastructure - August 2026 Osmocom CNI releases]() Original publisher: [Read original article]() Author: pespin Published: 2026-08-20T15:47:26Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [releases](), [Software](), [Vulnerabilities](), [Debian](), [Ubuntu](), [gnu linux]() Tags: [2026](), [bug](), [changelog](), [cni](), [debian](), [gnu-linux](), [issue](), [network](), [releases](), [security-vulnerabilities](), [tracker](), [ubuntu](), [update](), [version]() ### AI overview The Osmocom project released version 202608 of its Cellular Network Infrastructure software, covering components including OsmoTRX, OsmoBTS, OsmoPCU, OsmoBSC, OsmoMGW, OsmoMSC, OsmoHLR, OsmoSGSN, OsmoGGSN, OsmoSTP, and OsmoSIPConnector. The release includes several months of changes, with new features, extensive bug fixes, and fixes for multiple security vulnerabilities. An osmo-mgw 1.16.1 patch release corrected a Debian dependency issue. ### Source excerpt The Osmocom project has released new version 202608 of the CNI (Cellular Network Infrastructure) software, including OsmoTRX, OsmoBTS, OsmoPCU, OsmoBSC, OsmoMGW, OsmoMSC, OsmoHLR, OsmoSGSN, OsmoGGSN, OsmoSTP, OsmoSIPConnector, and others. Those new tagged/released versions contain up to 6-8 months of work since the previous versions released through December 2025 and February 2026. Some projects already got some intermediate releases since then. This set of releases contain some new features, but mostly lots of bug fixing, including multiple fixes for security vulnerabilities. See below for more detailed information. You can find pre-compiled binary packages of our latest release for a variety of Debian and Ubuntu GNU/Linux versions at Binary Packages. UPDATE: A new osmo-mgw patch release 1.16.1 was made on top of release 1.16.0 in order to fix a debian/control typo which was creating a dependency issue. Versions of newly released projects¶ Project Version Changelog libasn1c 0.9.39 https://gitea.osmocom.org/cellular-infrastructure/libasn1c/src/tag/0.9.39/debian/changelog libsmpp34 1.14.6 https://gitea.osmocom.org/cellular-infrastructure/libsmpp34/src/tag/1.14.6/debian/changelog libosmo-asn1-tcap 0.3.0 https://gitea.osmocom.org/ss7-in-c/libosmo-asn1-tcap/src/tag/0.3.0/debian/changelog libosmocore 1.14.2 https://gitea.osmocom.org/osmocom/libosmocore/src/tag/1.14.2/debian/changelog libosmo-netif 1.8.0 https://gitea.osmocom.org/osmocom/libosmo-netif/src/tag/1.8.0/debian/changelog libosmo-abis 2.2.0 https://gitea.osmocom.org/osmocom/libosmo-abis/src/tag/2.2.0/debian/changelog libosmo-pfcp 0.7.0 https://gitea.osmocom.org/osmocom/libosmo-pfcp/src/tag/0.7.0/debian/changelog libosmo-sigtran, osmo-stp 2.3.0 https://gitea.osmocom.org/osmocom/libosmo-sigtran/src/tag/2.3.0/debian/changelog osmo-e1d 0.8.0 https://gitea.osmocom.org/retronetworking/osmo-e1d/src/tag/0.7.1/debian/changelog osmo-pcap 0.8.1 https://gitea.osmocom.org/osmocom/osmo-pcap/src/tag/0.8.1/debian/changelog osmo ## osmo-remsim - osmo-remsim 1.2.0 released DevFeed: [osmo-remsim - osmo-remsim 1.2.0 released]() Original publisher: [Read original article]() Author: lynxis Published: 2026-08-05T16:54:21Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [bug](), [Concurrency](), [log management]() Tags: [bug](), [bug-fixes](), [client](), [crash](), [csv](), [deadlock](), [debug](), [issue](), [logging](), [mutex](), [tracker]() ### AI overview osmo-remsim 1.2.0 is a release containing stability and bug fixes across bankd, remsim-client, remsim-bankd, and related ASN.1 and logging code. The fixes address invalid CSV and TPDU handling, crashes, memory leaks, race conditions, signal handling, slot mapping, byte order, and a logging mutex deadlock. ### Source excerpt 1.2.0 contains stability fixes and bug fixes. [ Alexander Couzens ] * bankd: csv: fix crash on invalid lines * bankd: csv: fail on invalid csv lines * rspro_server: don't access the msg on error cases * rspro_util: asn1 decode: fix memleak when decoding fails * asn1: ber_decoder: disable stack size check on ctx = NULL * asn1: move asn_debug into librspro * Remove unconditional assignment of asn_debug = 0 * rspro_server: use correct byte order in log message "Bankd IP/Port changed to : [ Andreas Eversberg ] * Fix: Remove slot mapping at bankd when client disconnects * Fix: Prevent race conditions when accessing slotmap in bankd * Fix: Prevent bankd from exiting upon SIGPIPE * Fix unhandled (un)mapping events [ Harald Welte ] * remsim-client: Don't attempt to pass on illegal TPDU length * remsim-bankd: Don't pass on illegal TPDUs of illegal length * bankd: Avoid osmocom logging mutex deadlock in signal handling ## libosmocore - libosmocore 1.14.1 released DevFeed: [libosmocore - libosmocore 1.14.1 released]() Original publisher: [Read original article]() Author: osmith Published: 2026-07-22T10:37:33Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [changelog](), [IO](), [cpu](), [scheduling](), [make]() Tags: [2026](), [bug](), [changelog](), [cpu](), [io](), [issue](), [make](), [scheduling](), [tracker]() ### AI overview libosmocore 1.14.1 has been released with fixes to I/O queue handling, CPU scheduling initialization and platform-dependent scheduling support, utility issues, and a missing crypto header in the build configuration. ### Source excerpt Today we've released libosmocore 1.14.1. The changelog over 1.14.0 is as follows: libosmocore (1.14.1) unstable; urgency=medium [ Vadim Yanitskiy ] * osmo_io: iofd_txqueue_dequeue(): fix double next->io_len decrement [ Timur Davydov ] * vty: fix osmo_cpu_sched_vty_init() prototype * vty: make CPU scheduling optional based on platform support [ Oliver Smith ] * utils: fix typos * utils/gsmtap-logsend: close infile before exit [ Alexander Couzens ] * gsm/Makefile.am: add missing kdf/crypto.h -- Oliver Smith Wed, 22 Jul 2026 11:30:55 +0200 ## osmo-ePDG - VoWifi Evolved Packet Data Gateway - osmo-epdg 0.1.2 released DevFeed: [osmo-ePDG - VoWifi Evolved Packet Data Gateway - osmo-epdg 0.1.2 released]() Original publisher: [Read original article]() Author: osmith Published: 2026-07-22T09:00:22Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [gateway](), [changelog](), [version]() Tags: [bug](), [changelog](), [compiler](), [gateway](), [ipv6](), [issue](), [tracker](), [version]() ### AI overview Osmocom released osmo-epdg 0.1.2, an unstable release of its VoWifi Evolved Packet Data Gateway. The changelog lists IPv4/IPv6 support improvements, Diameter and GTP-related fixes, dependency updates, documentation changes, and test updates. ### Source excerpt Today we've released osmo-epdg 0.1.2. The changelog over 0.1.0 is as follows: osmo-epdg (0.1.2) unstable; urgency=medium [ clufn-sudo ] * Add required conversions for IPv6 and IPv4v6 support [ clufn ] * Enable the use of an UE requested IP type and address to be used for gtpv2 PDN Address Allocation [ Pau Espin Pedrol ] * gsup: Fix rx of AuthInfoReq without IP addr val * rebar.config: Update rebar3_diameter_compiler from 0.8.0 to v0.8.1 * dia/diameter_3gpp_ts29_173.dia: Fix trailing whitespace * dia/diameter_3gpp_ts29_273.dia: Fix trailing whitespace * dia/diameter_3gpp_ts29_229.dia: inherit only Line-Identifier * dia/diameter_3ggp_ts32_299.dia: Inherit RFC4005 instead of RFC7155 * dia: restrict AVPs inherited from RFC4005 * Remove duplicate 3GPP-AAA-Server-Name definition and break 3-way circular dependency * cosmetic: Fix typo in code documentation * aaa_ue_fsm: Avoid immediate stop of fsm during 2nd SWx RTR * aaa_diameter_swx: Avoid answering RTR with Success if already deregistering [ Alexander Couzens ] * s2b: set correct instance values for Bearers * diameter_3gpp_ts29_273_swx: add missing include for MAR * aaa_diameter_swx_tests: explicitly set Framed-IP-Address * aaa_diameter_swx_tests: use MAR record to improve readability [ Oliver Smith ] * editorconfig: new file [ Vadim Yanitskiy ] * rebar.config: use more recent rebar3_diameter_compiler * rebar.lock: use a more recent version of gen_netlink -- Oliver Smith Tue, 21 Jul 2026 14:12:41 +0200 osmo-epdg (0.1.1) unstable; urgency=medium [ Harald Welte ] * add notice about NLnet found ation to README.md * README.md: Use NLnet suggested language for funding acknowledgement * README.md: Update user manual section; we now have one. [ Oliver Smith ] * rebar.lock: update gtplib commit -- Oliver Smith Wed, 04 Dec 2024 15:24:46 +0100 ## When the bug slips through: How we built an AI feedback loop to strengthen our safety net DevFeed: [When the bug slips through: How we built an AI feedback loop to strengthen our safety net]() Original publisher: [Read original article]() Author: Vasilescu Andreea Published: 2026-07-14T07:16:00Z Content type: article Language: en Sources: [Data Science at Microsoft]() Topics: [Artificial Intelligence](), [bug](), [incident](), [Monitoring](), [Software](), [data](), [Azure]() Tags: [ai](), [analysis](), [artificial-intelligence](), [automation](), [bug](), [data-science](), [engineering](), [errors](), [incident](), [incident-management](), [issue](), [llm](), [monitoring](), [outage](), [production](), [software](), [teams]() ### AI overview The article describes how a large-scale engineering organization built an AI feedback loop to investigate production regressions, compare them with pre-production alerts, and identify gaps in its quality platform. It explains that manual incident sampling was valuable but covered less than 10 percent of incidents, making broader forensic analysis impractical at Azure scale. ### Source excerpt Figure 1: When the bug slips through, or how we built an AI feedback loop to strengthen our safety net. A regression reached production last fall. Not dramatically, no war-room scramble, no cascading outage. It showed up as a cluster of customer-facing errors, traced back through monitoring data to a change that had passed through every pre-production check without triggering a single alert. Somewhere upstream, the safety net had a hole that nobody knew was there. This scenario is not hypothetical. It happens. And when it does, the instinctive response is the same: investigate the incident, fix the issue, and then ask the uncomfortable follow-up question, Why didn't we catch this before it reached production? Answering that question is deceptively hard. A pre-production quality platform generates a constant stream of signals, warnings, and anomalies, many of them noisy, overlapping, or ultimately irrelevant. The regression in question might be buried among production incidents, false signals, and failures the platform was never designed to catch in the first place. While manual sampling and investigation can provide meaningful insight, understanding what was genuinely missed, why it was missed, and what needs to change at platform scale requires the kind of careful forensic analysis that is slow, expert-intensive, and -- at the scale of Azure -- practically impossible to do by hand. This is the problem we set out to solve. A safety net with blind spots Modern large-scale engineering organizations invest heavily in pre-production quality platforms, systems that evaluate software changes before they reach customers. These are systems designed to catch regressions before any code change reaches customers, running controlled experiments, executing targeted tests, monitoring key signals, and alerting engineering teams when something looks wrong. But a safety net is only as good as its coverage. And knowing how good your coverage actually is requires a feedback mechanism: a ## New: Versioned CLI and SDK Docs DevFeed: [New: Versioned CLI and SDK Docs]() Original publisher: [Read original article]() Author: Cam Soper Published: 2026-07-07T00:00:00Z Content type: release Language: en Sources: [Pulumi]() Topics: [Documentation](), [SDKs](), [Command-line interface]() Tags: [announcements](), [api](), [cli](), [community](), [docs](), [features](), [github](), [issue](), [java](), [net](), [node-js](), [product](), [pulumi](), [pulumi-cli](), [python](), [release](), [sdk](), [snapshots]() ### AI overview Pulumi has added version selectors to its CLI command reference and SDK API documentation. Users can choose documentation matching the Pulumi release they are running, with immutable snapshots available from v3.150.0 onward for the CLI and Node.js, Python, .NET, and Java SDKs. ### Source excerpt Pinned to an older Pulumi CLI or SDK version and finding that the docs describe a newer release? The Pulumi CLI command reference and the SDK API docs now include a version selector, so the documentation you're reading matches the version you're actually running. How it works When you open the CLI command reference, you'll see a version dropdown near the top of the page, below the title. The SDK API docs carry the same dropdown in the upper-right corner. Choose a release, and the page loads the documentation generated for that exact version. What's available Alongside the latest release, we keep immutable snapshots of previous versions going back to v3.150.0 (early 2025). The CLI command reference and the Node.js, Python, .NET, and Java SDK API docs are all covered, so the docs you need are only a dropdown away. (The Go SDK is versioned on pkg.go.dev, so its documentation lives there rather than in the Pulumi docs.) Get started Head to the CLI command reference or the SDK API docs and try the version dropdown. Selections are sticky, so when you navigate into a version, you'll be able to click around within that same version without having to choose it again. Have feedback? Let us know in the Pulumi Community Slack or by opening an issue on GitHub. Browse the CLI command reference ## Osmocom.org Servers - server outage of host3.osmocom.org DevFeed: [Osmocom.org Servers - server outage of host3.osmocom.org]() Original publisher: [Read original article]() Author: laforge Published: 2026-07-06T18:58:49Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [servers](), [Debian](), [maintenance](), [upgrade](), [Jenkins]() Tags: [bug](), [debian](), [hosting](), [issue](), [jenkins](), [maintenance](), [outage](), [server](), [servers](), [tracker](), [update](), [upgrade]() ### AI overview Osmocom.org reports an outage affecting host3.osmocom.org during routine maintenance for a Debian upgrade. The host, which primarily serves Jenkins, downloads, and people subdomains, has fully recovered. ### Source excerpt We're currently experiencing some troubles during routine maintenance (Debian upgrade) of host3.osmocom.org, which is primarily hosting jenkins.osmocom.org, downloads.osmocom.org and people.osmocom.org. We ask for your patience while we try to resolve the situation. Update: host3 has fully recovered. ## Retronetworking - 2026-07-08: Enabling Lawful Intercept in the Siemens EWSD DevFeed: [Retronetworking - 2026-07-08: Enabling Lawful Intercept in the Siemens EWSD]() Original publisher: [Read original article]() Author: laforge Published: 2026-06-26T16:08:20Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [digital]() Tags: [2026](), [announce](), [bug](), [digital](), [issue](), [presentation](), [tracker]() ### AI overview An announcement for the next RetroNetCall, a retronetworking-oriented spin-off of OsmoDevCall. The event will feature @jolly presenting research on enabling and operating the Lawful Intercept features of the historical Siemens EWSD digital telephony exchange. It is scheduled for July 8, 2026, at 20:00 CEST. ### Source excerpt After a bit of a hiatus, we're happy to announce the next incarnation of RetroNetCall, the retronetworking oriented spin-off of OsmoDevCall This time, we have a presentation by @jolly about his successful research efforts regarding enabling and operating the LI (Lawful Intercept) features of the historical Siemens EWSD digital telephony exchange. When: Wednesday, July 8th, 2026 from 20:00 CEST Time Topic Who 20:00 Meet and Greet everyone 20:10 enabling and operating the LI (Lawful Intercept) features of the historical Siemens EWSD digital telephony exchange @jolly Where: https://osmocom.org/RetroNetCall (Big Blue Button of https://franken.de/) ## Sentry's new AI grouping model reduces duplicate issues and incorrect merges DevFeed: [Sentry's new AI grouping model reduces duplicate issues and incorrect merges]() Original publisher: [Read original article]() Author: Kush Dubey; Yuval Mandelboum Published: 2026-06-12T09:00:00Z Content type: article Language: en Sources: [Sentry Blog]() Topics: [Artificial Intelligence](), [Machine learning](), [Embeddings](), [Algorithm](), [GPU]() Tags: [ai](), [algorithm](), [connection-pool](), [embeddings](), [gpu](), [issue](), [ml](), [model](), [production](), [server](), [timeout]() ### AI overview Sentry describes an upgraded AI model for grouping errors into issues. The model prevents 20% more duplicate issues and halves incorrect merges, separating errors with distinct root causes that the previous model combined. ### Source excerpt Sentry's new AI grouping model prevents 20% more duplicate issues while cutting incorrect merges in half. Here's how we trained and deployed it. ## Mac Native Builds, Live Protocols, And Open Issues Under 350 DevFeed: [Mac Native Builds, Live Protocols, And Open Issues Under 350]() Original publisher: [Read original article]() Author: Shai Almog Published: 2026-06-05T00:00:00Z Content type: article Language: en Sources: [CodeName One]() Topics: [WebSocket](), [GraphQL](), [gRPC](), [issue tracker](), [API](), [Feathers](), [Java]() Tags: [api](), [electron](), [framework](), [integration](), [issue](), [mac]() ### AI overview Codename One reports that its open issue count fell to 332 after reviewing older tracker reports. The weekly update also covers native Mac builds, WebSockets in the core framework, gRPC and GraphQL integration, a new advertising API, and richer background work. ### Source excerpt The open issue count dropped below 350 after a push through the oldest reports, and the same week brought native Mac builds, WebSockets in the core, gRPC and GraphQL integration, a new advertising API, and richer background work. ## My blog was hacked and Claude and I just fixed it DevFeed: [My blog was hacked and Claude and I just fixed it]() Original publisher: [Read original article]() Author: Julien Published: 2026-05-18T22:02:58Z Content type: opinion Language: en Sources: [Thoughts, stories and ideas.]() Topics: [Claude Code](), [Database](), [Windows](), [Self-hosted](), [nginx]() Tags: [claude-code](), [database](), [development](), [ghost](), [issue](), [reverse-proxy](), [security](), [self-hosted](), [selfhosted](), [web-dev](), [windows]() ### AI overview The author investigates a malicious script injected into the database of a self-hosted Ghost blog. The script displayed fake captcha-related popups only to Windows users, and Claude Code helped trace the problem to the database. ### Source excerpt My self-hosted Ghost blog got silently hacked via a malicious script injected directly into the database, targeting only Windows users. I traced the source of the issue and fixed it quickly with the help of Claude Code. ## Goodbye, Ubuntu 20.04 (netlab 26.05) DevFeed: [Goodbye, Ubuntu 20.04 (netlab 26.05)]() Original publisher: [Read original article]() Published: 2026-05-18T05:43:00Z Content type: release Language: en Sources: [ipSpace.net blog]() Topics: [Ubuntu](), [Python 3.8](), [releases](), [Python 3.10](), [networking](), [qemu]() Tags: [end-of-life](), [github](), [guide](), [issue](), [netlab](), [networking](), [python-3-10](), [python-3-8](), [qemu](), [release](), [ubuntu](), [upgrade](), [upgrades]() ### AI overview The netlab 26.05 release drops support for Python 3.8 and vanilla Ubuntu 20.04, requiring Python 3.10 or newer. The article discusses compatibility with older containerlab releases and cautions that Ubuntu 24.04 upgrades may still have quirks. ### Source excerpt netlab release 26.05 is out. I'll write about its highlights tomorrow; today, I want to focus on one of its breaking changes: netlab no longer works with Python 3.8 (which reached end-of-life in October 2024), so you can no longer install it on a vanilla Ubuntu 20.04 (which reached end of standard support a year ago). We wanted to get rid of old Python versions for ages, but never did because Ubuntu 20.04 shipped with Python 3.8, and many netlab early adopters installed it on Ubuntu 20.04 (and the last thing a networking engineer wants is wasting time with upgrades, right?). Read more ... ## PinePower V2 USB-C ports may report 0V despite outputting the correct voltage DevFeed: [PinePower V2 USB-C ports may report 0V despite outputting the correct voltage]() Original publisher: [Read original article]() Published: 2026-05-12T00:00:00Z Content type: news Language: en Sources: [Community blog on PINE64]() Topics: [USB](), [Microcontroller]() Tags: [issue](), [mcu](), [pinepower](), [power](), [product](), [usb]() ### AI overview Pine64 disclosed that some current Desktop PinePower V2 units may show 0V on their USB-C ports even though they output the correct voltage. The issue cannot be fixed by users because the MCU must be flashed at the factory; corrected batches are planned, but their production timing is unknown. ### Source excerpt Hey everyone, we'd like to make a public disclosure to the community about a product currently selling on the PineStore website (pine64.com). The current Desktop PinePower V2 batch has an issue where in some situations the USB-C ports will report "0V" when there is obviously something attached. In reality it is actually outputting the correct voltage. This has been fixed for future batches, but the current batch still has stock available. There is no fix available for affected Desktop PinePower V2 batches as the MCU can only be flashed at the factory. We have no ETA when the fixed batch will start production as this depends on the rest of the buggered batch being sold. We'll let you all know when the fixed ones hit the store. And please don't open your PinePower devices as they're high voltage power supplies, which can lead to serious risks. ## May 2026 Updates #2 for XCP-ng 8.3 LTS DevFeed: [May 2026 Updates #2 for XCP-ng 8.3 LTS]() Original publisher: [Read original article]() Author: Samuel Verschelde Published: 2026-05-07T17:32:25Z Content type: release Language: en Sources: [XCP-ng Blog]() Topics: [schema-evolution](), [API](), [Feathers]() Tags: [2026](), [api](), [compatibility](), [issue](), [lts](), [maintenance](), [maintenance-updates](), [storage](), [update](), [updates]() ### AI overview This release provides maintenance updates for XCP-ng 8.3 LTS, fixing a backward-compatibility issue that affected rolling pool updates using XOSTOR. ### Source excerpt Today's update addresses an issue with the rolling pool update process on pools using XOSTOR. ## Lovable's handling of a security regression drew criticism over its response and user communications DevFeed: [Lovable's handling of a security regression drew criticism over its response and user communications]() Original publisher: [Read original article]() Author: Sergio Visinoni Published: 2026-04-22T05:02:05Z Content type: opinion Language: en Sources: [Sudo Make Me a CTO]() Topics: [Security](), [incident](), [Cybersecurity]() Tags: [ai](), [cybersecurity](), [incident](), [issue](), [security]() ### AI overview This commentary examines Lovable's handling of a security regression that exposed chat histories in public projects. It argues that the company's response, including incomplete remediation for existing projects and communication concerns, intensified the incident's impact on users and security researchers. ### Source excerpt How a potentially easy-to-handle security issue turned into a complete PR disaster for the hyped European AI-startup Lovable. ## libosmocore - libosmocore 1.14.0 released DevFeed: [libosmocore - libosmocore 1.14.0 released]() Original publisher: [Read original article]() Author: osmith Published: 2026-04-15T11:01:17Z Content type: release Language: en Sources: [Open Source Mobile Communications: News]() Topics: [changelog](), [API]() Tags: [api](), [bug](), [changelog](), [issue](), [tracker]() ### AI overview libosmocore 1.14.0 has been released with fixes across core, GSUP, sockets, statistics, GSM, networking, and I/O, plus the new osmo_netdev_del_addr() API. ### Source excerpt Today we've released libosmocore 1.14.0. The changelog over 1.13.1 is as follows: libosmocore (1.14.0) unstable; urgency=medium [ Eric Wild ] * core: fix config.h [ Vadim Yanitskiy ] * gsup: encode_pdp_info(): fix wrong pdp_address index * socket: osmo_sockaddr_from_str_and_uint(): fix memleak * stats: osmo_stats_reporter_udp_open(): fix unconditional jump * gsm48: fix missing/misspelled value-strings * gsm48: remove duplicate GSM48_MT_RR_HANDO_INFO * gsmtap_util: gsmtap_gsm_channel_names[]: fix PTCCH string * netdev: netdev_mnl_set_mtu(): drop unneeded variables [ Pau Espin Pedrol ] * osmo_io: Rewrite iofd_handle_send_completion() to fix multiple issues * osmo_io: Fix msgb memleak if iofd is unregistered during write_cb with >1 io buffers * netdev: Add API osmo_netdev_del_addr() * tun: Fix typo in log line and comment -- Oliver Smith Wed, 15 Apr 2026 11:48:23 +0200 ## Retronetworking - 2026-04-01: RetroNetCall: 40C3 c3isdn network, new location DevFeed: [Retronetworking - 2026-04-01: RetroNetCall: 40C3 c3isdn network, new location]() Original publisher: [Read original article]() Author: xent Published: 2026-03-30T23:44:02Z Content type: news Language: en Sources: [Open Source Mobile Communications: News]() Topics: [Network]() Tags: [2026](), [announce](), [bug](), [communication](), [https](), [issue](), [location](), [network](), [presentation](), [tracker]() ### AI overview An announcement for the April 1, 2026 RetroNetCall, a retronetworking-oriented spin-off of OsmoDevCall. The session includes a presentation on initial findings from a visit to the Hamburg Messe, the new site for that year's Chaos Communication Congress. ### Source excerpt We're happy to announce the next incarnation of RetroNetCall, the retronetworking oriented spin-off of OsmoDevCall This time, we have a presentation about the first findings after @jolly and @xent visit of the Hamburg Messe on 28th March 2026 (the new site for this year Chaos Communication Congress). When: Wednesday, April 1st, 2026 from 20:00 CEST Time Topic Who 20:00 Meet and Greet everyone 20:10 40C3 New Location (Hamburg Messe) @jolly and @xent Where: https://osmocom.org/RetroNetCall (Big Blue Button of https://franken.de/) [Next page]()