Developer Launches Real-Time Train Tracker for Pakistan Railways

·3 views

A developer has built Pakistan Live Train Tracker, a web platform providing real-time train status updates across Pakistan Railways. The tool offers live delay and arrival tracking, along with route and schedule lookup features. It is designed to be mobile-friendly for travelers commuting between cities. The platform is built using Python, FastAPI, React, and TypeScript, with PostgreSQL and Redis for data storage and AWS and Cloudflare for infrastructure. It is currently live at trains.metro-status.com.

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)

Ethereum sandwich attacks can now be proven on-chain using Creditcoin's index41

Ethereum transaction receipts record block number, gas used, and logs, but do not store a transaction's position within a block, making it impossible to cryptographically prove the order transactions executed. This gap allows sandwich attacks — where a searcher places trades around a victim's swap — to be observable yet legally unprovable on-chain. A new smart contract called index41, deployed on Creditcoin, addresses this by leveraging Creditcoin's Attestcoin Protocol to verify Ethereum transaction inclusion via Merkle proofs and derive transaction order from proof geometry. By reading the left-or-right child flags at each step of a Merkle authentication path, the contract reconstructs a transaction's index within the block without that index ever being explicitly stored. When a sandwich is proven, index41 can compensate the victim from a bond, turning an observable but unverifiable event into an enforceable on-chain claim.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How .NET 10 and Apache Kafka Power Resilient Fintech Microservices

A technical guide published on DEV Community outlines how fintech systems can overcome synchronous architecture bottlenecks using event-driven design with Apache Kafka and .NET 10. Traditional tightly coupled service communication in fintech creates risks including cascading failures, thread pool exhaustion, and transactional inconsistency during high-traffic periods. The proposed solution decouples services by publishing financial events — such as credit application submissions — to Kafka topics, allowing downstream services like risk, compliance, and notifications to process them asynchronously. This approach ensures data durability and system availability even when individual services experience latency or downtime. The article also provides concrete implementation code, including an idempotent Kafka producer configured to await acknowledgment from all in-sync replicas before confirming message delivery.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer Test Reveals Gaps in AI Shopping Agents Before Price Comparisons

A developer at WebAZ ran a read-only test on September 7, 2026, querying tissue products available in Singapore to evaluate how a shopping agent handles price comparisons. The test returned three listings, including an under-cabinet organizer, highlighting that text-based relevance alone can surface non-substitute items alongside genuine product matches. Results also showed that a listing's starting price does not confirm which product variant it applies to, making per-unit cost calculations unreliable without selecting a specific option first. Additionally, the search response provided no final shipping or tax totals, meaning the cheapest listed price cannot be treated as the cheapest delivered price. The developer outlined a manual checklist of verification steps an AI agent should complete before ranking products by cost, and is offering a limited free product-clarity review for merchants and developers.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Sofka: The Rust-Built Kubernetes TUI That Treats All Resources Generically

Sofka is an open-source Kubernetes terminal UI written in Rust by developer nklmilojevic, built on the kube-rs and ratatui libraries with an asynchronous execution model. Its core design choice is to avoid creating separate renderers and state models for each Kubernetes resource type, instead routing all objects — including custom resource definitions — through a shared generic pipeline. This approach addresses the combinatorial complexity of the Kubernetes API, where supporting each new resource kind traditionally requires duplicated code for sorting, status extraction, watch updates, and detail views. Common resource types like pods and deployments still receive curated column displays, while unfamiliar or operator-defined CRDs are handled immediately through the same generic path. The design aims to decouple cluster visibility from release velocity, preventing the tool from becoming a maintenance burden as production clusters grow in API diversity.

0 comments Read more at DEV Community