Six JavaScript Checks That Reveal How Much Your Browser Leaks

·4 views

A developer has demonstrated that browser privacy can be assessed using just 30 lines of native JavaScript, without relying on any third-party tools. The self-built checker runs six key tests covering HTTPS status, cookie settings, local storage, Do Not Track signals, incognito mode detection, and browser identification. Each check contributes to a score out of 100, with HTTPS and Do Not Track weighted more heavily due to their real-world privacy impact. The tool returns a verdict alongside a personalized list of recommended fixes based on the results. The developer is also exploring additions such as WebRTC leak detection, canvas fingerprinting scores, and third-party cookie isolation checks.

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)

Ownership in software development means solving problems end-to-end, not just shipping code

A senior developer argues that true ownership in tech goes far beyond writing code and opening a pull request. The article outlines a seven-step framework — from understanding the real problem and designing solutions before coding, to verifying in production, communicating, and following up. The author reflects on years of closing tasks without actually resolving underlying issues, realizing that only 30% of the work is code. A key distinction is drawn between a problem (e.g., an 8-second search query) and a solution (e.g., migrating databases), urging developers to explore all options before building. Mastering this end-to-end responsibility is described as the real path to becoming a senior developer, rather than simply accumulating years of experience.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How ICD-10 Codes Are Converted Into Medicare Advantage RAF Scores

In Medicare Advantage risk adjustment, ICD-10-CM diagnosis codes do not carry individual risk scores — they must first be mapped to Hierarchical Condition Categories (HCCs) before a Risk Adjustment Factor (RAF) score can be calculated. The process involves applying a hierarchy rule that retains only the most severe HCC within a disease family, preventing double-counting of related conditions. The final RAF score combines a demographic factor, coefficients for each surviving HCC, and interaction terms for specific disease combinations. Critically, CMS updates the HCC maps and coefficients annually, meaning the same set of diagnosis codes can produce different scores depending on which model version — such as V24 or V28 — is applied. Implementers are advised to always validate their crosswalk tables against the current CMS Rate Announcement to avoid scoring errors.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer adds tests to PowerShell VM script after spotting one-character logic risk

A developer maintaining a PowerShell script that automates Fedora and other Linux VM builds in VirtualBox discovered a subtle fragility in its state-checking function. The function uses VBoxManage to detect when a VM has powered off, relying on a wildcard filter to isolate the VMState field from the machine-readable output. A single equals sign in the pattern 'VMState=*' prevents it from accidentally matching VMStateChangeTime, a similarly named field that appears in the same output. Had the filter been written as 'VMState*', the function could have returned a timestamp instead of a state value, silently stalling the install loop for up to 90 minutes. No bug was found, but the developer wrote six unit tests to formally document and protect the assumption going forward.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Developer shares practical lessons for building reliable CI/CD pipelines

A software developer on DEV Community detailed their journey from unreliable, ad-hoc build scripts to structured, dependable CI/CD pipelines. Early attempts using shell scripts and cron jobs frequently failed silently, with missing environment variables and broken artifacts going undetected despite green status checks. The turning point came when the developer began treating pipelines as state machines, guided by three core principles: idempotency, fast and loud failure, and environment parity with production. Using GitHub Actions and GitLab CI as examples, they highlighted common pitfalls such as missing dependency caching, unspecified Node versions, and tests running after failed builds. The article provides before-and-after pipeline configurations for a Node.js service, demonstrating how small structural changes can significantly improve reliability and developer confidence.

0 comments Read more at DEV Community