Open source *

The idea appeared after a normal working evening went slightly wrong.

I opened a repository, started a build, and noticed that nearly every useful action required a connection to somebody else’s server. The source code was hosted remotely. The CI runner was remote. Package metadata came from remote registries. Test files were downloaded from object storage. API collections were synchronized through a cloud account. Documentation lived in another browser tab. Even code completion waited for a remote model.

My laptop was powerful enough to compile the project, run several databases, and heat the room better than the radiator. Still, it behaved more like a terminal connected to a collection of external services.

So I made a simple rule for one month:

The main development workflow had to remain usable with the network disconnected.

I did not try to recreate the entire Internet in Docker. Public package registries, operating system updates, and communication tools were still allowed during planned synchronization periods. But coding, commits, builds, tests, documentation, API experiments, and basic code review had to work locally.

The first assumption was that this would mostly be a Docker Compose exercise.

It was not.

The containers were the easy part. The difficult part was discovering all the invisible contracts hidden inside a normal cloud-based workflow.

One of the most inspiring moments in microcontroller development is their first installation and launch within a local network. Yet, this very moment can turn into a living hell when the procedure has to be repeated dozens or hundreds of times. Deploying dozens of identical controllers simultaneously demands hours of monotonous configuration—time that any engineer would rather spend on more creative and useful tasks. To solve this problem, a lightweight open-source service codenamed "Esp monitor" was developed.

The Configuration Problem and Protocol Choice 

One of the most popular (and importantly, cheap—costing around $2) microcontrollers is the Wemos D1 Mini based on the ESP8266 chip. It is fast, reasonably reliable, and boasts a vast ecosystem of add-on modules. These are the exact controllers widely used in household appliances and DIY projects due to their massive potential for integration into sensors and home automation systems.

However, they are also among the most inconvenient to configure: by default, the only wireless interface "onboard" is Wi-Fi. This means connecting to a new wireless access point turns into another "dance with a tambourine".

It might seem that this task could be solved by classic port forwarding out of the local Wi-Fi network, but in most scenarios, this is a dead end: 

Hello, Habr! My name is Nikita Pastukhov—author of FastStream, Principal Engineer, and maintainer of AG2 (a framework for developing agents). I’ve been in development for 8 years, and for the last year, I’ve been up to my ears in agents.

And I want to prove to you that writing your own agent is no more difficult than writing a CRUD

Why does this even need proving? Because there’s a noticeable gap between what’s happening with AI globally and what’s happening in the average Russian company. Globally—every company has an OpenAI subscription, there are a billion startups with AI products, and agents are deeply integrated into the back office. In Russia—it’s “dangerous, we host our own models,” “it’s unclear,” and support chatbots. Globally, engineers already know how to develop agents. In Russia—it’s “what even is that?”

So let’s break down how agents work using the example of OpenClaw—the most hyped “personal AI agent” right now. It lives in your messenger, sorts your email, manages your social media, writes code, and deploys services. Its popularity is a testament to how little people are currently using agents in their daily lives. For those in the know, OpenClaw hasn’t brought anything new to the table.

Author: Sergey Lukyanchikov, C-NLTX/Open-Source

Disclaimer: The views expressed in this document reflect the author's subjective perspective on the current and potential capabilities of jBPM.

TL;DR: Zero "quantum supremacy". Zero "agentic orchestration". Zero other hype. Just an approach to achieving an efficient quantum-assisted automation using 100% free open-source components (except for Azure).

In my previous article, I discussed the rationale for adopting jBPM as an AI orchestration platform. This article extends that discussion by examining jBPM’s ability to automate quantum computations and to incorporate their results into business processes and related analytical workflows:

When you buy a $20 ChatGPT subscription, you get access to about $1,000 worth of tokens. When you buy a $100 Claude subscription, you get access to about $2,000 worth of tokens. However, these subscriptions cannot be connected to Cursor directly. The API and subscription request formats are different, so you need a workaround — proxying the requests.

Malicious code was injected into four Laravel-Lang projects, presumably stealing credentials from the devices on which it was run.

Popular projects were affected: Lang, Actions, Attributes, and HTTP Statuses.

The incident concerns not only Laravel...

We are losing history in all forms, and maybe you can help to preserve it.

Wikimedia Commons will accept your scans of 19th-century books, newspapers, documents.

Async logging is often treated as an obvious optimization.

It isn’t.

It just moves the cost somewhere else.

This idea sounds simple: synchronous logging blocks, async logging doesn’t — so it must be faster.

But once you look at what actually happens inside the system, the picture becomes very different.

Libraries like Quill are built around asynchronous pipelines. Others, like spdlog, support both synchronous and asynchronous modes. Some systems — including logme — deliberately mix synchronous formatting with asynchronous output.

Despite these differences, they all run into the same fundamental constraints.

Since I'm a fan of self-hosting, I have a home infrastructure:

Orange Pi - a media server;

Synology - a file dump;

Neptune 4 - a 3D printer with a web interface and a camera feed. And I'd like to have secure access to it externally via my phone and PC, while also having internet access outside the RF. I used to use OpenVPN for these needs, but it's no longer reliable. So I started studying the documentation for an excellent tool from our Chinese comrades - Xray!

