- The provider card now shows the address block your connection belongs to, as the RIPE Database names it, for example "MOBILE-USERS-BLOCK (IT)" on Iliad mobile or "FASTWEB-L3-PAT_NAT (IT)" on a Fastweb shared address. The path shows it under your provider too. - No block is left out: the server keeps every block in the RIPE Database, small and unique ones included, and tells the app the block of the address it sees, never anyone else's. The app also carries about 430,000 of the larger blocks, for when the server can't be reached. - Only each block's range, name and country are used, nothing about people. The data comes from the RIPE NCC's RIPE Database, used with the RIPE NCC's permission; it may lag behind the live database, and the "What this app contacts" sheet gives its date. - The privacy page says that the server's answer now includes that block name; nothing new is stored or sent. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_012CzABvBkbcFqoHdmi8b9WB
17 lines
584 B
Bash
Executable File
17 lines
584 B
Bash
Executable File
#!/bin/sh
|
|
set -eu
|
|
manifest=http://127.0.0.1:5480/api/knowledge
|
|
for attempt in $(seq 1 240); do
|
|
body=$(curl -fsS "$manifest" 2>/dev/null || true)
|
|
missing=""
|
|
for file in ip2asn.bin networks.bin carriers.json registry.bin; do
|
|
case "$body" in *"\"$file\""*) ;; *) missing="$missing $file" ;; esac
|
|
done
|
|
if [ -n "$body" ] && [ -z "$missing" ]; then
|
|
echo "network data ready: $(printf '%s' "$body" | head -c 200)"
|
|
exit 0
|
|
fi
|
|
sleep 10
|
|
done
|
|
echo "::warning::the server's network data still lacks${missing:- everything} after forty minutes; the apps embed what it has"
|