"me-web?" 0.11.0: the name of the block your address belongs to

- 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

src/MeWeb.App/Strings/en.json

@@ -84,6 +84,8 @@
   "FactAdapter": "Network adapter",
   "FactAddressesSeen": "Public IPv4 addresses seen",
   "FactBattery": "Battery",
+  "FactBlock": "Address block",
+  "FactBlockIpv6": "Address block for IPv6",
   "FactChecks": "Checks",
   "FactCores": "Processor cores",
   "FactDisk": "Free disk",
@@ -259,6 +261,7 @@
   "RefusalTooMany": "too many tests for now",
   "RefusalUnknownTicket": "the test expired",
   "RefusalUnreachable": "server not reachable",
+  "RegistryCredit": "Address blocks: the RIPE NCC's RIPE Database (ripe.net), used with its permission, data of {0}. It may lag behind the live database.",
   "ResultsTitle": "What “me-web?” found",
   "RouterMobile": "On mobile data there is no home router: your provider's network comes first.",
   "RouterNone": "No home router was found on this connection.",