8000 [pull] main from jason5ng32:main by pull[bot] · Pull Request #24 · comanche2008/MyIP · GitHub
[go: up one dir, main page]

Skip to content

[pull] main from jason5ng32:main - #24

Merged
pull[bot] merged 82 commits into
comanche2008:mainfrom
jason5ng32:main
Jul 13, 2026
Merged

pull[bot] merged 82 commits into
comanche2008:mainfrom
jason5ng32:main

Conversation

@pull
@pull pull Bot commented Jul 13, 2026 •
Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

jason5ng32 and others added 30 commits July 8, 2026 11:54
allIPs previously held only { ip, country }, which was enough for the
Globalping picker but not for the upcoming local IP-history record. Entries
now carry location / asn / org display strings, back-filled per field the
same way country already was. IpInfos pushes full card details, WebRTC and
RuleTest push their MaxMind lookups (use-maxmind now surfaces the ASN the
API already returned), and SpeedTest's egress IP now feeds the store too.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Records every IP the app detects (store.allIPs) into localStorage, grouped
by local day with per-day dedupe and 90-day retention — browser-local only,
never synced to the account. A new FAB between InfoMask and QueryIP (and
the H shortcut) opens a left sheet listing each day's IPs with flag,
location and ASN; IPs respect the InfoMask blur and clear-all needs a
second confirming click. Pure grouping/pruning logic lives in
utils/ip-history.js with unit tests. Button gains a success variant for
the FAB, and IpDetailPanel's ASN-history icon moves to FolderClock so the
History icon unambiguously means IP history.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Lets users turn the IP-history recorder off entirely and pick how long
records are kept (1-90 days, slider to avoid free-form input). The slider
only commits the preference on release — writing during the drag would
prune history through every intermediate low value, which is irreversible.
Disabling hides the FAB, deadens the H shortcut and stops recording, but
deliberately keeps existing records: deletion stays an explicit user
action in the panel.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Three stacked FABs cover too much content on phones. On mobile the stack
now shows through page load, then (2s after the InfoMask button appears,
so it gets seen) tucks into a single ellipsis toggle. Tapping it expands
the stack and turns the toggle into an X; tapping any action or the X
collapses again. While collapsed, a green dot on the toggle mirrors the
active InfoMask state. Buttons are v-show-hidden, never unmounted, so the
teleported Dialog/Sheet overlays keep working. Desktop is unchanged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The three FABs each had their own color with no meaning behind it, and the
collapsed-dock dot introduced a fourth. Colors now follow one rule: action
blue = trigger (QueryIP), neutral = stateless panel entries (IPHistory)
and inactive toggles, success green = a protective state currently active
(InfoMask while masking; the dock dot reuses the same green). The mask
toggle toast follows suit — success on hide, warning on reveal — with the
redundant first sentence dropped from its copy. Spec documented in
frontend/AGENTS.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Achievement triggers were inlined in 10 components, each repeating the
signed-in + already-achieved boilerplate — finding "what unlocks X" meant
grepping the whole tree. Components now emit domain events on a tiny
pub/sub bus (utils/app-events.js); the trigger conditions live in one
flat rule table (data/achievement-rules.js); and a single engine
(composables/use-achievement-engine.js, initialized in App.vue) owns the
cross-cutting guards plus the 2s-spaced dispatch queue that SpeedTest
previously hand-rolled.

Behavior notes: multiple qualifying achievements now all unlock (queued
2s apart) instead of one-per-interaction (SecurityChecklist's else-if
chain), and events are emitted unconditionally — the engine filters
signed-out sessions uniformly.

Rules, engine, and bus are unit-tested (+29 specs); frontend/AGENTS.md
documents the new "achievements are event-driven" convention.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ayNames

The 1200-line four-language country table carried stale and outright wrong
entries (notably the French column) and covered only ~180 of the ISO 3166
codes real traffic produces. getCountryName(abbr, lang) keeps its signature
but now resolves via the runtime's CLDR data with a per-locale instance
cache: full code coverage, every locale, zero bundle weight.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
utils/country-name, utils/speedtest-colos, utils/masked-info and
utils/use-analytics no longer exist at those paths, so the manual chunk
entries pointing at them were dead config.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The history panel gains flat toggle-tag filters: an IPv4/IPv6 row and a
country row (flag + localized name + count). Tags combine freely — values
OR within a row, the rows AND — with an empty-result state for impossible
combos and auto-cleanup of selections whose records expired. Each row only
appears once it can actually narrow the list.

Filtering lives in pure helpers (countryFacets / ipVersionCounts /
filterHistoryDays) in utils/ip-history.js, unit-tested. The codebase-wide
"v6 has a colon" idiom is formalized as isIPv6() in common/valid-ip.js.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Stock shadcn's data-[state=on]:bg-accent is nearly invisible against the
resting background in light mode. The pressed state now uses the primary
pair (+ border-primary on the outline variant) so every ToggleGroup consumer
(DnsResolver, SecurityChecklist, Preferences, IPHistory) reads clearly
on/off. Documented as a deliberate deviation in frontend/AGENTS.md.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ated end to end

Frontend (@sentry/vue, loaded via build-time-gated dynamic import — no
VITE_SENTRY_DSN_FRONTEND, no Sentry in the bundle; init joins the mount
gate so instrumentation precedes the first render):
- uncaught errors, route-change tracing / Web Vitals, error-only masked
  Session Replay, console.error capture fingerprinted per message prefix
  so each fallback source stays a distinct issue
