# bind

Published articles for bind.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Events as Triggers for Behavioral Diversity in Multi-Agent Reinforcement Learning

DevFeed: [Events as Triggers for Behavioral Diversity in Multi-Agent Reinforcement Learning](<https://devfeed.tech/articles/events-as-triggers-for-behavioral-diversity-in-multi-agent-reinforcement-learning-111399.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2605.12388>)

Author: Hannes B\\"uchi, Manon Flageat, Eduardo Sebasti\\'an, Amanda Prorok

Published: 2026-11-02T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Reinforcement learning](<https://devfeed.tech/topics/reinforcement-learning.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [lora](<https://devfeed.tech/topics/lora.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agent-identities](<https://devfeed.tech/tags/agent-identities.md>), [agent-identity](<https://devfeed.tech/tags/agent-identity.md>), [agents](<https://devfeed.tech/tags/agents.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [based](<https://devfeed.tech/tags/based.md>), [behavior](<https://devfeed.tech/tags/behavior.md>), [behaviors](<https://devfeed.tech/tags/behaviors.md>), [benchmarks](<https://devfeed.tech/tags/benchmarks.md>), [bind](<https://devfeed.tech/tags/bind.md>), [build](<https://devfeed.tech/tags/build.md>), [changes](<https://devfeed.tech/tags/changes.md>), [construction](<https://devfeed.tech/tags/construction.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [cs-ma](<https://devfeed.tech/tags/cs-ma.md>), [diversity](<https://devfeed.tech/tags/diversity.md>), [events](<https://devfeed.tech/tags/events.md>), [learning](<https://devfeed.tech/tags/learning.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [reinforcement-learning](<https://devfeed.tech/tags/reinforcement-learning.md>), [triggers](<https://devfeed.tech/tags/triggers.md>)

### AI overview

The paper proposes using task-changing events to trigger behavior reassignment in multi-agent reinforcement learning, decoupling behaviors from fixed agent identities. It combines Neural Manifold Diversity, a distance metric for transient, agent-agnostic behaviors, with an event-based hypernetwork that generates LoRA modules over a shared team policy for on-the-fly reconfiguration. The authors state that the design prevents diversity from interfering with reward maximization. Their abstract reports better performance than established baselines across benchmarks, zero-shot generalization, and success on tasks requiring sequential behavior reassignment where the compared methods did not solve them. The supplied text contains the abstract, not detailed benchmark evidence.

### Source excerpt

arXiv:2605.12388v3 Announce Type: replace-cross Abstract: Effective multi-agent cooperation requires agents to adopt diverse behaviors as task conditions evolve-and to do so at the right moment. Yet, current Multi-Agent Reinforcement Learning (MARL) frameworks that facilitate this diversity are still limited by the fact that they bind fixed behaviors to fixed agent identities. Consequently, they are ill-equipped for tasks where agents need to take on different roles at very specific moments in time. We argue that, to define these behavioral transitions, the missing ingredient is $\textbf{events}$. Events are changes in the state of the system that induce qualitative changes in the task. Based on this view, we introduce a framework that decouples agent identity from behavior, capturing a continuous manifold from which agents instantiate their behaviors in response to events. This framework is based on two elements. First, to build an expressive behavior manifold, we introduce Neural Manifold Diversity (NMD), a formal distance metric that remains well-defined when behaviors are transient and agent-agnostic. Second, we use an event-based hypernetwork that generates Low-Rank Adaptation (LoRA) modules over a shared team policy, enabling on-the-fly agent-policy reconfiguration in response to events. We prove that this construction ensures that diversity does not interfere with reward maximization by design. Empirical results demonstrate that our framework outperforms established baselines across benchmarks while exhibiting zero-shot generalization, and being the only method that solves tasks requiring sequential behavior reassignment.

## New Linux 7.4 Feature For Reducing AI Noise Already Reverted Due To A "Crazy Beast"

DevFeed: [New Linux 7.4 Feature For Reducing AI Noise Already Reverted Due To A "Crazy Beast"](<https://devfeed.tech/articles/new-linux-7-4-feature-for-reducing-ai-noise-already-reverted-due-to-a-crazy-beast-109837.md>)

Original publisher: [Read original article](<https://www.phoronix.com/news/Linux-7.4-Drops-Taint-Bind>)

Author: Michael Larabel

Published: 2026-10-31T12:15:22Z

Content type: news

Language: en

Sources: [Phoronix](<https://devfeed.tech/sources/phoronix.md>)

Topics: [Linux](<https://devfeed.tech/topics/linux.md>), [Fuzzing/Fuzz testing](<https://devfeed.tech/topics/fuzzing.md>)

Tags: [7-4](<https://devfeed.tech/tags/7-4.md>), [ai](<https://devfeed.tech/tags/ai.md>), [attack](<https://devfeed.tech/tags/attack.md>), [bind](<https://devfeed.tech/tags/bind.md>), [bots](<https://devfeed.tech/tags/bots.md>), [bug-reports](<https://devfeed.tech/tags/bug-reports.md>), [desktop-linux](<https://devfeed.tech/tags/desktop-linux.md>), [driver](<https://devfeed.tech/tags/driver.md>), [drivers](<https://devfeed.tech/tags/drivers.md>), [feature](<https://devfeed.tech/tags/feature.md>), [fuzzing](<https://devfeed.tech/tags/fuzzing.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-7-4](<https://devfeed.tech/tags/linux-7-4.md>), [linux-benchmarking](<https://devfeed.tech/tags/linux-benchmarking.md>), [linux-hardware-benchmarks](<https://devfeed.tech/tags/linux-hardware-benchmarks.md>), [linux-hardware-reviews](<https://devfeed.tech/tags/linux-hardware-reviews.md>), [linux-how-to](<https://devfeed.tech/tags/linux-how-to.md>), [linux-performance](<https://devfeed.tech/tags/linux-performance.md>), [linux-server-benchmarks](<https://devfeed.tech/tags/linux-server-benchmarks.md>), [llm](<https://devfeed.tech/tags/llm.md>), [noise](<https://devfeed.tech/tags/noise.md>), [open-source-graphics](<https://devfeed.tech/tags/open-source-graphics.md>), [pcie](<https://devfeed.tech/tags/pcie.md>), [phoronix](<https://devfeed.tech/tags/phoronix.md>), [phoronix-test-suite](<https://devfeed.tech/tags/phoronix-test-suite.md>), [testing](<https://devfeed.tech/tags/testing.md>), [ubuntu-benchmarks](<https://devfeed.tech/tags/ubuntu-benchmarks.md>), [ubuntu-hardware](<https://devfeed.tech/tags/ubuntu-hardware.md>)

### AI overview

Linux 7.4's TAINT_FORCED_BIND feature, intended to flag sysfs bind/unbind use in bug reports and reduce irrelevant fuzzing reports, was reverted after developers found that VFIO users rely on that behavior to detach host drivers and attach PCIe devices to vfio-pci for VM passthrough. Tainting those legitimate workflows would be disruptive. The excerpt says syzbot has stopped the problematic testing, while the revert leaves the broader issue unresolved. Uwe Kleine-König proposed instead tainting use of driver_override and disabling it by default, with drivers able to opt in; that approach may be revisited for Linux 7.5.

### Source excerpt

A new feature merged last week for Linux 7.4 to help reduce AI/LLM generated noise from invalid/irrelevant testing configurations is now reverted due to a "crazy beast" in the VFIO subsystem...

## CVE-2026-61850 - Kargo: Privilege escalation via Project RBAC management in the Kargo API

DevFeed: [CVE-2026-61850 - Kargo: Privilege escalation via Project RBAC management in the Kargo API](<https://devfeed.tech/articles/cve-2026-61850-kargo-privilege-escalation-via-project-rbac-management-in-the-kargo-api-109383.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-61850>)

Author: CVEFEED.io; github.com

Published: 2026-10-30T20:17:11Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [rbac](<https://devfeed.tech/topics/rbac.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Credential theft](<https://devfeed.tech/topics/credential-theft.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [akuity](<https://devfeed.tech/tags/akuity.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [artifacts](<https://devfeed.tech/tags/artifacts.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bind](<https://devfeed.tech/tags/bind.md>), [changes](<https://devfeed.tech/tags/changes.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [container-registry](<https://devfeed.tech/tags/container-registry.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-61850](<https://devfeed.tech/tags/cve-2026-61850.md>), [kargo](<https://devfeed.tech/tags/kargo.md>), [management](<https://devfeed.tech/tags/management.md>), [privilege-escalation](<https://devfeed.tech/tags/privilege-escalation.md>), [project](<https://devfeed.tech/tags/project.md>), [rbac](<https://devfeed.tech/tags/rbac.md>)

### AI overview

CVE-2026-61850 affects Kargo versions from 0.6.0 up to fixes 1.8.14, 1.9.9, and 1.10.8. In the project-scoped RBAC API, delegated permission to edit Roles can be abused to grant unheld permissions, or permission to edit a Role's ServiceAccount can bind an identity to a more powerful Role. The API uses broadly privileged server credentials and checks only the resource kind, not the permissions being granted. An attacker must control an account assigned an administrator-created custom role with relevant RBAC-management permissions; default non-administrator roles do not allow this. Escalation can expose Project Secrets and credentials or alter and delete Project resources, but remains confined to Projects where the attacker has that delegation and does not itself grant cluster-wide or cross-Project access. Stolen Git, container-registry, or Helm-registry credentials may extend impacts to those systems.

### Source excerpt

CVE ID :CVE-2026-61850 Published : Oct. 30, 2026, 8:17 p.m. | 1 hour, 37 minutes ago Description :Kargo manages and automates the promotion of software artifacts. From 0.6.0 until 1.8.14, 1.9.9, and 1.10.8, two authorization flaws in the `project-scoped RBAC API` let an authenticated user with delegated permission to manage a Project's `Roles` or `ServiceAccounts` confer permissions exceeding the user's own. A user authorized to edit `Roles` can create, replace, or add rules granting permissions not held by the user; a user authorized to edit a Role's ServiceAccount can bind an identity, including the user's own, to a more powerful Role. A Kargo Role comprises a `ServiceAccount, Role, and RoleBinding` in the Project namespace. Changes are written using the API server's broadly privileged credentials after only a coarse resource-kind edit check, rather than checking each permission being conferred. This permits escalation to Project-administrator access, disclosure of `Project Secrets` and credentials, and modification or deletion of Project resources. Stolen Git, container-registry, or Helm-registry credentials can extend confidentiality and integrity impacts to those external systems. Escalation remains limited to Projects where the attacker already has RBAC-management delegation and does not itself grant cluster-wide or cross-Project access. Default non-administrator roles do not permit these operations; exploitation requires an `administrator-created custom role` granting the relevant permissions and control of an account assigned that role. This issue is fixed in versions 1.8.14, 1.9.9, and 1.10.8. Severity: 9.3 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## CVE-2026-61826 - Bazarr: Plex OAuth API namespace is entirely unauthenticated, allowing config tampering, integration takeover and server-side request forgery

DevFeed: [CVE-2026-61826 - Bazarr: Plex OAuth API namespace is entirely unauthenticated, allowing config tampering, integration takeover and server-side request forgery](<https://devfeed.tech/articles/cve-2026-61826-bazarr-plex-oauth-api-namespace-is-entirely-unauthenticated-allowing-config-tampering-integration-takeover-and-server-side-request-forgery-109182.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-61826>)

Author: CVEFEED.io; github.com

Published: 2026-10-30T17:17:27Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [API](<https://devfeed.tech/topics/api.md>), [API keys](<https://devfeed.tech/topics/api-keys.md>), [account takeover](<https://devfeed.tech/topics/account-takeover.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [account](<https://devfeed.tech/tags/account.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [apis](<https://devfeed.tech/tags/apis.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bazarr](<https://devfeed.tech/tags/bazarr.md>), [beta](<https://devfeed.tech/tags/beta.md>), [bind](<https://devfeed.tech/tags/bind.md>), [config](<https://devfeed.tech/tags/config.md>), [credential-exposure](<https://devfeed.tech/tags/credential-exposure.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-61826](<https://devfeed.tech/tags/cve-2026-61826.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [forgery](<https://devfeed.tech/tags/forgery.md>), [integration](<https://devfeed.tech/tags/integration.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [plex](<https://devfeed.tech/tags/plex.md>), [server-side-request-forgery](<https://devfeed.tech/tags/server-side-request-forgery.md>)

### AI overview

Before Bazarr 1.5.7-beta.14, handlers in the Plex OAuth API namespace lack authentication, allowing anonymous callers to alter persistent configuration, disable or take over the Plex integration, and expose the configured API key. Attacker-controlled server URLs can trigger outbound requests carrying that key in `X-Plex-Token`, creating SSRF and credential-exposure risks. Version 1.5.7-beta.14 adds authentication to close the anonymous API-mutation path. The source does not establish complete OAuth state validation; it identifies that as a separate unresolved concern.

### Source excerpt

CVE ID :CVE-2026-61826 Published : Oct. 30, 2026, 5:17 p.m. | 1 hour, 57 minutes ago Description :Bazarr is a companion application to Sonarr and Radarr. Prior to 1.5.7-beta.14, the `api_ns_plex` namespace in `bazarr/api/plex/oauth.py` omits `@authenticate` on its Resource handlers, while normal APIs require an API key and no global authentication hook compensates. Anonymous callers can invoke `POST /api/plex/oauth/logout` to clear credentials and disable the integration, or `POST /api/plex/apikey` to persist an attacker-selected key, without a PIN, account or state precondition. `POST /api/plex/oauth/pin` and `GET /api/plex/oauth/pin//check` additionally allow an attacker who completes a PIN with an attacker-controlled Plex account to bind that account's token to the instance. `PlexPinCheck` skips state validation when `state_param` is absent and merely logs a mismatch without stopping execution. `POST /api/plex/select-server`, `POST /api/plex/oauth/servers`, `POST /api/plex/webhook/create`, `POST /api/plex/webhook/delete` and `POST /api/plex/encrypt-apikey` expose further `write_config()` operations. Attacker-controlled server URLs feed later outbound requests carrying the configured API key in `X-Plex-Token`, enabling server-side request forgery and credential exposure in addition to persistent configuration tampering and integration denial of service. Version 1.5.7-beta.14 closes the anonymous API-mutation path by adding authentication; complete OAuth state validation is not established and remains a separate residual for curator review. Severity: 10.0 | CRITICAL Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Vercel Daemons can now call services with bindings

DevFeed: [Vercel Daemons can now call services with bindings](<https://devfeed.tech/articles/vercel-daemons-can-now-call-services-with-bindings-109247.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/vercel-daemons-can-now-call-services-with-bindings>)

Author: Nik Sidnev

Published: 2026-10-30T00:00:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [Vercel](<https://devfeed.tech/topics/vercel.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [bind](<https://devfeed.tech/tags/bind.md>), [call](<https://devfeed.tech/tags/call.md>), [can](<https://devfeed.tech/tags/can.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [docs](<https://devfeed.tech/tags/docs.md>), [environment](<https://devfeed.tech/tags/environment.md>), [http](<https://devfeed.tech/tags/http.md>), [private](<https://devfeed.tech/tags/private.md>), [promotion](<https://devfeed.tech/tags/promotion.md>), [rollback](<https://devfeed.tech/tags/rollback.md>), [routing](<https://devfeed.tech/tags/routing.md>), [service](<https://devfeed.tech/tags/service.md>), [services](<https://devfeed.tech/tags/services.md>), [target](<https://devfeed.tech/tags/target.md>), [tls](<https://devfeed.tech/tags/tls.md>), [url](<https://devfeed.tech/tags/url.md>), [variable](<https://devfeed.tech/tags/variable.md>), [vercel](<https://devfeed.tech/tags/vercel.md>)

### AI overview

Vercel Daemons can reach services in their deployment through one-way service bindings. A daemon declares the target service and an environment variable to receive its URL; it can then call that URL with a regular HTTP request. Vercel handles internal routing, authentication, and TLS while the service remains private. Services cannot bind back to daemons, and each daemon instance continues calling the deployment that started it, including after a promotion or rollback.

### Source excerpt

Vercel Daemons can now call the services in their deployment through service bindings. Declare the binding on the daemon. It names the target service and the environment variable that receives the service's URL: The daemon calls that URL like any other HTTP endpoint. Vercel handles the internal routing, authentication, and TLS, and the service stays private: Bindings point one way: services can't bind to daemons. Each instance keeps calling the deployment that started it, even after a promotion or rollback. Learn more about daemon service bindings in the docs. Read more

## CVE-2026-61542 - Gearboy advisory / Gearsystem body: Unauthenticated network exposure of MCP HTTP tools

DevFeed: [CVE-2026-61542 - Gearboy advisory / Gearsystem body: Unauthenticated network exposure of MCP HTTP tools](<https://devfeed.tech/articles/cve-2026-61542-gearboy-advisory-gearsystem-body-unauthenticated-network-exposure-of-mcp-http-tools-105497.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-61542>)

Author: CVEFEED.io; github.com

Published: 2026-10-28T20:18:27Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [ecosystem-security](<https://devfeed.tech/topics/ecosystem-security.md>), [Cross-origin resource sharing (CORS)](<https://devfeed.tech/topics/cors.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [bearer](<https://devfeed.tech/tags/bearer.md>), [bind](<https://devfeed.tech/tags/bind.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [cve-2026-61542](<https://devfeed.tech/tags/cve-2026-61542.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [emulator](<https://devfeed.tech/tags/emulator.md>), [files](<https://devfeed.tech/tags/files.md>), [http](<https://devfeed.tech/tags/http.md>), [localhost](<https://devfeed.tech/tags/localhost.md>), [loopback](<https://devfeed.tech/tags/loopback.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [media](<https://devfeed.tech/tags/media.md>), [network](<https://devfeed.tech/tags/network.md>), [optional](<https://devfeed.tech/tags/optional.md>), [patch](<https://devfeed.tech/tags/patch.md>), [peer](<https://devfeed.tech/tags/peer.md>), [port](<https://devfeed.tech/tags/port.md>)

### AI overview

The optional `--mcp-http` mode exposes MCP tools to reachable network peers: the described Gearsystem transport binds to `INADDR_ANY` (normally port 7777) and dispatches POSTs to `/mcp` without authorization or `Host`/`Origin` checks. A peer can initialize a session and invoke emulator and debugging operations; the advisory bounds the reported impact to the emulator process, debugging state, and local files accepted as media, with no host code execution demonstrated. A loopback-bind control blocked network access. Gearboy 3.8.7 contains a patch.

### Source excerpt

CVE ID :CVE-2026-61542 Published : Oct. 28, 2026, 8:18 p.m. | 59 minutes ago Description :Gearboy is a Game Boy, Game Boy Color, and Super Game Boy emulator and debugger with an embedded MCP server. Gearsystem, the affected component, has an optional `--mcp-http` mode that accepts unauthenticated MCP requests from any reachable network peer despite localhost-only documentation and logging. In the described `platforms/shared/desktop/mcp/mcp_transport.h` transport, the socket binds `INADDR_ANY`, normally on port 7777, and POST requests to `/mcp` reach dispatch without `Authorization`, `Host`, or `Origin` checks. Responses and OPTIONS advertise `Access-Control-Allow-Origin: *`. A peer can initialize an MCP session and invoke exposed emulator/debugging operations; even a garbage bearer token does not block dispatch, while a loopback-bind negative control prevents network access. The reported impact is bounded to the emulator process, debugging state, and local files accepted as media, rather than demonstrated host code execution. Gearboy 3.8.7 contains a patch. Severity: 8.6 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Domain Decoupling Attack: Exploiting the Validation Gap Between Protective DNS and Shared Edge Routing

DevFeed: [Domain Decoupling Attack: Exploiting the Validation Gap Between Protective DNS and Shared Edge Routing](<https://devfeed.tech/articles/domain-decoupling-attack-exploiting-the-validation-gap-between-protective-dns-and-shared-edge-routing-103326.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2608.00643>)

Author: Weizhe Wang, Minhong Dong, Jinhao Li, Lyuchuan Wei, Yao Zhang, Qiang Hu, Qi Guo, Guangquan Xu, Bin Wu

Published: 2026-10-28T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Cryptography and Security](<https://devfeed.tech/sources/arxiv-cryptography-and-security.md>), [arXiv: Networking](<https://devfeed.tech/sources/arxiv-networking.md>)

Topics: [Security](<https://devfeed.tech/topics/security.md>), [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [Authorization](<https://devfeed.tech/topics/authorization.md>), [Zero Trust](<https://devfeed.tech/topics/zero-trust.md>), [DNS security](<https://devfeed.tech/topics/dns-security.md>), [TLS handshake](<https://devfeed.tech/topics/tls-handshake.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [anchor](<https://devfeed.tech/tags/anchor.md>), [attack](<https://devfeed.tech/tags/attack.md>), [bind](<https://devfeed.tech/tags/bind.md>), [block](<https://devfeed.tech/tags/block.md>), [cdn](<https://devfeed.tech/tags/cdn.md>), [censorship](<https://devfeed.tech/tags/censorship.md>), [command-and-control](<https://devfeed.tech/tags/command-and-control.md>), [consistency](<https://devfeed.tech/tags/consistency.md>), [content](<https://devfeed.tech/tags/content.md>), [cs-cr](<https://devfeed.tech/tags/cs-cr.md>), [cs-ni](<https://devfeed.tech/tags/cs-ni.md>), [data-exfiltration](<https://devfeed.tech/tags/data-exfiltration.md>), [decoupling](<https://devfeed.tech/tags/decoupling.md>), [dns](<https://devfeed.tech/tags/dns.md>), [domain](<https://devfeed.tech/tags/domain.md>), [domains](<https://devfeed.tech/tags/domains.md>), [edge](<https://devfeed.tech/tags/edge.md>), [gap](<https://devfeed.tech/tags/gap.md>), [routing](<https://devfeed.tech/tags/routing.md>), [validation](<https://devfeed.tech/tags/validation.md>)

### AI overview

The Domain Decoupling Attack exploits a gap between DNS-based permits, which approve shared edge IP addresses, and edge routing, which selects tenants by name. An attacker can obtain a permit through an allowed domain, then request another tenant using its name as both SNI and HTTP Host. In probes of 1,069,048 domains, 95.8% accepted external SNI and 84.6% returned content matching the named tenant; reported exposure was 99.26% for CDN domains and 92.75% for non-CDN domains. The study says none of the tested defenses tied tenant identity to the DNS-approved name. Cleartext inline IPS can block by SNI, but ECH hides SNI; the Windows ZTDNS permit remains reusable in both cases. The findings describe tested domains and defenses, not universal rates.

### Source excerpt

arXiv:2608.00643v2 Announce Type: replace Abstract: Command-and-control, data transfer, and censorship circumvention can hide in traffic to widely used services. DNS-bound access control grants permits based on resolved IP addresses, while shared edges route requests by tenant identity, creating a validation gap. An attacker can resolve an allowed anchor, obtain a permit for its shared edge address, and access a hidden tenant by presenting the tenant's name as both SNI and HTTP Host. To investigate this gap, we present the Domain Decoupling Attack (DDA), which exploits this gap in CDN and non-CDN hosting while preserving SNI--Host consistency. Across 1,069,048 domains, we conduct 18,025,068 successful probes. Overall, 95.8% of domains accept an external SNI, and 84.6% return content matching the named tenant. Exposure reaches 99.26% across 506,763 CDN domains and 92.75% across 562,285 non-CDN domains. The co-location graph places 666,413 exposed domains in cross-tenant components; 97.7% of 54,069 cross-tenant non-CDN addresses have a confirmed path to another tenant. None of the tested defenses bind tenant identity to the DNS-approved name. Cleartext inline IPS can block access based on SNI, but Encrypted Client Hello (ECH) hides it. The Windows Zero Trust DNS (ZTDNS) permit remains reusable in both cases, enabling the concealment of command-and-control and data-exfiltration traffic and facilitating censorship circumvention. The risk conceals command-and-control and data-exfiltration traffic and supports censorship.

## Access Your Version Controlled Configuration from a Docker Container

DevFeed: [Access Your Version Controlled Configuration from a Docker Container](<https://devfeed.tech/articles/access-your-version-controlled-configuration-from-a-docker-container-100792.md>)

Original publisher: [Read original article](<https://spin.atomicobject.com/accessing-your-version-controlled-configuration-from-a-docker-container/>)

Author: Matt Fletcher

Published: 2026-10-26T12:00:45Z

Content type: article

Language: en

Sources: [Atomic Object](<https://devfeed.tech/sources/atomic-object.md>)

Topics: [Docker Compose](<https://devfeed.tech/topics/docker-compose.md>), [Docker](<https://devfeed.tech/topics/docker.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [.env](<https://devfeed.tech/topics/dotenv.md>)

Tags: [bind](<https://devfeed.tech/tags/bind.md>), [compose](<https://devfeed.tech/tags/compose.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [directory](<https://devfeed.tech/tags/directory.md>), [docker](<https://devfeed.tech/tags/docker.md>), [docker-container](<https://devfeed.tech/tags/docker-container.md>), [extracurricular-activities](<https://devfeed.tech/tags/extracurricular-activities.md>), [git](<https://devfeed.tech/tags/git.md>), [homelab](<https://devfeed.tech/tags/homelab.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>)

### AI overview

To avoid keeping separate copies of version-controlled configuration and Docker service data, the author bind-mounts the configuration file directly from the homelab repository into the container. The Gatus Compose example maps `${HOMELAB_DIR}/gatus/config/config.yaml` to `/config/config.yaml:ro`, while its writable data directory comes from `${SERVICE_DATA_DIR}/gatus/data`. The `.env` file sets those host directories separately. The read-only mount fits Gatus because, according to the author, the application has no reason to change its configuration.

### Source excerpt

For years now, I've stubbornly duplicated version-controlled configuration files into my running Docker containers. Meaning, instead of making the files accessible directly by the container, I've been maintaining both the version-controlled file and copies used by the containers. At last, I've found a solution to help avoid the duplication. The problem Right now I keep [...] The post Access Your Version Controlled Configuration from a Docker Container appeared first on Atomic Spin.

## RiboBridge: protein-conditioned de novo RNA binder structure design

DevFeed: [RiboBridge: protein-conditioned de novo RNA binder structure design](<https://devfeed.tech/articles/ribobridge-protein-conditioned-de-novo-rna-binder-structure-design-96959.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2610.30668>)

Author: Zhou Zhang, Hanqun Cao, Minghao Sun, Odin Zhang, Yang Zhang, Pheng Ann Heng, Wujun Li, Tianfan Fu

Published: 2026-10-23T04:00:00Z

Content type: article

Language: en

Sources: [arXiv: Machine Learning](<https://devfeed.tech/sources/arxiv-machine-learning.md>)

Topics: [Electrical engineering and computer science (EECS)](<https://devfeed.tech/topics/electrical-engineering-and-computer-science-eecs.md>)

Tags: [arxiv](<https://devfeed.tech/tags/arxiv.md>), [assembly](<https://devfeed.tech/tags/assembly.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [bind](<https://devfeed.tech/tags/bind.md>), [binder](<https://devfeed.tech/tags/binder.md>), [bridge](<https://devfeed.tech/tags/bridge.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [canonical](<https://devfeed.tech/tags/canonical.md>), [complex](<https://devfeed.tech/tags/complex.md>), [component](<https://devfeed.tech/tags/component.md>), [cross](<https://devfeed.tech/tags/cross.md>), [cs-lg](<https://devfeed.tech/tags/cs-lg.md>), [design](<https://devfeed.tech/tags/design.md>), [designing](<https://devfeed.tech/tags/designing.md>), [diagnostics](<https://devfeed.tech/tags/diagnostics.md>), [error](<https://devfeed.tech/tags/error.md>), [evaluation](<https://devfeed.tech/tags/evaluation.md>), [generation](<https://devfeed.tech/tags/generation.md>), [interaction](<https://devfeed.tech/tags/interaction.md>), [q-bio-bm](<https://devfeed.tech/tags/q-bio-bm.md>), [rna](<https://devfeed.tech/tags/rna.md>), [structure](<https://devfeed.tech/tags/structure.md>)

### AI overview

RiboBridge separates RNA shape generation from assembly with a target protein. It proposes candidate protein-surface interfaces, generates canonical RNA conformations in the pretrained RiboSphere latent space, predicts interaction constraints across the separate coordinate frames, and uses rigid placement to form a protein-relative pose. On a benchmark of 124 protein-RNA complexes, it achieved the best reported fNAT and DockQ and lowest interface and ligand RMSDs among compared methods under post-hoc interface-correspondence evaluation. In that evaluation, native information selects among candidates only after generation; the reported ranking is therefore specific to this protocol. Ablations and stage-wise diagnostics examine contributions and sources of recovery error.

### Source excerpt

arXiv:2610.30668v1 Announce Type: new Abstract: Designing RNA molecules that bind to target protein structures requires generating both an RNA conformation and its bound complex geometry, without assuming a predefined binding site. Existing approaches generally model these coupled processes within a unified representation, entangling RNA conformation generation with protein-relative placement. In this work, we introduce RiboBridge, a structure-first framework that separates RNA conformational generation from protein--RNA assembly through cross-frame interaction geometry. RiboBridge first proposes multiple candidate RNA-binding interfaces on the protein surface, generates canonical RNA conformations within a pretrained RNA structural latent space (RiboSphere), and then predicts protein--RNA interaction constraints to bridge the independently defined RNA and protein coordinate frames. The resulting interaction geometry is converted into a geometrically consistent protein-relative pose through rigid placement. We evaluate RiboBridge on a temporally split, sequence-filtered, and redundancy-controlled benchmark of 124 protein--RNA complexes. Under post-hoc interface-correspondence evaluation, where native information is used only after generation to select among already generated predicted-pocket candidates, RiboBridge achieves the highest fNAT and DockQ and the lowest interface and ligand RMSDs among compared methods. Component ablations and stage-wise diagnostics further characterize the contributions of RNA conformational generation, interaction prediction, and rigid placement, identifying the main sources of complex-recovery error.

## DevOps Looks Easy... Until the Interviewer Goes Deep

DevFeed: [DevOps Looks Easy... Until the Interviewer Goes Deep](<https://devfeed.tech/articles/devops-looks-easy-until-the-interviewer-goes-deep-85885.md>)

Original publisher: [Read original article](<https://blog.devops.dev/devops-looks-easy-until-the-interviewer-goes-deep-ab1816762ce3?source=rss----33f8b2d9a328---4>)

Author: Arvind Verma

Published: 2026-10-13T10:51:51Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [DevOps](<https://devfeed.tech/topics/devops.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [observability](<https://devfeed.tech/topics/observability.md>)

Tags: [affinity](<https://devfeed.tech/tags/affinity.md>), [ai](<https://devfeed.tech/tags/ai.md>), [api](<https://devfeed.tech/tags/api.md>), [api-server](<https://devfeed.tech/tags/api-server.md>), [apply](<https://devfeed.tech/tags/apply.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bind](<https://devfeed.tech/tags/bind.md>), [builds](<https://devfeed.tech/tags/builds.md>), [candidate](<https://devfeed.tech/tags/candidate.md>), [cd](<https://devfeed.tech/tags/cd.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [command](<https://devfeed.tech/tags/command.md>), [commands](<https://devfeed.tech/tags/commands.md>), [container](<https://devfeed.tech/tags/container.md>), [cpu](<https://devfeed.tech/tags/cpu.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-graph](<https://devfeed.tech/tags/dependency-graph.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [devops](<https://devfeed.tech/tags/devops.md>), [docker](<https://devfeed.tech/tags/docker.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>)

### AI overview

The article's central takeaway is that DevOps interviews test how candidates explain system behavior, failure and troubleshooting, not just commands. It illustrates this with practical walkthroughs: Kubernetes filters and scores nodes before binding Pods, and controllers reconcile desired state; Docker creates a container and configures its filesystem, networking and isolation before starting a process; Terraform uses resource dependencies to build an execution graph. Further examples cover CI/CD job dependencies, DNS and CloudFront caching, Git merge versus rebase, observability signals, and structured incident response. The material is presented as interview preparation with concepts, examples, commands, common traps and sample answers; the supplied text is excerpted.

### Source excerpt

Many DevOps engineers can run: 🐳 Docker ☸ Kubernetes 🔄 CI/CD pipelines ☁ AWS 🏗 Terraform 🌐 Networking tools And everything feels comfortable. Until the interviewer asks: "What actually happens internally?" Suddenly, knowing the command isn't enough. You may know: kubectl apply -f deployment.yaml But can you explain what happens after you press Enter? You may know: docker run nginx But what happens between that command and the container actually starting? You may know Terraform. But can you explain how Terraform builds its dependency graph and determines what should be created first? That's where DevOps interviews become much more interesting. Modern interviews increasingly test whether you understand the mechanisms behind the tools, not just their commands. For every question below, we'll use the same framework: 🧠 Simple Concept ❓ Why do we need it? ⚙ How does it work? 🏢 Production Example 💻 Command / YAML 🚨 Common Interview Trap 🎯 Candidate-Style Answer 🧠 Memory Trick Let's go underneath the surface. 📘 SECTION 1: KUBERNETES, DOCKER & TERRAFORM INTERNALS1. How does Kubernetes decide which node to schedule a Pod on?🧠 Simple Concept When you create a Pod, Kubernetes needs to decide which worker node should run it. The scheduler is responsible for this decision. It doesn't simply pick the first available node. ❓ Why do we need it? A cluster may contain: Different CPU capacities Different memory capacities Taints and tolerations Node labels Affinity rules Resource constraints Topology requirements The scheduler needs to find a node where the Pod can actually run. ⚙ How does it work? A simplified flow is: Pod Created ↓ API Server ↓ Scheduler ↓ Filter unsuitable nodes ↓ Score remaining nodes ↓ Select node ↓ Bind Pod to node ↓ Kubelet starts container The scheduler considers constraints such as requested resources and scheduling rules. 🏢 Production Example Suppose a Pod requests: resources: requests: cpu: "2" memory: "4Gi" A node that doesn't have enough allocatable r

## Monsta FTP: An SSRF Blocklist That Forgot IPv6 Exists

DevFeed: [Monsta FTP: An SSRF Blocklist That Forgot IPv6 Exists](<https://devfeed.tech/articles/monsta-ftp-an-ssrf-blocklist-that-forgot-ipv6-exists-91537.md>)

Original publisher: [Read original article](<https://www.vulncheck.com/blog/monsta-ftp-ssrf-ipv6-blocklist-bypass>)

Author: Valentin Lobstein (Chocapikk)

Published: 2026-07-14T00:00:00Z

Content type: news

Language: en

Sources: [VulnCheck](<https://devfeed.tech/sources/vulncheck.md>)

Topics: [Domain Name System (DNS)](<https://devfeed.tech/topics/dns-resolution-process.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [hosting](<https://devfeed.tech/topics/hosting.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [least privilege](<https://devfeed.tech/topics/least-privilege.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [bind](<https://devfeed.tech/tags/bind.md>), [bypass](<https://devfeed.tech/tags/bypass.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-metadata](<https://devfeed.tech/tags/cloud-metadata.md>), [cloudflare](<https://devfeed.tech/tags/cloudflare.md>), [control-plane](<https://devfeed.tech/tags/control-plane.md>), [coordinated-vulnerability-disclosure](<https://devfeed.tech/tags/coordinated-vulnerability-disclosure.md>), [ftp](<https://devfeed.tech/tags/ftp.md>), [ipv4](<https://devfeed.tech/tags/ipv4.md>), [ipv6](<https://devfeed.tech/tags/ipv6.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [ssrf](<https://devfeed.tech/tags/ssrf.md>), [vulncheck](<https://devfeed.tech/tags/vulncheck.md>)

### AI overview

Monsta FTP through 2.14.4 has an unauthenticated SSRF in `fetchRemoteFile`: its IP blocklist checks IPv4 ranges only when PHP classifies an address as IPv4, so IPv4-mapped IPv6 addresses such as `::ffff:169.254.169.254` bypass both URL validation and the post-connect recheck. An attacker can serve a static AAAA record for an internal or metadata address, have Monsta fetch it over HTTP or HTTPS, and exfiltrate the response to an attacker-controlled FTP server. The issue enables reads from cloud metadata and internal services; the text says a stock install does not provide a direct SSRF-to-shell path. The vendor silently fixed the flaw in 2.14.5. The article recommends upgrading, restricting `fetchRemoteFile` and host egress until then, and normalizing addresses before range checks, including in the connection recheck.

### Source excerpt

VulnCheck's Initial Access Intelligence team details an unauthenticated SSRF in Monsta FTP 2.14.4, where an IPv4-only blocklist waves through the IPv4-mapped IPv6 form of the cloud metadata endpoint and bypasses both the front gate and the anti-rebinding recheck.

## How JavaScript call, apply, and bind Actually Work

DevFeed: [How JavaScript call, apply, and bind Actually Work](<https://devfeed.tech/articles/how-javascript-call-apply-and-bind-actually-work-87912.md>)

Original publisher: [Read original article](<https://jsdev.space/howto/call-apply-bind/>)

Author: Anton Liberant

Published: 2026-05-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [JavaScript Development](<https://devfeed.tech/sources/javascript-development.md>)

Topics: [JavaScript](<https://devfeed.tech/topics/javascript.md>), [explicit receiver](<https://devfeed.tech/topics/explicit-receiver.md>)

Tags: [apply](<https://devfeed.tech/tags/apply.md>), [arguments](<https://devfeed.tech/tags/arguments.md>), [bind](<https://devfeed.tech/tags/bind.md>), [call](<https://devfeed.tech/tags/call.md>), [deep-dive](<https://devfeed.tech/tags/deep-dive.md>), [internals](<https://devfeed.tech/tags/internals.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [this](<https://devfeed.tech/tags/this.md>)

### AI overview

This tutorial explains how JavaScript's call, apply, and bind methods control function invocation and this binding, including simplified implementations and constructor edge cases. It also covers the arguments object, method borrowing, callback context, and the modern use of rest parameters.

### Source excerpt

Deep dive into JavaScript call, apply, bind, and arguments. Learn explicit binding, handwritten implementations, and real language internals.

## Resolving the Reverse Tunnel Remote port forwarding failed for listen port SSH Error

DevFeed: [Resolving the Reverse Tunnel Remote port forwarding failed for listen port SSH Error](<https://devfeed.tech/articles/resolving-the-reverse-tunnel-remote-port-forwarding-failed-for-listen-port-ssh-error-4517.md>)

Original publisher: [Read original article](<https://feeds.feedblitz.com/~/919939007/0/baeldung/linux~Resolving-the-Reverse-Tunnel-Remote-port-forwarding-failed-for-listen-port-SSH-Error>)

Author: Hiks Gerganov

Published: 2025-06-09T04:49:53Z

Content type: article

Language: en

Sources: [Baeldung - Linux](<https://devfeed.tech/sources/baeldung-linux.md>)

Topics: [ssh](<https://devfeed.tech/topics/ssh.md>)

Tags: [bash](<https://devfeed.tech/tags/bash.md>), [bind](<https://devfeed.tech/tags/bind.md>), [bookworm](<https://devfeed.tech/tags/bookworm.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [command](<https://devfeed.tech/tags/command.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [configure](<https://devfeed.tech/tags/configure.md>), [connectivity](<https://devfeed.tech/tags/connectivity.md>), [curl](<https://devfeed.tech/tags/curl.md>), [debian](<https://devfeed.tech/tags/debian.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [error](<https://devfeed.tech/tags/error.md>), [failed](<https://devfeed.tech/tags/failed.md>), [network-configuration](<https://devfeed.tech/tags/network-configuration.md>), [network-configuration-network-monitoring-security-ssh](<https://devfeed.tech/tags/network-configuration-network-monitoring-security-ssh.md>), [port](<https://devfeed.tech/tags/port.md>), [remote](<https://devfeed.tech/tags/remote.md>), [reverse](<https://devfeed.tech/tags/reverse.md>), [security](<https://devfeed.tech/tags/security.md>), [ssh](<https://devfeed.tech/tags/ssh.md>), [vpn](<https://devfeed.tech/tags/vpn.md>)

### AI overview

Reverse SSH forwarding uses `ssh -N -R` to expose a service reachable from a protected client through a listening port on a remote server. The `-R` value specifies the remote bind address and port, then the destination host and port reachable from the client; by default, the remote listener is loopback-only. The "remote port forwarding failed for listen port" error can result from a busy port, attempting to bind a privileged port below 1024, malformed address or port fields, an unavailable bind address or disabled forwarding in `sshd_config`, or other configuration issues. Check listeners and their IP versions on the server with `ss`, verify the forwarding syntax and port availability, and inspect `AllowTcpForwarding` and `GatewayPorts` when relevant. A working tunnel may still be unreachable externally if the port is filtered by a firewall, router, or ISP; client-side tunneling does not remove those restrictions beyond the remote server.

### Source excerpt

Learn about reverse SSH tunnels, i.e., SSH port forwarding, and issues that you might encounter when trying to use them. The post Resolving the Reverse Tunnel Remote port forwarding failed for listen port SSH Error first appeared on Baeldung on Linux. Related Stories Sending a Password via SSH or SCP Using subprocess.Popen in Linux What Is SELinux? How To Automatically Connect to a VPN in Linux

## Jetpack Compose under the hood

DevFeed: [Jetpack Compose under the hood](<https://devfeed.tech/articles/jetpack-compose-under-the-hood-25851.md>)

Original publisher: [Read original article](<https://medium.com/@banmarkovic/jetpack-compose-under-the-hood-7bb88f08c47e?source=rss-8aced922ece------2>)

Author: Ban Markovic

Published: 2022-12-12T10:49:33Z

Content type: article

Language: en

Sources: [Ban Markovic](<https://devfeed.tech/sources/stories-by-ban-markovic-on-medium.md>)

Topics: [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [Android](<https://devfeed.tech/topics/android.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [apis](<https://devfeed.tech/tags/apis.md>), [app-development](<https://devfeed.tech/tags/app-development.md>), [base](<https://devfeed.tech/tags/base.md>), [basic](<https://devfeed.tech/tags/basic.md>), [bind](<https://devfeed.tech/tags/bind.md>), [change](<https://devfeed.tech/tags/change.md>), [changes](<https://devfeed.tech/tags/changes.md>), [code](<https://devfeed.tech/tags/code.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [components](<https://devfeed.tech/tags/components.md>), [compose](<https://devfeed.tech/tags/compose.md>), [data](<https://devfeed.tech/tags/data.md>), [deprecated](<https://devfeed.tech/tags/deprecated.md>), [designers](<https://devfeed.tech/tags/designers.md>), [developers](<https://devfeed.tech/tags/developers.md>), [developing](<https://devfeed.tech/tags/developing.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>)

### AI overview

Android UI development has repeatedly changed how developers access and update XML views, from findViewById and Butter Knife through Kotlin synthetics, ViewBinding, and DataBinding. The excerpt attributes this churn to growing UX complexity and the demand for flexible, reusable code. It frames Jetpack Compose as a new system best understood by comparing it with the Android View System, and says the article will use a "Hello World" screen as a comparison example. The excerpt does not provide the Compose implementation or explain its internals.

### Source excerpt

The development of Android mobile apps is nothing new. We have been doing it since 2009, when the Android SDK was published. In the meantime, many APIs used for developing Android mobile apps were updated, but the general idea of app development remained. Looking at something as basic as accessing the UI elements and modifying them, we can see the constant need for improvement and change. We've started with findViewById, then we transferred to Butter Knife library. After we switched from Java to Kotlin, we were introduced to Kotlin synthetics, then it went deprecated soon enough, and it was replaced by ViewBinding. In the meantime, we also received a new support library, DataBinding, that enabled us to bind our UI components to data sources from our app. As we can see, even though the final goal was the same (accessing UI elements defined inside XML and modifying their values), the APIs for reaching our goal were changed quite drastically and quite often. Why so many changes? The constant need for polishing the UX of ours apps introduced a lot more complexity in our mobile app projects. Designers demand more and more from their developers, and developers constantly strive for making their code as flexible and reusable as possible. This is something that gets harder and harder to accomplish when your base is not particularly designed for handling new types of designers requirements. Motivation To better learn something new, we need to understand the differences between what we know (Android View System) and the new things that are introduced by the new system (Jetpack Compose). Sometimes this feels overwhelming, because at the beginning, most of it looks like magic as we don't know anything about it. By familiarizing ourselves with Jetpack Compose way of working, we are putting ourselves in a better position to utilize this new tool. Android View System The base for developing Android apps most of us are currently using is Android View System. It is here since 2009 a

## A brief history of select(2)

DevFeed: [A brief history of select(2)](<https://devfeed.tech/articles/a-brief-history-of-select-2-38956.md>)

Original publisher: [Read original article](<https://idea.popcount.org/2016-11-01-a-brief-history-of-select2>)

Author: Marek

Published: 2016-10-31T23:00:00Z

Content type: article

Language: en

Sources: [Marek Majkowski](<https://devfeed.tech/sources/marek-majkowski.md>)

Topics: [async](<https://devfeed.tech/topics/async.md>), [Linux](<https://devfeed.tech/topics/linux.md>), [Process](<https://devfeed.tech/topics/process.md>), [freebsd](<https://devfeed.tech/topics/freebsd.md>), [io\_uring](<https://devfeed.tech/topics/io-uring.md>), [ML model versioning](<https://devfeed.tech/topics/ml-model-versioning.md>)

Tags: [abstractions](<https://devfeed.tech/tags/abstractions.md>), [api](<https://devfeed.tech/tags/api.md>), [api-design](<https://devfeed.tech/tags/api-design.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [batch-processing](<https://devfeed.tech/tags/batch-processing.md>), [batching](<https://devfeed.tech/tags/batching.md>), [bind](<https://devfeed.tech/tags/bind.md>), [blocking](<https://devfeed.tech/tags/blocking.md>), [bsd](<https://devfeed.tech/tags/bsd.md>), [c](<https://devfeed.tech/tags/c.md>), [channel](<https://devfeed.tech/tags/channel.md>), [communication](<https://devfeed.tech/tags/communication.md>), [history](<https://devfeed.tech/tags/history.md>), [i-o](<https://devfeed.tech/tags/i-o.md>), [linux](<https://devfeed.tech/tags/linux.md>), [multiplexing](<https://devfeed.tech/tags/multiplexing.md>), [select](<https://devfeed.tech/tags/select.md>), [syscall](<https://devfeed.tech/tags/syscall.md>), [unix](<https://devfeed.tech/tags/unix.md>)

### AI overview

The article traces `select(2)` to the need to handle multiple I/O streams in one process. Early Unix programs mostly used blocking I/O, and `cu` relied on two processes to read and write concurrently. With 4.2BSD's sockets and applications such as Blit's virtual terminals, remote login clients, and later `inetd`, that model was insufficient: `select` let a program wait until a descriptor was ready, while nonblocking reads alone could require polling. The article argues that multiplexing arose from practical needs around networking, terminal work, and shared server state, rather than from a Unix design based on CSP-like channels. It also qualifies the history: Rob Pike's update says earlier Blit work used Greg Chessons' `mpx`, and notes that `select` and sockets appeared around the same time but were not necessarily designed as a single system. A later update corrects the claim that nonblocking I/O did not exist before 1983, citing earlier TTY support.

### Source excerpt

A brief history of select(2) I/O multiplexing part #1 Recently I've been thinking about the multiplexing in Linux, namely the syscall. I was curious if is better or worse than the or . I was wondering if there was a benefit in batching calls. But let's step back for a while, before we start a serious discussion we need to get some context. Most importantly - is file descriptor multiplexing an aberration or a gentle extension to the Unix design philosophy's?

## Learning Angular: Set your language culture before any UI is displayed

DevFeed: [Learning Angular: Set your language culture before any UI is displayed](<https://devfeed.tech/articles/learning-angular-set-your-language-culture-before-any-ui-is-displayed-21239.md>)

Original publisher: [Read original article](<https://juri.dev/blog/2015/03/learning-ng-angular-translate-promises/>)

Published: 2015-03-02T00:00:00Z

Content type: tutorial

Language: en

Sources: [Juri Strumpflohner](<https://devfeed.tech/sources/juri-strumpflohner.md>)

Topics: [Angular](<https://devfeed.tech/topics/angular.md>), [Learning](<https://devfeed.tech/topics/learning.md>)

Tags: [angular](<https://devfeed.tech/tags/angular.md>), [api](<https://devfeed.tech/tags/api.md>), [application](<https://devfeed.tech/tags/application.md>), [article](<https://devfeed.tech/tags/article.md>), [backend](<https://devfeed.tech/tags/backend.md>), [bind](<https://devfeed.tech/tags/bind.md>), [cache](<https://devfeed.tech/tags/cache.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [controller](<https://devfeed.tech/tags/controller.md>), [data](<https://devfeed.tech/tags/data.md>), [files](<https://devfeed.tech/tags/files.md>), [i18n](<https://devfeed.tech/tags/i18n.md>), [issue](<https://devfeed.tech/tags/issue.md>), [language](<https://devfeed.tech/tags/language.md>), [learning](<https://devfeed.tech/tags/learning.md>), [loading](<https://devfeed.tech/tags/loading.md>), [locale](<https://devfeed.tech/tags/locale.md>), [localization](<https://devfeed.tech/tags/localization.md>), [route](<https://devfeed.tech/tags/route.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

The article's practical fix is to load the current user and set their preferred language before Angular renders the UI. With angular-translate, changing languages refreshes bound translations, but localized data may not refresh correctly and can flicker or appear in the wrong locale if the language is set too late. The author uses a client-side route's promise-returning resolve function to wait for user and language setup. In the real application, the resolve is attached dynamically to routes, so backend calls should be cached to avoid repeating them on each route change; returning the user and language in an object also makes them available to a route controller.

### Source excerpt

Lorem ipsum dolor sit amet

## Bind before connect

DevFeed: [Bind before connect](<https://devfeed.tech/articles/bind-before-connect-38934.md>)

Original publisher: [Read original article](<https://idea.popcount.org/2014-04-03-bind-before-connect>)

Author: Marek

Published: 2014-04-02T22:00:00Z

Content type: article

Language: en

Sources: [Marek Majkowski](<https://devfeed.tech/sources/marek-majkowski.md>)

Topics: [Linux Kernel](<https://devfeed.tech/topics/linux-kernel.md>), [ephemeral ports](<https://devfeed.tech/topics/ephemeral-ports.md>), [Kernel](<https://devfeed.tech/topics/kernel.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [article](<https://devfeed.tech/tags/article.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [bind](<https://devfeed.tech/tags/bind.md>), [bsd](<https://devfeed.tech/tags/bsd.md>), [call](<https://devfeed.tech/tags/call.md>), [connect](<https://devfeed.tech/tags/connect.md>), [ephemeral](<https://devfeed.tech/tags/ephemeral.md>), [ip](<https://devfeed.tech/tags/ip.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [linux](<https://devfeed.tech/tags/linux.md>), [linux-kernel](<https://devfeed.tech/tags/linux-kernel.md>), [number](<https://devfeed.tech/tags/number.md>), [operating-system](<https://devfeed.tech/tags/operating-system.md>), [port](<https://devfeed.tech/tags/port.md>), [range](<https://devfeed.tech/tags/range.md>), [socket](<https://devfeed.tech/tags/socket.md>), [source](<https://devfeed.tech/tags/source.md>), [system](<https://devfeed.tech/tags/system.md>), [tcp](<https://devfeed.tech/tags/tcp.md>)

### AI overview

Linux normally selects an ephemeral source port during `connect()`, allowing the same port to serve connections to different destinations; the excerpt says more than 28,000 simultaneous connections to one destination pair will fail by default. Binding a source IP first changes allocation: without reuse, a port is effectively tied up regardless of destination. Setting `SO_REUSEADDR` permits sharing across nonconflicting connections, including cases involving established or `TIME_WAIT` sockets, but a later `connect()` can still fail with `EADDRNOTAVAIL` if the chosen port conflicts, so retry may be needed. The excerpt recommends expanding the port range and using multiple source IPs for higher connection counts, and warns that `connect()` and bind-before-connect allocations interfere with each other. It distinguishes `SO_REUSEPORT` as primarily for distributing incoming traffic among sockets. These are the article's described Linux behaviors and caveats.

### Source excerpt

Bind before connect A TCP/IP connection is identified by a four element tuple: {source IP, source port, destination IP, destination port}. To establish a TCP/IP connection only a destination IP and port number are needed, the operating system automatically selects source IP and port. This article explains how the Linux kernel does the source port allocation. Ephemeral port range To establish a connection BSD API requires two steps: first you need to create a socket, then call on it.

## Smooth image loading by upscaling

DevFeed: [Smooth image loading by upscaling](<https://devfeed.tech/articles/smooth-image-loading-by-upscaling-2141.md>)

Original publisher: [Read original article](<https://developers.soundcloud.com/blog//smooth-image-loading-by-upscaling>)

Published: 2014-02-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [SoundCloud Backstage](<https://devfeed.tech/sources/soundcloud-backstage-blog.md>)

Topics: [Image](<https://devfeed.tech/topics/image.md>), [Cache](<https://devfeed.tech/topics/cache.md>), [Single-page application (SPA)](<https://devfeed.tech/topics/spa.md>), [Web app](<https://devfeed.tech/topics/webapp.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [also](<https://devfeed.tech/tags/also.md>), [application](<https://devfeed.tech/tags/application.md>), [applications](<https://devfeed.tech/tags/applications.md>), [array](<https://devfeed.tech/tags/array.md>), [avatar](<https://devfeed.tech/tags/avatar.md>), [basic](<https://devfeed.tech/tags/basic.md>), [bind](<https://devfeed.tech/tags/bind.md>), [browser](<https://devfeed.tech/tags/browser.md>), [but](<https://devfeed.tech/tags/but.md>), [cache](<https://devfeed.tech/tags/cache.md>), [displays](<https://devfeed.tech/tags/displays.md>), [image](<https://devfeed.tech/tags/image.md>), [images](<https://devfeed.tech/tags/images.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [loading](<https://devfeed.tech/tags/loading.md>), [make](<https://devfeed.tech/tags/make.md>), [single-page-application](<https://devfeed.tech/tags/single-page-application.md>), [upscaling](<https://devfeed.tech/tags/upscaling.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

SoundCloud's image-loading technique uses a previously cached smaller image as a stretched placeholder while the requested larger image loads, then fades the larger image in. To avoid an extra HTTP request just for a brief placeholder, the code records which sizes have loaded during the session: it extracts an image identifier and size from each URL and stores size flags in an integer bitmask. When a larger image is requested, it selects the largest smaller cached size, or loads the full-size image normally if none is available. The excerpt reports a 30% memory difference between boolean arrays and integer bitmasks in one 10,000-image example, and notes that compact keys matter because keys consume much of the map's memory. Positioning and some implementation details are omitted.

### Source excerpt

The site is a single-page application that displays a multitude of users' images. At SoundCloud, we use a technique to make the loading of...