🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-02 22:09 UTC.

@T3chFalconon X · 2026-10-02
Reason 1: RATs are real and common. Remote Access Trojans are a documented, widespread category of malware. they include webcam access as a standard feature. Operators can activate webcams silently on victim machines. Reason 2: There's a possibility indicator light can be bypassed. Johns Hopkins researchers published a paper in 2013 showing they could reprogram a MacBook webcam's firmware to operate independently of the LED indicator. camera on. light off. This works on any webcam where the LED is firmware-controlled rather than hardwired to the power circuit. Reason 3: a physical cover is the best. No exploit or malware can get to it. Reason 4: the FBI said so. in 2016, FBI Director James Comey said he covers his webcam. He said it was basic security hygiene. the head of the agency that investigates computer crimes covers his camera.
quotesthe post below (author id 1580269238429880332)
I see a lot of people covering their laptop cameras. But I feel like some people don't actually know why they're doing it. They just saw someone else covering theirs and followed the trend. Can someone explain why people actually cover their laptop cameras? Genuinely curious.

This post quote-tweets the one above. Its text and identity are anchored (one level, no deeper); any media it showed is anchored with this post's media. Quoted text may be truncated for a long-form original — the anchored hash covers exactly the text shown here.

posthttps://x.com/T3chFalcon/status/2106113327029989389
author id1592695259502370817
posted2026-10-02T20:05:21.000Z
manifest sha256ed9b27609d9059152a1b9c9e52d140d127497a10e7c3b2a1b9b511066d4084a4
text sha25647251ad066ba0fd1512cc3274a984016d6cf16c5c3224c9d18f020f1d168215a
quoted text sha256f2bded391a15639c0447d67cb0bbd75db3c30160b2ff50b8b8deefb7bc6ec52f (quoted post 2105281517861908743, author id 1580269238429880332)
on-chain⛓ anchored — 1b064af9ce36e74d1754188a1e8bbfd7905fb3242bae62c1b2398ee347687a39

Verify it yourself: the manifest is the exact JSON whose SHA-256 is ed9b27609d9059152a1b9c9e52d140d127497a10e7c3b2a1b9b511066d4084a4; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 47251ad066ba0fd1512cc3274a984016d6cf16c5c3224c9d18f020f1d168215a, plus the quoted post's id, author, and text hash f2bded391a15639c0447d67cb0bbd75db3c30160b2ff50b8b8deefb7bc6ec52f, and read the anchor transaction's OP_RETURN bsv.cx / x1 / ed9b27609d9059152a1b9c9e52d140d127497a10e7c3b2a1b9b511066d4084a4 — the block's timestamp proves the post said this at or before that time, with no trust in bsv.cx. Content archived via the X API.

← bsv.cx · JSON · ⚠ Report