- explicit ip-source:exhausted signal via the app-events bus
- hidden source maps uploaded (then deleted) by @sentry/vite-plugin,
  gated on SENTRY_AUTH_TOKEN

Backend (@sentry/node, bootstrapped by sentry-instrument.js via
node --import so ESM loader hooks land before express; never loaded
without SENTRY_DSN_BACKEND):
- Express error capture + per-route tracing
- logger hook mirrors warn+ lines to Sentry Logs and elevates error+
  to grouped, alertable Issues
- Sentry Crons check-ins for the MaxMind / CAIDA / service-status jobs
  via the no-op-without-DSN wrapper common/sentry-cron.js

Delivery & ops:
- first-party tunnel /api/monitoring relays envelopes past ad blockers;
  DSN-allowlisted (never an open relay), exempt from the shared rate
  limiter with its own generous ceiling
- rate-limit ledger file becomes opt-in now that the warn line reaches
  Sentry Logs; ecosystem.config.cjs carries the --import flag for pm2

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Sentry sections cover the gating philosophy (no DSN, nothing ships or
loads), the two frontend rules (never import Sentry in app code;
explicit signals ride the app-events bus) and the backend split
(warn+ to Logs, error+ to Issues, Crons via sentry-cron).

The slim-down removes what code already expresses: tutorial-style
snippets become one-line rules pointing at exemplar components, and
per-file directory trees drop to directory level (file headers are the
per-file source of truth). Also fixes a stale claim — the router has
been on HTML5 history mode, not hash mode. 38 KB → 19 KB total.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…policy

New telemetry section in all four locales, rendered only on deployments
actually built with a Sentry DSN — self-hosted, Sentry-free copies keep
an accurate policy. States exactly what our config does: error reports,
performance timings, masked error-replays; no IP attached, first-party
relay, no third-party sharing, short retention.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…y visitors

Production immediately showed the dominant frontend noise: visitors
without an IPv6 stack fail every v6 source fetch, flooding Issues with
'TypeError: Failed to fetch' that reflects the visitor's network, not a
defect. beforeSend now drops console events from the pure-v6 chains
(also sparing the error-replay uploads they used to trigger).

Prerequisite message disambiguation: several v6 sources logged the
exact same prefixes as their v4 counterparts (Cloudflare, IPify,
MyExternalIP), which merged v4/v6 into one fingerprint group; all
pure-v6 prefixes now carry 'IPv6'. The dual-stack source logs 'IPv6/4'
and is exempt from the drop — it must succeed even for IPv4-only
visitors, so its failures stay a real signal.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…e privacy policy

Debugging network-specific reports needs the visitor's network context,
and on this site that context is literally the page: IPs, ASN and DNS
details are what the UI renders. Instead of collecting IPs into event
data (which the tunnel would misattribute to the relay anyway), the
error-only Session Replay now keeps page text and media unmasked — the
on-screen state is the debugging signal. Typed input stays masked, and
event data still carries no IP (sendDefaultPii stays false).

Privacy policy telemetry section updated in all four locales to state
exactly that: replays show the page as the visitor saw it, input stays
masked, and nothing beyond what is visible there attaches their IP.
frontend/AGENTS.md records both this and the v6 drop convention.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Privacy-hardened browsers (Firefox with media.peerconnection.enabled
off, some WebViews) have no RTCPeerConnection at all. The test used to
throw four times and paint every card as a red 'Connection Error' —
wrong twice over, since for a leak test a browser without WebRTC is the
protected outcome. checkAllWebRTC now feature-detects up front and gives
all cards a dedicated 'WebRTC Unavailable' state in green (the InfoMask
protective-state color), detail fields render as em-dashes, and the new
label joins the info-mask non-sensitive whitelist. All four locales.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
jason5ng32 and others added 26 commits July 13, 2026 09:14
Cloudflare Radar outages return HTML error pages; parsing them as JSON
raised a misleading SyntaxError instead of naming the upstream status.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Without the script no probe data ever reaches the server, so polling
just made users wait ~40s for a generic fetch error. Surface a
dedicated message immediately instead (all four locales).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The signal only ever fired for visitors whose networks block every
third-party request — nothing actionable on our side. The domain event
stays on the bus for future subscribers.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…d one is gone

A concurrent card's failure can disable the preferred geo source (or a
stale stored preference can name a removed one); findIndex then returned
-1 and sources[-1] crashed the whole retry chain.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The message embeds the queried IP, so every IP minted a fresh issue, and
the event only restates the per-source failures logged right before it —
visitor connectivity or an edge-side block, nothing actionable.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Same guard cf-radar already has: gateway/outage pages come back as
HTML, so a 502 must surface as a status error, not a SyntaxError
from JSON.parse.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Privacy extensions can replace RTCPeerConnection with a stub that
passes the typeof check but throws "not a constructor" on new —
same protective state as NotAllowedError, not an error.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…metry

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@pull pull Bot locked and limited conversation to collaborators Jul 13, 2026
@pull pull Bot added the ⤵️ pull label Jul 13, 2026
@pull
pull Bot merged commit 419f730 into comanche2008:main Jul 13, 2026
1 check passed

This branch had an error being deployed

1 failed deployment
production — 419f730c Deployed Jul 13, 2026 by pull[bot] via Push README to Docker Hub #6
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0