What you'll need:

A server with an external IP for the infrastructure. In my case, it's an Orange Pi, hereinafter - Bridge

The server you want to access - Server

A server outside the RF for internet access. Hereinafter - Proxy

A client of your choice. Hereinafter - Client

Client and server on Linux - Xray-core, which can be installed via the official Xray installation script

Client for Android - v2rayNG

More clients can be found in the Xray-core repository

Let's take the VLESS-TCP-XTLS-Vision-REALITY configuration file as a base and start reading the Xray documentation

Routing is done on the client. For example, if the client accesses the xray.com domain, we route the traffic to the Bridge, and for all other connections - to the Proxy. Then the Bridge routes the traffic to the Server if the client accessed server.xray.com.
It looks like this:

The reality of today is that most people write dossiers on themselves in their social networks. In this article, you will learn about some tools that will help you find out the maximum amount of information about a person.

A VPN is a technology for a secure connection to a remote computer or network, and for most users, it's simply a safe way to use the internet in public Wi-Fi zones.

In this article, we will look at four ways to create your own VPN. Let's start with the simplest option, which is manageable even for novice PC users.

Pinterest is a visual discovery platform where people can find ideas like recipes, home and style inspiration, and much more. The platform offers its partners shopping capabilities as well as a significant advertising opportunity with 500+ million monthly active users. Advertisers can purchase ads directly on Pinterest or through partnerships with advertising agencies. Due to our huge scale, advertisers get an opportunity to learn about their Pins and their interaction with Pinterest users from the analytical data. This gives advertisers an opportunity to make decisions which will allow their ads to perform better on our platform.

Hello, Habr! I'd like to share my experience developing such a system.
The defining parameters of a domain-specific system are:

Apache Druid has been a staple for real-time analytics. However, with evolving and sophisticated analytics demands, it has faced challenges in satisfying modern data performance needs. Enter StarRocks, a high-performance, open-source analytical database, designed to adeptly meet the advanced analytics needs of contemporary enterprises by offering robust capabilities and performance.

In this article, we’ll explore the functionalities, strengths, and challenges of both Apache Druid and StarRocks. Using practical examples and benchmark results, we aim to guide you in identifying which database might best meet your data needs.

Hello, Habr! Today I want to tell you about my project — “Game Engine 3”, a software shell for creating 2D games and applications...

Learning Shopify has been on my bucket list for a few years now. Plenty of people in my circle — friends, colleagues, and fellow devs — are all somehow involved with Shopify in one way or the other. Earlier this year, I finally had some breathing room between projects, so I figured it was the perfect time to give Shopify a proper look.

I started exploring the platform by setting up a dev store, poking around the admin, and skimming through the API manual. While this was a quick and easy start, it didn’t give me a deeper understanding of the platform. Plus, clicking my way through the UI felt repetitive and tedious.

That got me thinking: is there a more efficient, developer-centric way to manage a store? Something that I could run in a terminal, plug into a CI/CD pipeline, or script my way out of those mundane tasks.

This world needs a new theory — a theory that could describe all the theories on the planet. A theory that could easily describe philosophy, mathematics, physics, and psychology. The one that makes all kinds of sciences computable.

This is exactly what we are working on. If we succeed, this theory will become the unified meta-theory of everything.

A year has passed since our last publication, and our task is to share the progress with our English-speaking audience. This is still not a stable version; it’s a draft. Therefore, we welcome any feedback, as well as your participation in the development of the links theory.

As with everything we have done before, the links theory is published and released into the public domain — it belongs to humanity, that means, it is yours. This work has many authors, but the work itself is far more important than any specific authorship. We hope that today it can become useful to more people.

We invite you to become a part of this exciting adventure.

Author: Sergey Lukyanchikov, C-NLTX/Open-Source

Disclaimer: The views expressed in this document reflect the author's subjective perspective on the current and potential capabilities of jBPM.

TL;DR: Zero "agentic AI". Zero "cloud native". Zero other hype. Just an approach to achieving an efficient AI-centric automation using 100% free open-source components.

This text presents jBPM as a platform for orchestrating external AI-centric environments, such as Python, used for designing and running AI solutions. We will provide an overview of jBPM’s most relevant functionalities for AI orchestration and walk you through a practical example that demonstrates its effectiveness as an AI orchestration platform:

Написал лонгрид на английском о текущем состоянии открытых средств проектирования ASIC-ов. Заодно познакомил англоязычных читателей с практиками шаманов Сибири и фигурой Ивана Сусанина. Упомянул планируемые семинары в Мексике и Армении.

A text on the current state of Open-source ASIC design tools. Includes side discussions of the upcoming hackathons in Mexico and Armenia, Docker and Python, Static Timing Analysis and RISC-V, Siberian shamans and treacherous swamps in Belarus.

Trends change rapidly in UI/UX, and new year means quite a few new emerging innovations that designers should be aware of in order to create relevant and engaging designs. Some trends stay on from previous years, some are completely new, and some might end up being the fleeting ones, so it’s important to pearl off those that truly elevate user experience and make a better impact on your product. Let’s discuss some of the most anticipated UI/UX trends of the coming year.