FoddoLearn
Foddo Learn · 13 chapters · ~114 min

Learn watermarking the hard way

Don't trust a watermark you haven't broken yourself. 13 hands-on chapters with live browser demos: break LSB, crush files with JPEG, survive crops, then pick a method for your real route. Everything runs locally. No uploads.

0/13

Your progress saves in this browser only. No account, no tracking.

13chapters
13live labs
0uploads
100%local
Continue where you left offChapter 1: Visible watermarks deter. Invisible IDs attribute.

Two different jobs. Visible marks make casual reposts ugly. Invisible per-subscriber IDs answer which copy escaped after a leak. Most creators need both, in different places.

Continue chapter →

Start here

  1. 1 · Start here7 min

    Visible watermarks deter. Invisible IDs attribute.

    Two different jobs. Visible marks make casual reposts ugly. Invisible per-subscriber IDs answer which copy escaped after a leak. Most creators need both, in different places.

    Visible marks deter casual sharing but every subscriber gets the same pixels.Start chapter →

Core

  1. 2 · Core8 min

    How invisible watermarking traces a leak

    Each subscriber receives a file that looks identical but carries a private recipient ID. When a leak appears, you recover that ID from the exact downloaded file and match it to your delivery record.

    One master becomes N unique copies, one per recipient_id.Start chapter →
  2. 8 · Core7 min

    The CSV is the map. Dirty map, no attribution.

    One duplicate recipient_id means two humans share one fingerprint. Break a list live, watch the collision, fix it, and confirm every ID names exactly one human.

    recipient_id must map 1:1 to the human receiving that copy.Start chapter →

Hands-on

  1. 3 · Hands-on12 min

    LSB looks perfect until you save as JPEG

    Least-significant-bit hiding is invisible and trivially destroyed. Embed a message in your browser, export PNG versus JPEG, and watch the payload survive once and die once.

    LSB survives untouched PNGs and dies on any JPEG re-encode.Start chapter →
  2. 4 · Hands-on10 min

    Compression, crops and screenshots: the three killers

    Drag three sliders and watch similarity collapse. Re-encodes change bytes while the image still looks the same, crops delete evidence outright, screenshots create a brand-new bitmap.

    JPEG quality under ~70 visibly degrades fragile marks while the image still looks fine.Start chapter →
  3. 7 · Hands-on8 min

    Tags travel with files. Strip them before delivery.

    Scan a phone photo, count the EXIF and GPS tags riding along, strip them with a canvas re-export, and verify zero. All local.

    Camera JPGs carry GPS, device IDs and edit history by default.Start chapter →
  4. 9 · Hands-on9 min

    See the frequencies robust methods hide in

    Your image as 8×8 cosine blocks: heatmap the mid-band hiding space, then quantize it away and watch detail dissolve in the exact order JPEG kills.

    Images are sums of cosine waves; JPEG keeps the big slow ones.Start chapter →
  5. 10 · Hands-on8 min

    Will this image carry a mark?

    Texture and edge analysis scores your photo as a watermark carrier. Test your flattest pack image. The gap between best and worst is your real risk spread.

    Texture and edges are hiding space; flat gradients starve fragile methods.Start chapter →
  6. 11 · Hands-on9 min

    Audit the whole pack the night before

    Drop up to 20 images: dimensions, metadata tags and carrier scores in one table, exportable as a release-notes CSV. Batch thinking without the app.

    Audit packs as tables, not vibes: every file gets dims, tags, carrier.Start chapter →
  7. 12 · Hands-on7 min

    Write a takedown notice that works

    Platform-tailored notice generator with an evidence checklist attached. General information, not legal advice. Get counsel for high-value disputes.

    Exact post URLs, not channel homepages: precision gets removals.Start chapter →

Decision

  1. 5 · Decision8 min

    Pick a method for your actual delivery route

    LSB, DCT, TrustMark, Robust Transform and WAM fail in different places. Answer four questions about format, channel, compression and screenshot risk to get an honest recommendation.

    Match protection to how subscribers actually share, not how you wish they would.Start chapter →

Field manual

  1. 6 · Field manual9 min

    Limits, evidence and what to do after a leak

    No watermark survives everything. Learn the evidence chain that still gives you options: preserve the file, compare, audit metadata, and only then attribute.

    Save the exact file, never a screenshot, and log URL plus time immediately.Start chapter →
  2. 13 · Field manual12 min

    Three cases. Download. Investigate. Reveal.

    Fictional training scenarios with real fixture files: a Telegram forward, a cropped repost, a dirty CSV. Work each with the free tools, then reveal the solution.

    Triage before attribution: compare, audit, then decide on Inspect.Start chapter →

How to work the labs

New chapters ship over RSS. Subscribe to never miss a lab.

  1. Start at chapter 3 if you are impatient: LSB fragility lab breaks a hidden message in 60 seconds.
  2. Use the sample image first. No uploads of any kind, same lesson. Then try one of your own exports.
  3. Read the caveats. Every demo has an "Honest limits" box. Knowing what a demo does not prove is the actual skill.

Diagrams are educational illustrations, not Foddo internals. Foddo implements LSB, JPEG DCT, TrustMark, Robust Transform and WAM locally with different survival profiles.

Workflow Upgrade

From one-off lesson to every subscriber copy

Finish one chapter and 10-line LSB demos will never fool you again. Finish every chapter and batch day stops feeling like gambling: Distribution mode plus Inspect is the repeatable version of what you just did by hand.