mirror of
https://github.com/planetrenox/inzerosight.git
synced 2026-09-18 10:05:44 +00:00
Release extension 3.2.0 with ZWUS-7 and large text support
This commit is contained in:
@@ -24,6 +24,7 @@ All operations performed by inØsight—including text encoding, decoding, encry
|
||||
inØsight requests permissions only to function as intended:
|
||||
|
||||
- **Web Page Content (`<all_urls>`):** Used strictly to scan text nodes in the Document Object Model (DOM) for inØsight zero-width Unicode signatures so the local on-screen decode/decrypt button can be displayed. No page content, personal details, or browsing activity is tracked, logged, or recorded.
|
||||
- **Clipboard (`clipboardWrite`):** Used to copy encoded text when requested in the popup. Clipboard contents are processed locally and are not transmitted.
|
||||
|
||||
## 4. Third-Party Disclosures
|
||||
|
||||
|
||||
33
docs/zwus.md
33
docs/zwus.md
@@ -4,20 +4,36 @@ Choosing the right ZWUS base involves balancing **payload size** against **platf
|
||||
|
||||
## Choosing the Optimal Base
|
||||
|
||||
- **Higher Bases (e.g. ZWUS-8):**
|
||||
You generally want to use the highest standard possible because higher bases encode more data per character, resulting in significantly more compact zero-width payloads and smaller storage footprints.
|
||||
- **ZWUS-7:**
|
||||
Ranks printable ASCII characters by frequency so common English letters and spaces use short values. It is the default for casual text.
|
||||
|
||||
- **Compatibility Trade-off:**
|
||||
The higher the base, the larger the alphabet of zero-width Unicode characters required. Certain messaging apps, web services, or platforms may strip, sanitize, or fail to hide some of these characters properly (sometimes rendering visible space or placeholder boxes). If a platform alters or rejects certain characters, lower bases like **ZWUS-6** or **ZWUS-3** offer higher compatibility by restricting the alphabet to a smaller, safer subset of zero-width characters.
|
||||
|
||||
> **Developer Advice:**
|
||||
> - **ZWUS-8:** Only pick ZWUS-8 if you are using lots of Asian or non-standard Unicode characters (where high code points benefit most from base-8 compression).
|
||||
> - **ZWUS-6:** The sweet spot for English text if the target website or platform supports it.
|
||||
> - **ZWUS-7:** Use it for compact everyday English text.
|
||||
> - **ZWUS-6:** Use it when a platform does not preserve ZWUS-7's additional character.
|
||||
> - **ZWUS-3:** Only use ZWUS-3 if you want to be as safe as possible across strict platforms.
|
||||
|
||||
## Why ZWUS-7 Is Smaller
|
||||
|
||||
ZWUS-6 writes each character's Unicode code point in base 6. For example, `t` is code point 116, which needs three base-6 digits. ZWUS-7 first assigns short numbers to printable ASCII characters in an order chosen for ordinary English text, then writes those numbers in base 7:
|
||||
|
||||
| Character | ZWUS-6 value | ZWUS-6 digits | ZWUS-7 rank | ZWUS-7 digits |
|
||||
| :--- | ---: | ---: | ---: | ---: |
|
||||
| `t` | 116 | 3 | 0 | 1 |
|
||||
| `e` | 101 | 3 | 1 | 1 |
|
||||
| space | 32 | 2 | 2 | 1 |
|
||||
| `a` | 97 | 3 | 3 | 1 |
|
||||
| `s` | 115 | 3 | 7 | 2 |
|
||||
|
||||
Ranks 0–6 fit in one zero-width digit; ranks 7–48 fit in two. All lowercase English letters fit in one or two digits, as do the decimal digits. Each encoded character is separated by one zero-width unifier in either standard, so shorter values directly reduce the payload length. ZWUS-7 adds `U+FEFF` as a seventh digit, but the frequency ranking is responsible for most of the saving.
|
||||
|
||||
For example, encoding `hello world` without a signature produces **42 zero-width characters with ZWUS-6** and **28 with ZWUS-7**: one third fewer characters. The count includes separators and measures characters, not UTF-8 bytes. The exact saving depends on the text. Rare printable characters can still need three digits, and control characters such as newlines can be longer in ZWUS-7. Non-ASCII characters retain their code points. Frequency ranking applies to strings only; number arrays use ordinary base-7 numbers.
|
||||
|
||||
## Automatic Detection with Sign
|
||||
|
||||
If you enable **Sign** when encoding, an invisible, collision-free signature is attached to the secret message. When decoding—either in the extension popup or via the on-screen overlay—inØsight automatically identifies and switches to the correct base and cipher every time. You never need to remember or guess which standard was used.
|
||||
If you enable **Sign** when encoding, an invisible signature is attached to the secret message. When decoding—either in the extension popup or via the on-screen overlay—inØsight identifies the base and cipher.
|
||||
|
||||
---
|
||||
|
||||
@@ -46,8 +62,8 @@ Uses 7 unique characters (base 6 digits + delimiter):
|
||||
| **Digit 4** | `U+200B` | Zero Width Space |
|
||||
| **Digit 5** | `U+200E` | Left-to-Right Mark |
|
||||
|
||||
### ZWUS-8
|
||||
Uses 9 unique characters (base 8 digits + delimiter):
|
||||
### ZWUS-7
|
||||
Uses 8 unique characters (base 7 digits + delimiter). Printable ASCII is ranked so frequent English characters take fewer digits; other Unicode code points retain their numeric value (control characters move above the ASCII ranks). Number arrays use ordinary base-7 values:
|
||||
|
||||
| Role | Unicode | Character Name |
|
||||
| :--- | :--- | :--- |
|
||||
@@ -58,5 +74,4 @@ Uses 9 unique characters (base 8 digits + delimiter):
|
||||
| **Digit 3** | `U+2060` | Word Joiner |
|
||||
| **Digit 4** | `U+200B` | Zero Width Space |
|
||||
| **Digit 5** | `U+200E` | Left-to-Right Mark |
|
||||
| **Digit 6** | `U+180E` | Mongolian Vowel Separator |
|
||||
| **Digit 7** | `U+FEFF` | Zero Width No-Break Space (BOM) |
|
||||
| **Digit 6** | `U+FEFF` | Zero Width No-Break Space (BOM) |
|
||||
|
||||
Reference in New Issue
Block a user