# Central Published articles for Central. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CAPIF 5: Regional Interconnectivity in Central Asia DevFeed: [CAPIF 5: Regional Interconnectivity in Central Asia]() Original publisher: [Read original article]() Author: Anastasiya Pak Published: 2026-09-17T17:29:36Z Content type: article Language: en Sources: [RIPE Labs]() Topics: [Internet](), [Routing Security](), [networking](), [Networks]() Tags: [2026](), [adoption](), [aspa](), [atlas](), [central](), [connectivity](), [country](), [events](), [internet](), [ipv4](), [ipv6](), [ixps](), [measurements](), [progress](), [region](), [report](), [research](), [ripe](), [ris](), [routing](), [routing-security](), [rpki](), [traffic]() ### AI overview This report examines changes in Central Asia's Internet connectivity since CAPIF 1. It describes more direct regional routes, expanding IXPs, stronger routing security and new links toward Pakistan, China, Azerbaijan and Europe, while noting persistently low IPv6 adoption and continued, though reduced, reliance on routes through Russia. ### Source excerpt Central Asia's Internet looks very different than it did back at CAPIF 1. We trace the rise of direct regional routes, stronger routing security and new connectivity options - along with the gaps that remain. ## How Chainguard Libraries for Java Secures Dependencies at Maven Central Scale DevFeed: [How Chainguard Libraries for Java Secures Dependencies at Maven Central Scale]() Original publisher: [Read original article]() Published: 2025-06-25T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard libraries](), [Java](), [Reverse Dependencies](), [Maven](), [Open Source]() Tags: [central](), [chainguard-libraries](), [chainguard-libraries-for-java](), [dependencies](), [graph](), [java](), [java-libraries](), [java-packages](), [libraries](), [maven-central](), [open-source](), [supply-chain]() ### AI overview This article explains how Chainguard is building Chainguard Libraries for Java to secure open-source JVM dependencies from Maven Central. It describes the repository's scale and the initial selection strategy, which uses dependency-graph data to identify popular libraries and prioritizes newer projects. ### Source excerpt Chainguard Libraries for Java is Chainguard's repository of malware-resistant Java dependencies. Learn how we are building and maintaining over 50,000 projects. ## Mastering incident routing: a critical component in incident management DevFeed: [Mastering incident routing: a critical component in incident management]() Original publisher: [Read original article]() Author: Tom Wentworth Published: 2025-03-10T16:22:00Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Routing (disambiguation)](), [incident management](), [incident](), [Automation]() Tags: [automation](), [central](), [dependencies](), [how-to](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [infrastructure](), [outage](), [post](), [post-mortem](), [real-time](), [routing](), [site-reliability](), [slack-incident](), [systems]() ### AI overview This article explains how effective incident routing sends alerts to the right people at the right time, reducing response delays, confusion, alert fatigue, and incident impact. It recommends using service ownership and dependency context, including data from the incident.io Catalog, to enable automated routing and support incident response communication. ### Source excerpt Mastering incident routing is key to reducing response times and ensuring alerts reach the right people, fast. This post breaks down how to build a smarter routing strategy using real-time service ownership data from incident.io Catalog. ## Attention Is Off By One DevFeed: [Attention Is Off By One]() Original publisher: [Read original article]() Author: Evan Miller Published: 2023-07-24T16:05:00Z Content type: opinion Language: en Sources: [Evan Miller]() Topics: [Transformer](), [quantization](), [Large Language Model](), [AI Models]() Tags: [central](), [cloud](), [edge](), [llms](), [pytorch](), [quantization]() ### AI overview Evan Miller argues that the standard Transformer attention formula contains an overlooked off-by-one error. He discusses how outlier weights and activations complicate quantization and deployment, and proposes investigating fixes including Softmax One and QuietAttention. ### Source excerpt Transformer has a mathematical bug that has been overlooked for 6+ years. I propose fixing its outliers with two new devices, Softmax One and QuietAttention: Attention Is Off By One ## KotlinDL 0.3: поддержка ONNX, Object Detection API, 20+ новых моделей в ModelHub, и много новых слоев DevFeed: [KotlinDL 0.3: поддержка ONNX, Object Detection API, 20+ новых моделей в ModelHub, и много новых слоев]() Original publisher: [Read original article]() Author: zaleslaw (JetBrains) Published: 2021-10-04T13:56:53Z Content type: release Language: ru Sources: [JetBrains RU]() Topics: [onnx](), [object-detection](), [Maven](), [Maven Central](), [Artificial Intelligence](), [Keras](), [PyTorch]() Tags: [big-data](), [central](), [deep-learning](), [fine-tuning](), [image-recognition](), [keras](), [kotlin](), [machine-learning](), [maven-central](), [object-detection](), [onnx](), [onnx-runtime](), [pytorch](), [tensorflow]() ### AI overview This release article presents KotlinDL 0.3, adding ONNX model support through ONNX Runtime Java API, new ModelHub models, an experimental high-level image-recognition API, additional layers, and Maven Central availability. It also describes object-detection support and fine-tuning limitations for ONNX models. ### Source excerpt Представляем версию 0.3 библиотеки глубокого обучения KotlinDL! Вас ждет множество новых фич: новые модели в ModelHub (включая модели для обнаружения объектов и распознавания лиц), возможность дообучать модели распознавания изображений, экспортированные из Keras и PyTorch в ONNX, экспериментальный высокоуровневый API для распознавания изображений и множество новых слоев, добавленных контрибьюторами. Также KotlinDL теперь доступен в Maven Central. В этой статье мы коснемся самых главных изменений релиза 0.3. Полный список изменений доступен по ссылке. Узнать больше о релизе ## JCenter Shutdown Impact on Gradle Builds DevFeed: [JCenter Shutdown Impact on Gradle Builds]() Original publisher: [Read original article]() Author: Sterling Greene Published: 2021-02-22T05:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Maven](), [Security](), [Git](), [GitHub]() Tags: [bintray](), [build](), [central](), [dependencies](), [documentation](), [github](), [gradle](), [jfrog](), [maven-central](), [mirror](), [packages](), [pipelines](), [release](), [update]() ### AI overview This article explains how the shutdown of Bintray and JCenter could disrupt Gradle builds by affecting dependency resolution, plugin dependencies, and package publishing. It describes JCenter's relationship to Maven Central, notes that JCenter became read-only indefinitely, and recommends moving builds and publishing workflows to other repositories, with Maven Central becoming Gradle's default in new samples and init templates. ### Source excerpt ℹ Update on July 15, 2024 See our recent blog post for up-to-date information about the Plugin Portal and JCenter. On February 3 2021, JFrog announced that they will be shutting down Bintray and JCenter. This post tells you what you need to know and do to avoid disruptions to your build pipelines. Your build may be affected by this shutdown in several ways: Gradle may not be able to download the dependencies used to compile, test or run your code. Gradle may not be able to download the dependencies used by plugins to configure your build. Gradle may no longer be able to publish your package to Bintray. Additionally, you should be aware of the security considerations when moving from one repository to another. UPDATE: JFrog has decided to keep JCenter as a read-only repository indefinitely. New package and versions are no longer accepted on JCenter. All Bintray services have been shutdown. Background JCenter is a central artifact repository, like Maven Central. Software projects use JCenter to distribute their software to other people. JCenter also serves as a mirror for Maven Central, so any dependencies available on Maven Central are also available on JCenter (but not vice versa). Bintray is a management layer that software projects use to publish and promote packages to JCenter. Bintray also allowed users to create public user-specific repositories that were isolated from JCenter. Both of these services are affected by the shutdown. Impact to builds By default, Gradle does not add an artifact repository to your project; however, Gradle does provide a convenient API for using the JCenter repository. The Gradle Build Init plugin produces build templates that use the JCenter repository to resolve dependencies. In many code examples and documentation, JCenter is used as an example repository. It's very likely that you have builds that rely on JCenter. We've found over a million Git repositories on GitHub that use JCenter with Gradle. To discourage new projects from u ## Interesting Upcoming pgDays DevFeed: [Interesting Upcoming pgDays]() Original publisher: [Read original article]() Author: Map Published: 2019-10-29T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [.NET Framework]() Tags: [berlin](), [central](), [conference](), [conferences](), [europe](), [events](), [postgres](), [postgresql]() ### AI overview The author highlights upcoming pgDay conferences in Helsinki, Paris, and San Francisco, recommending them as opportunities to learn about PostgreSQL, hear from technology companies, meet attendees, and submit conference proposals. ### Source excerpt I've been to a lot of conferences over the years. PgConf EU, PostgresOpen, too many pgDays to count, and even more none Postgres conferences (OSCON, Strangeloop, Railsconf, PyCon, LessConf, and many more). I've always found Postgres conferences one of the best places to get training and learn about what's new with Postgres (in addition to Dimitri's recent book, more on that below). They're my regular stop to catch up on all the new features of a release before it comes out, and often there is a talk highlighting what is new with a simple easy to understand summary once released. I just got back from PGConf EU a little over a week ago and it was a great time. I'm sure we'll see some rundowns of it start appearing on Postgres planet. But, as far as I'm concerned PGConf EU is in the past (unless your counting next year which is in Berlin-in which case I'll see you there). For me it's time to look to the future and there are a number of upcoming pgDays I'm looking forward to. The first two I want to highlight are separate events, but you'll notice they're scheduled nicely for you to easily attend both. With a day in between for travel you'll find that many speakers and attendees depart one and head straight to the other. It makes for an easy opportunity to visit two cities, see two different communities, and yet not have to spend too much time traveling. The first is Nordic pgDay in Helsinki. It's coming up on March 24. The second is pgDay Paris on March 26. Both of these are great single track conferences. If you're in Europe of fancy a trip to Europe I recommend giving them a look, and even better the CFPs are open so consider submitting. Another pgDay I have to mention is right in my backyard. pgDay SF I'm particularly excited for a few reasons: San Francisco is very much a central tech hub, which means a great chance of learning from folks at many many interesting tech companies in attendance Just like Nordic and Paris this is a single track conference, which I'm a ## How a central rsyslog server outage froze Bandcamp applications and services DevFeed: [How a central rsyslog server outage froze Bandcamp applications and services]() Original publisher: [Read original article]() Author: Leigh Dyer Published: 2015-04-28T18:29:22Z Content type: opinion Language: en Sources: [Bandcamp]() Topics: [systems](), [Logging](), [log management](), [configuration](), [Server]() Tags: [app](), [central](), [configuration](), [logging](), [maintenance](), [outage](), [server](), [services](), [tcp](), [uncategorized]() ### AI overview Bandcamp describes how maintenance on its central rsyslog server caused remote logging over TCP to block application-server logging. A shared delivery queue filled up, eventually freezing applications and system services; the team addressed the issue with a dedicated remote-logging queue that spills over to disk. ### Source excerpt Bandcamp was offline briefly yesterday due to what I like to call an unexpected single point of failure. Good systems design is all about addressing single points of failure, making sure you have redundancies in place, but sometimes you discover single points of failure that you didn't realise you had. Yesterday's problem was caused by [...]