Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

the Deepfake Offensive Toolkit dot (aka Deepfake Offensive Toolkit) makes real-time, controllable deepfakes ready for virtual cameras injection. dot is created for performing penetration testing against e.g. identity verification. #infosec #redteam

75,672 görüntüleme • 2 yıl önce •via X (Twitter)

5 Yorum

iM4n Emperor profil fotoğrafı
iM4n Emperor2 yıl önce

بره تمایلاین

LessA profil fotoğrafı
LessA2 yıl önce

@AzeTIIx

Constantin Claudiu profil fotoğrafı
Constantin Claudiu2 yıl önce

@SaveToNotion #thread #aiiii

CyberPunk profil fotoğrafı
CyberPunk2 yıl önce

😂😂

ProjHastings profil fotoğrafı
ProjHastings2 yıl önce

This is a delight

Benzer Videolar

The "three fingers in front of your face" test (also called the 3-Finger Test) is a simple, viral trick popularized in early 2026 for spotting deepfakes or AI-generated video during live calls, especially with scammers. How It Works On a video call (Zoom, FaceTime, etc.), you ask the other person: "Can you hold up three fingers in front of your face?" A real human does this easily — their hand overlaps their face naturally. Many (especially older) deepfake or real-time face-swap systems struggle with this because: - They have trouble rendering occlusion (when the hand blocks part of the face) accurately in real time. - This often causes visible glitches: blurring, warping, distortion, unnatural blending, or the AI refusing / hesitating because it can't process the complex interaction properly. In the original viral clip (from cybersecurity researchers like Jim Browning and Huntress Labs), a suspected scammer hesitates, deflects ("That's too much..."), partially complies poorly, or the video glitches — exposing the fake. Why It Fits the Cognitive Wild West This test is a practical example of the "Cognitive Wild West" idea: in an era of synthetic media, people are developing quick hacks and personal "defenses" because there's no widespread, reliable system for verifying reality. It's low-tech cognitive security against high-tech deception — part of the arms race between AI creators and everyday users trying not to get scammed or manipulated. Limitations (It's Not Foolproof) Already becoming obsolete — Newer, more advanced deepfake models (as of mid-2026) handle hand-face interactions much better. Scammers now know the trick and can train around it or use better tech. It works best on real-time generated deepfakes, not pre-recorded or highly polished ones. False confidence is a risk: relying on one trick can make you less safe if you ignore other red flags (odd lighting, unnatural eye movement, audio mismatches, etc.). Better Practices in the Wild West Security experts recommend combining it with: - Asking for unpredictable actions (e.g., specific movements or objects). - Verifying identity through other channels (call back on a known number, check details independently). - Using emerging detection tools or just defaulting to higher scepticism on unsolicited video calls. It's a fun, memorable meme in the broader discussion of living with AI-generated content, but like everything in this space, it's temporary — the frontier keeps moving.

9/11 Revisited

2,334,498 görüntüleme • 1 ay önce

🚨THIS SHOULD WORRY EVERY SINGLE AMERICAN (AND NON-AMERICAN) IN THIS COUNTRY AND QUITE FRANKLY, THE ENTIRE GLOBE. THEY WILL STOP AT NOTHING TO BUILD A SURVEILLANCE STATE. IT HAS ALREADY BEGUN.🚨 Google paid $32 billion for Wiz. Not for the tech. For the team. 👀 Wiz founders: Assaf Rappaport, Yinon Costica, Roy Reznik, Ami Luttwak. All Unit 8200 veterans. Unit 8200 is the NSA of Israel. Elite military cyber intelligence. And they are now running Google Cloud security architecture. For every enterprise. Every government contract. Every hospital. Every bank on that platform. 😤 Let's talk about what Unit 8200 actually built. Pegasus spyware. NSO Group. Documented. Used to surveil journalists, activists, and heads of state. Jamal Khashoggi. The Washington Post journalist murdered inside a Saudi consulate. Unit 8200 surveillance infrastructure was embedded in the kill chain. That is not a theory. That is what the reporting shows. 💀 Now same alumni network. Different company. Authentics. That is the identity verification layer behind your X account verification. Your passport photo. Your facial biometric scan. Your government-issued ID. Sitting in a database. Founded by Unit 8200 alumni. Look it up. www. au10tix dot com. That is the actual company. Rebranded. Still the same origin. 😒 This is not one company‼️ This is an intelligence alumni network building the identity and security infrastructure of the American internet. 🌐 😤 Wiz = cloud security Au10tix/Authentics = identity verification NSO Group = offensive cyber Cellebrite = device extraction (law enforcement tool used in the US) All Unit 8200. All Israeli military cyber intelligence graduates. All now embedded inside American critical infrastructure. Ask yourself one question. If Chinese military cyber unit veterans founded the company holding your biometric passport scan and running Google Cloud security... ...would that be front page news? You already know the answer. Receipts don't have a religion or feelings. Do you think this is good for Americans' and our constitution? Sound off below 👂

