SShortSingh.

Programming

0
ProgrammingDEV Community ·

EU AI Act, US RMF, and Sector Rules: What ML Practitioners Must Know Now

The EU AI Act, adopted in 2024, is the world's first comprehensive AI law, classifying systems into four risk tiers with fines for high-risk non-compliance reaching up to €35 million or 7% of global annual turnover. High-risk applications such as hiring tools, credit scoring, and healthcare diagnostics require conformity assessments, human oversight, and ongoing post-market monitoring registered in an EU database. In the United States, NIST's voluntary AI Risk Management Framework has become the de facto governance standard, structured around four functions: Govern, Map, Measure, and Manage. Beyond horizontal AI laws, sector-specific rules add additional obligations — including FDA oversight of medical AI, explainability requirements for credit decisions, and New York City's mandatory bias audits for automated hiring tools. Practitioners building AI in regulated domains must treat these legal frameworks as a compliance floor, not an optional checklist.

0
ProgrammingDEV Community ·

Developer builds RSS directory with MCP server to give AI tools real-time field updates

A developer has built RSS Atlas, a directory of 2,907 RSS feeds spanning 19 languages and 37 categories, to address the gap in AI tools that cannot query recent developments within a specific technical field. The project exposes its data through a Model Context Protocol (MCP) server, making it accessible to AI assistants like Claude. The builder shared four key engineering lessons learned post-launch, covering tool design, authentication handling, user identity scoping, and rate limiting. Notable decisions included collapsing a proposed fifth tool into a parameter to reduce model decision points, and returning HTTP 401 instead of a payload error to properly trigger client authentication flows. A no-authentication demo is publicly available, with the backend running on Cloudflare Workers, Supabase, and Cloud Run Jobs.

0
ProgrammingDEV Community ·

Developer Builds Bilingual Web Studio Site with AI Chat and Analytics in 5 Days

A developer named Yuriy, founder of WebStudio, built a fully functional website in five days using HTML5, vanilla JavaScript, and a Python Flask backend hosted on PythonAnywhere. The site includes an AI-powered chat feature built on Cohere's command-r model, a custom analytics tracker alongside Google Analytics and Yandex.Metrica, and bilingual support for Russian and English. A lightweight 20-line JavaScript solution handled the multilingual functionality without any frontend framework. The project resulted in 23 published blog posts, over 200 tracked visits, 103 unique IPs, and seven leads generated after deployment via GitHub Pages. Yuriy noted that vanilla JavaScript, free-tier hosting, and a content-heavy approach were sufficient to achieve meaningful early traction.

0
ProgrammingDEV Community ·

Google Search Console Now Tracks Instagram, TikTok, X and YouTube Search Performance

Google has introduced Platform Properties in Search Console, allowing account owners on Instagram, TikTok, X, and YouTube to monitor how their content appears across Google Search, Discover, and Google News. The feature was announced on July 7, 2026, with global availability confirmed on July 29. Connected accounts gain access to a Performance report with click and impression data, an Insights report highlighting traffic trends and top posts, and an Achievements panel for milestone tracking. The tool is especially useful for creators and social teams who publish primarily on video or social platforms rather than traditional websites. It gives SEO and social teams a shared reporting environment to evaluate organic search visibility for externally hosted content.

0
ProgrammingDEV Community ·

Developer Builds AI System to Unify GitHub Data Into Queryable Knowledge Graph

A developer has created an open-source AI Operating System for organizations that aggregates scattered GitHub data — including commits, pull requests, and issues — into a connected graph database. The tool allows teams to query organizational knowledge in plain language, such as identifying who modified a file or which issues were resolved in a release. Built with Python, FastAPI, Neo4j, and Docker, the system's core technical challenge was linking the GitHub API to Neo4j in a queryable structure. The project is aimed at helping teams with common pain points like onboarding new engineers and investigating incidents. The source code is publicly available on GitHub, with a live demo hosted on Netlify.

0
ProgrammingDEV Community ·

Google Play to Restrict READ_CONTACTS Permission for Android 17 Apps from Jan 2027

Google Play announced on April 15, 2026, a new Contacts Permissions policy that takes effect on January 27, 2027, affecting apps targeting Android 17 (API level 37) or higher. Under the policy, apps may only request the READ_CONTACTS permission if the Android Contact Picker cannot adequately support their core functionality. Apps that still require broad address book access must submit a Play Console declaration explaining why the picker is insufficient, with pre-review checks beginning October 27, 2026. A key limitation of the picker is that below Android 17, it grants access only to a contact's display name, omitting phone numbers, email addresses, and structured name fields. Developers using the Capacitor Contacts plugin can avoid the permission entirely by using the property option in pickContacts(), available since plugin version 8.1.0 and requiring no permission on any Android or iOS version.

