SShortSingh.
Back to feed

Phone photos can leak GPS location; stripping EXIF data in the browser before upload

0
·1 views

Most smartphone photos embed EXIF metadata that can include camera details, timestamps, and exact GPS coordinates. Large platforms typically remove this data on upload, but personal apps, small forums, file-sharing links, and email attachments often do not. The article suggests that developers accepting user photos can strip this metadata on the user's device before transmission. Two browser-based approaches are described: re-encoding the image through a canvas, which discards metadata but may slightly reduce JPEG quality and drop colour profiles, and removing the APP1 segment from JPEG files, which preserves the image data. The author also recommends stripping metadata on the server, since client-side protection can be bypassed by calling an API directly.

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)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Validating event counts before plotting a clinical evidence table

A percentage alone does not reveal the denominator, so an extraction row should keep the event count, participant total, study arm and an exact source location. The article offers a small dependency-free Python validator that uses synthetic teaching data and rejects booleans, non-integers, impossible counts, zero denominators and missing source locators. It does not infer missing values or back-calculate counts from rounded percentages. The example's valid rows yield proportions of 0.1 and 0.3, and its negative cases confirm that invalid rows are refused. The author stresses that passing these structural checks does not confirm the copied numbers, the randomized population or outcome comparability, and that recurrent-event data needs a different schema.

0
ProgrammingDEV Community ·

Why ATS Systems Miss Your Resume Without Exact Job Keywords

Many job seekers assume general phrases like "frontend development" are enough to qualify for a role, but applicant tracking systems match resumes against the literal skills in a job description. If a posting asks for React or TypeScript and the resume only uses broad terms, the system may give no credit for those skills, lowering the candidate's ranking. Recruiters also skim resumes quickly and look for specific tools they recognize, so vague category labels can make qualified applicants appear generic. The recommended fix is to identify each hard skill and tool in the posting and include the matching terms verbatim where they truly apply, often with both full names and abbreviations. Targeted edits to the headline, skills section, and a few bullet points are usually enough, without padding the resume with unrelated buzzwords.

0
ProgrammingDEV Community ·

Nearly 3,000 US Companies Hiring 113,000 Open Roles, Led by Healthcare

A scan of public job feeds from thousands of company career sites counted 113,287 open US roles across 2,991 companies as of 19 November 2026. About 79,500 of those positions were posted in the last 30 days, and 12,142 are remote. Healthcare and care work dominate the list, with home health, therapy, autism care, veterinary and hospital systems accounting for seven of the top 15 hirers. Defense and space firms such as SpaceX and Anduril also have more than 1,000 open US roles each. Roughly 48% of hiring companies show salary ranges in at least one job posting.

0
ProgrammingDEV Community ·

Node.js Brotli decoder flaw CVE-2026-111497: upgrade runtimes and verify running processes

A memory corruption vulnerability, CVE-2026-111497, affects the native Brotli decoder used by Node.js's node:zlib module. Attacker-controlled Brotli input can corrupt memory, putting any 22.x, 24.x or 26.x service that decompresses external Brotli data at risk. Fixed releases are 22.23.4, 24.22.1 and 26.12.1, with 22.23.5, 24.22.3 and 26.13.1 recommended as the 2026-11-11 security builds. Version 20.x and older receive no fix because they have reached end of life. Operators are advised to inspect runtime versions from inside each serving process, since commands run from a shell may not reflect what is actually executing, and then restart services to load the patched binaries.