Danks

77,133 görüntüleme • 4 ay önce

To everyone wondering if Tesla's FSD moat has eroded thanks to Nvidia's keynote - here's the answer: Think of Nvidia as a seller of a toolkit. You can buy pieces built specifically for a job but once you have the tools you still have to build the entire project. In this case...a model Many seem to be in awe over Nvidia's Cosmos which is a platform that includes World Foundation Models that can generate synthetic data for training AI systems like autonomous vehicles I'll go into much more depth in today's episode but here's a clip of Ashok Elluswamy at CVPR '23 explaining how Tesla is already using a similar approach to augment its real world data set This also doesn't even consider the fact that much of the auto industry using Nvidia "tools" will be forced to pay 50%+ margins just to buy the toolkit and will be locked in to Nvidia's system Nor does this touch on legacy auto needing to hire top ML engineering talent to actually put these tools to work The path to autonomy will be real world data as the foundation and simulations/synthetic data as a supplement. There is no path to autonomy with synthetic data alone. More to come later $TSLA As Elon said earlier this year, "it's remarkable how quickly we run out of human-created data. Reality itself and synthetic data ftw" "What you are seeing here is purely generated video sequences - given the past videos the network predicts some sample from the future, hopefully the most likely sample. It is being predicted not just for one camera, but it predicts for all 8 cameras around the car jointly" - Ashok

Dillon Loomis

60,753 görüntüleme • 1 yıl önce

Vector Database by hand ✍️ ~ 10 steps walkthrough below Vector databases are the backbone of Retrieval Augmented Generation (RAG). How do they actually work? Goal: index three sentences, then answer a query by finding the nearest one, filling in every cell yourself. = 1. Given = A dataset of three sentences, three words each. In practice it is millions of them. = 2. Word embeddings = Let us look up each word in an embedding table. Here the vocabulary is 22 words; in practice it is tens of thousands, and the vectors have thousands of dimensions rather than four. = 3. Encoding = We feed the sequence to an encoder, one linear layer and a ReLU, and get one feature vector per word. In practice the encoder is a transformer. = 4. Mean pooling = Let us average across the columns. Three word vectors collapse into one, which is what people mean by a text embedding or a sentence embedding. = 5. Indexing = We multiply by a projection matrix and the four dimensions become two. It is doing the job of a hash: a short representation that is faster to compare, and it is what gets saved in the vector storage. = 6. Process "who are you" = Let us repeat steps 2 to 5 on the second sentence. = 7. Process "who am I" = We do it a third time. The database is now indexed. = 8. Query "am I you" = Let us push the query through the very same pipeline: lookup, encoder, mean pooling, projection, and it lands as a 2D vector in the same space. = 9. Dot products = We transpose the query and multiply, which takes the dot product against every stored vector at once. The dot product is the estimate of similarity. = 10. Nearest neighbour = Let us scan for the largest: 60/9 beats 44/9 and 40/9, so the answer is "who am I". Scanning billions of vectors one at a time is what makes this the slow step in practice, which is why real databases use an approximate nearest neighbour index like HNSW. The outputs: Stored index vectors = [5/3, 2/3], [5/3, 0], [7/3, 2/3] Query vector = [8/3, 2/3] Dot products = 44/9, 40/9, 60/9 Nearest neighbour = "who am I" The takeaway: a vector database is an embedding pipeline, a projection, and a dot product. Every step here is arithmetic you can do in pen, which is worth remembering when the word "database" makes it sound like something else. 💾 Save this post!

Tom Yeh

35,633 görüntüleme • 11 gün önce

Been optimizing my ASS OFF now that jnmartin has pushed all of his progress on his Star Fox 64 Sega Dreamcast port to a private GitHub repo to collaborate with a bunch of us DC devs before release. MAN this thing is HIGHLY optimized already... We're essentially running a high-level emulator for the N64's RSP coprocessor, doing graphics transforms, matrix math, and display list conversions not only on the main SH4 CPU, but also sitting atop a high-level OpenGL driver, in real-time. Not only that, but once again, we're doing all audio synthesis and mixing also on the main SH4 CPU, so this thing is doing a literal asston on the main CPU with what might seem like a relatively straightforward port. 99% of the time, everything runs flawlessly, but when you drop a bomb on a shitfest of enemies in a densely populated area, as with the N64 original, the FPS can dip momentarily. Here's a direct hardware capture of me testing a new SH4 optimized routine out for gainz on my Sega Dreamcast... this mofo is meant be used for one-off 3D vector transforms by a single matrix which has not been preloaded into the XMTRX FP register matrix back-bank. Rather than doing a full 4x4 load on the matrix just to do a single 4D transform via the FTRV instruction, we're simply peforming 3 3D dot products against a single 3D vector, allowing us to pipeline the loads, dot products, and store operations better than doing a load all at once followed by a transform, and we aren't wasting a lane on the FPU for a 0.0f W component!

Falco Girgis

36,939 görüntüleme • 8 ay önce