Construct HTTP request mostly in js

[mhchia]

!!! Steps 1~2 have been changed!!!

What's done?

Rust WASM

1. Rename prover to notarize
2. Make params more abstract by accepting method, url, headers, body, secrets (to be hidden), reveals (to be public)

Javascript (worker.ts)

1. Support notarizeTwitterDM and notarizeTwitterProfile
2. Use public notary at notary.efprivacyscaling.org:443
3. Tell websockify the target by token in websocketProxyURL

Steps to run

Step 1: Edit information
For general twitter info

tlsn-extension/src/pages/Offscreen/worker.ts

Lines 15 to 17 in a9bbe33

	const AUTH_TOKEN = '';
	const ACCESS_TOKEN = '';
	const CSRF_TOKEN = '';

To run notarizeTwitterDM, fill in

tlsn-extension/src/pages/Offscreen/worker.ts

Lines 22 to 23 in a9bbe33

	const conversationId = '';
	const clientUuid = '';

To run notarizeTwitterProfile, fill in

tlsn-extension/src/pages/Offscreen/worker.ts

Line 77 in a9bbe33

const twitterId = '';

And choose which to run

tlsn-extension/src/pages/Offscreen/worker.ts

Lines 135 to 136 in a9bbe33

	// const resJSON = await notarizeTwitterDM();
	const resJSON = await notarizeTwitterProfile();

Step 2: Open a new terminal. Build and run a websocket proxy with multiple targets

git clone https://github.com/novnc/websockify && cd websockify
./docker/build.sh
docker run -it --rm -p 55688:80 -v $(pwd):/app novnc/websockify 80 --target-config /app/websockify_target_cfg

Step 3: Build the wasm and run the dev server

pnpm install
pnpm run build:wasm
npm run dev

Step 4: Load built extension
Go to chrome://extensions, click Load unpacked, select the build directory

Step 5: Run notarize
Open the TLSN Extension and click Notarize. Check out the console by clicking the offscreen.html in the inspect views section in TLSN Extension

[mhchia]

Closed since it's covered by #20