0
ProgrammingDEV Community ·

One Solo Founder's Five Hard Rules for Keeping AI Agents in Check

A solo developer running multiple small apps with AI agents has outlined five strict boundaries that keep his automated setup from going off the rails. He never lets agents send anything externally, touch credentials, or perform irreversible actions like deleting data or moving money without his explicit approval. Any new automation must come with a clear hypothesis, a measurable success metric, and a planned expiry date to prevent unchecked sprawl. Agents are also barred from making judgment calls on whether work meets quality standards — that decision always stays with the human. The author argues that true leverage from AI autonomy depends not on removing limits, but on knowing precisely where to draw them.

0
ProgrammingDEV Community ·

Tailscale Traced 19 Database Corruptions Over 6 Months to a 16-Year-Old SQLite Bug

Tailscale engineer Alex Chan published a postmortem detailing how the company's control plane suffered 19 separate SQLite database corruption incidents over six months, causing repeated downtime for affected tailnet shards. Each shard runs a single Go process with exclusive access to its SQLite database, a design that made the recurring corruption especially puzzling. Early incidents each required over an hour of recovery time, during which users on affected shards lost access to the admin console and API. After months of forensic investigation with no reproducible cause, the team traced the fault to a bug that had existed within SQLite itself for at least 16 years. The postmortem has drawn significant attention in the developer community for its methodical debugging approach, which its author argues is applicable to any team running relational databases in production.

0
ProgrammingDEV Community ·

Go developer releases open-source distributed rate limiter with zero memory allocation

A software developer has released distlimit, an open-source distributed rate-limiting library for Go, designed to address performance and reliability gaps in existing solutions. The library achieves sub-100 nanosecond evaluation speeds by eliminating heap memory allocations during request processing. To reduce lock contention, it splits in-memory data across 64 independent shards using FNV-1a hashing, enabling up to 64x higher concurrent throughput compared to single-mutex designs. The library includes a hybrid Redis-plus-memory fallback system with a circuit breaker to prevent service crashes or thundering herd spikes during Redis outages. Security features include CIDR-validated proxy trust rules to guard against IP spoofing via manipulated forwarding headers.

0
ProgrammingDEV Community ·

Why DNS Changes Don't Update Instantly: The Role of Caching and TTL

When a DNS record is updated, the change does not instantly reflect across the internet because millions of systems rely on cached DNS information. DNS is stored in multiple layers of cache, including browsers, operating systems, routers, ISPs, and recursive resolvers like Google's 8.8.8.8 and Cloudflare's 1.1.1.1. There is no global mechanism that pushes DNS updates to every network simultaneously; instead, old cached answers simply expire before resolvers fetch the new ones. The delay most users experience during so-called 'DNS propagation' is therefore a caching problem, not a distribution problem. Three key concepts — DNS cache, TTL (Time to Live), and recursive resolvers — determine how long outdated DNS answers persist across the internet.

0
ProgrammingHacker News ·

Mozilla warns strict Google antitrust remedies could defund and kill Firefox

Mozilla has cautioned that aggressive antitrust measures targeting Google could pose an existential threat to Firefox. The browser's development is heavily funded by a revenue-sharing deal with Google, which pays Mozilla to remain the default search engine in Firefox. If regulators force Google to abandon such agreements as part of antitrust remedies, Mozilla warns it could lose its primary source of income. This financial dependency means that actions intended to curb Google's dominance could inadvertently harm one of the few remaining independent browser makers. Mozilla is urging regulators to consider the broader ecosystem impact before imposing sweeping restrictions on Google's search partnerships.

0
ProgrammingHacker News ·

GoAccess: Open-Source Tool for Real-Time Web Log Analysis

GoAccess is an open-source web log analyzer that provides real-time data processing and an interactive viewer interface. The tool is designed to help developers and system administrators monitor and analyze server access logs efficiently. It can be run directly in a terminal or generate visual HTML reports for browser-based viewing. GoAccess supports multiple log formats, making it versatile across different web server environments.

0
ProgrammingDEV Community ·

Developer details how to build Universal 2 libraries for Qt macOS apps on Apple Silicon

A developer building a Qt-based macOS application faced a significant dependency challenge when transitioning from an Intel Mac to Apple Silicon. The application needed to run natively on both x86_64 and ARM64 architectures, requiring a Universal 2 binary approach. Simply recompiling the app was insufficient, as every third-party library in the entire dependency chain also had to support both architectures. The developer rebuilt each library separately for each architecture and merged them using Apple's lipo tool to produce universal binaries. The process revealed that even nested dependencies, along with Qt itself, had to be rebuilt to avoid ARM64 build or runtime failures.

