`izzy-facebook.wacz` bevat alle data van zn facebook, is gemaakt door deze extension:  https://webrecorder.net/archivewebpage/  

Je kan die file bekijken op: https://replayweb.page/  
Maar die rendered niet goed.  

Claude heeft een alternatief gemaakt die alle text van posts en comments weer geeft en sommige videos.  
Om te openen de hele `fb_render_out` folder downloaden, en in de folder index.html openen met chrome of andere browser.  

# claude zijn README
# fb_warc_render

Turns a Facebook **WARC/WACZ** capture into a browsable static HTML archive —
one page per person, with posts, comments/replies, reaction counts, images,
reassembled videos, and links back to the live Facebook posts. It reads the
captured response bodies directly, so it does **not** need a replay engine.

---

## 1. Install — Ubuntu (fresh install)

```bash
sudo apt update
sudo apt install -y python3 python3-venv python3-pip ffmpeg
python3 -m venv ~/fbenv
~/fbenv/bin/pip install warcio beautifulsoup4
```

## 2. Install — Windows (fresh install)

Open **PowerShell** and run:

```powershell
winget install -e --id Python.Python.3.12
winget install -e --id Gyan.FFmpeg
```

Close and reopen PowerShell (so PATH updates), then:

```powershell
py -m venv fbenv
fbenv\Scripts\pip install warcio beautifulsoup4
```

> `ffmpeg` is only needed to rebuild videos. Skip it if you don't care about video.

---

## 3. Run the script

Put `fb_warc_render.py` and your capture (e.g. `my-archive.wacz`) in the same
folder, then:

**Ubuntu**
```bash
~/fbenv/bin/python fb_warc_render.py my-archive.wacz fb_render_out
```

**Windows**
```powershell
fbenv\Scripts\python fb_warc_render.py my-archive.wacz fb_render_out
```

- First argument = your `.wacz` (or `.warc.gz`).
- Second argument = output folder (created automatically).

It prints a summary (posts, people, images, videos, unlinked comments).

## 4. Open the render

Open the output folder and **double-click `index.html`** — it opens in your
default browser. Start there: it lists every person who posted; click a name to
see that person's posts, comments, images, and videos. Everything works
offline; nothing is uploaded.

---

## 5. Capturing the data — ArchiveWeb.page (short)

The script needs a capture to read. Make one with **ArchiveWeb.page**:

1. **Install**: add the *ArchiveWeb.page* extension from the Chrome Web Store
   (Chrome / Edge / Brave), or get the desktop app from
   `webrecorder.net/archivewebpage`.
2. **Use**: open it, **Create New Archive**, click **Start Archiving**, then
   browse the Facebook page in the recording window — scroll slowly, open posts,
   and click **"View more comments"** to load comments. Stop, then **Download →
   WACZ**.

**Why the built-in replay (replayweb.page) looks broken but the data is fine:**
replay re-runs Facebook's JavaScript, which fires dynamic requests that don't
match what was recorded, so the feed renders blank. But every response Facebook
sent during capture is stored verbatim in the WACZ. This script ignores replay
and reads those stored responses directly — that's why it works where replay
doesn't.

---

## 6. What's missing / imperfect in the render (short)

- **Videos**: only fragments that buffered during capture exist, so video may be
  partial or fail to rebuild. Check `video_urls.txt` in the output.
- **Comments/counts**: only comments you actually expanded during capture are
  present; counts reflect captured data and may under-count the real totals.
- **Unlinked comments**: comments whose parent post wasn't captured are listed
  in a separate section on `index.html` instead of under a post.
- **Heuristic extraction**: Facebook's JSON is undocumented, so some unusually
  structured posts may be missed or mislabeled.
- **Out of scope**: the page's own comments left on *other* people's posts can't
  be captured (Facebook doesn't expose that list anywhere).