MTProto Proxies on Mobile: What They Really Cost in Battery and Data

·1 views

MTProto proxies help Telegram users bypass connectivity restrictions, but they carry measurable costs for mobile users in terms of battery life and data consumption. Frequent proxy disconnections trigger repeated reconnection cycles that drain battery, while features like Fake-TLS handshakes and voice calls routed through a proxy add further overhead. On the data side, text messaging adds only minimal extra bytes, but video autoplay combined with a high-latency proxy can cause repeated failed segment requests, potentially burning hundreds of megabytes in a single session. Android devices rely on Firebase Cloud Messaging to keep Telegram alive in the background, meaning a dropped proxy can silently halt notifications for extended periods. Users can reduce these costs by limiting media transfers to Wi-Fi, disabling cellular autoplay, and choosing stable proxy URLs over frequently rotating lists.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How Spring Boot's Convention over Configuration Cuts Java Setup Complexity

Spring Boot applies the 'Convention over Configuration' principle, which lets a framework adopt sensible defaults so developers avoid manually setting up every project detail. Before Spring Boot, building even a simple Java REST API required hundreds of lines of XML configuration covering servlets, beans, database connections, and server setup. By detecting dependencies like spring-boot-starter-web or spring-boot-starter-data-jpa, Spring Boot automatically enables the relevant components — such as Tomcat, Spring MVC, Hibernate, and JPA — without any explicit configuration. Developers only need to override defaults when their requirements differ, using a straightforward application.properties file or class-level annotations. This approach significantly reduces boilerplate code, accelerates development, and allows teams to focus on writing business logic rather than infrastructure setup.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How to Build an Accurate Codex Usage Tracker Without Outdated Data

Developers building Codex usage trackers must display the current weekly quota window, as Codex no longer exposes a previous five-hour window that some interfaces still show. Hardcoding outdated labels or preserving empty UI slots can mislead users by presenting stale data as live telemetry. When combining Claude and Codex dashboards, each provider requires its own error state and refresh timestamp, since a single shared status indicator can mask failures from either service. A local token ledger should deduplicate replayed session events and attribute usage by event timestamp rather than scan time, while unknown models must remain unpriced instead of borrowing rates from similar ones. Estimated API value derived from local logs is not equivalent to actual billing, as provider-side aggregation, price changes, and missing events prevent exact reconciliation.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

10 Python Libraries Recommended for Building AI Applications in 2026

A developer with hands-on AI workflow experience has compiled a list of ten Python libraries considered essential for building reliable AI applications in 2026. The selection prioritizes consistency and practicality over novelty, focusing on tools the author repeatedly returns to across projects. The list spans backend frameworks, data handling, and AI-specific needs, covering libraries such as FastAPI for API development, LangChain for LLM workflows, Pydantic for data validation, and ChromaDB for vector search. Supporting tools like Pandas, NumPy, SQLAlchemy, the OpenAI SDK, and Requests are also included for their roles in data preparation, numerical computing, database management, and external integrations. The guide is aimed at developers looking to reduce development time by building on a proven, well-rounded Python toolkit rather than chasing the latest frameworks.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Builds Self-Repairing AI Script That Fixes Claude Config Using Frustration Signals

A developer has created an automated weekly script that monitors their Claude Code environment for degradation by scanning conversation transcripts for frustration signals and performance issues. The shell script, scheduled every Sunday via launchd, collects five key metrics including injected file size, loaded agent count, and user frustration phrases detected in chat logs. When any metric crosses a set threshold, the system autonomously invokes Claude to repair configuration files inside the ~/.claude directory without human intervention. A July 2026 audit revealed three simultaneous failures — 99 rogue agents, a 228KB bloated CLAUDE.md, and an excessively firing Stop hook — which motivated building the self-repair loop. After each automated fix, the script independently re-measures all metrics to verify improvement, then posts a full report to a Discord channel.

0 comments Read more at DEV Community