0
ProgrammingDEV Community ·

Hybrid Retrieval with BM25 and Reranker Outperforms Dense-Only Search on Technical Docs

A developer building a retrieval layer for a personal wiki found that dense-only vector search consistently failed to surface exact matches for technical identifiers like config keys, error strings, and CLI flags. On a 10-query evaluation set, dense-only retrieval placed the correct article in the top three results for just 5 queries, while a hybrid approach combining Qwen embeddings, BM25, and Reciprocal Rank Fusion (RRF) with a reranker improved that score to 8. Attempts to fix the problem by upgrading to a larger embedding model or using LLM-based query expansion yielded minimal gains while adding latency and non-determinism. Serving a cross-encoder reranker through Ollama produced silently incorrect relevance scores, because GGUF conversion strips the classification head the model relies on for ranking. The author concludes that technical corpora require lexical retrieval alongside semantic search, as embedding models are structurally unable to treat exact identifiers as discriminative tokens.

0
ProgrammingDEV Community ·

How Enterprises Can Build Reliable AI Agentic Workflows With Proper Controls

Agentic workflows, where AI systems execute multi-step tasks rather than responding to single prompts, are gaining traction as an enterprise automation approach. Unlike simple AI features, these workflows combine instructions, business data, tools, and human approval steps to move structured work forward. Experts recommend starting with a narrow, well-defined process that has a clear owner, a known bottleneck, and a measurable outcome, rather than broad mandates like automating entire departments. Governance must be embedded within the workflow itself, covering data access, identity management, human escalation, and incident response before any pilot scales to critical operations. Return on investment should be evaluated against a documented baseline, with oversight levels calibrated to the potential business impact of each workflow.

0
ProgrammingDEV Community ·

Developer builds SQL-based Supabase RLS audit tool that bypasses AI guesswork

A developer has created a structured audit tool for Supabase Row Level Security (RLS) that relies on direct SQL queries rather than asking AI agents to infer security configurations. The tool queries Postgres catalogue views such as pg_tables and pg_policies to surface concrete issues including tables with no RLS, overly permissive policies, public storage buckets, and tables with RLS enabled but no attached policy. Unlike typical AI-assisted audits, the prompt instructs the model only to run a fixed SQL block and report results, ensuring findings are grounded in actual database state. The tool is designed to be pasted into AI coding environments like Claude Code or Cursor and runs against a live Supabase project in around thirty seconds at no cost. The developer noted that all detected issues can silently reappear after migrations or ad-hoc fixes, which motivated building a broader monitoring product called Defencecore to track catalogue changes over time.

0
ProgrammingDEV Community ·

Aux Battles runs multiplayer music game using Postgres as sole state machine

Aux Battles is a free, browser-based multiplayer music game that operates without a dedicated game server. Instead, all game state — rooms, players, prompts, and voting — is synchronized across clients via Supabase Realtime, which streams live Postgres database changes. Every player action is handled as a direct table write, with a single phase column on each room row driving the game's progression. Host-only controls are enforced at the UI level rather than through row-level security, keeping the architecture simple for a no-login game. The most complex feature was a Twitch-style 64-song knockout bracket, stored in a single JSONB column and protected against race conditions using a compare-and-set sequence token.

0
ProgrammingDEV Community ·

MemoryDesk: Open-Source Agent That Retains Customer Support Memory

MemoryDesk is an open-source customer support agent project hosted on GitHub by developer THRISHANTH222. The project focuses on building AI agents capable of persistent memory across conversations. Its core architectural principle treats memory as a standalone, modular capability rather than embedding it within individual chat sessions. This design allows the agent to recall past interactions without being constrained by single-conversation context limits. The project is available publicly for developers to explore and contribute to.

0
ProgrammingDEV Community ·

Self-Hosted vs SaaS Support AI: What EU E-Commerce Shops Need to Know

Businesses running customer support AI can either use a hosted solution like Intercom's Fin or deploy a self-hosted agent on infrastructure they control, with the core difference being architectural. For EU-based shops, self-hosting means customer data stays within a chosen region and jurisdiction, making data-residency compliance straightforward and independent of third-party sub-processors. On the cost side, hosted tools typically charge per resolved ticket — tying support expenses directly to sales volume — while self-hosted setups use fixed monthly instance costs and measurable, cappable inference fees. Self-hosting also avoids vendor lock-in, since the knowledge base, conversation logs, and automation logic remain portable and operational even if the setup partner changes. However, the trade-off is real: teams must own operations including monitoring, model updates, and incident response, which may not suit smaller teams without dedicated technical resources.

← NewerPage 14 of 1192Older →