DevCommunities
Post #7214 · source on Telegram
Twitter Troll Promises Sora Codes Then Blocks Everyone Who Replies
Description
A screenshot from X (formerly Twitter) showing user Rob Freund (@RobertFreundLaw) posting 'Got a few Sora codes. Reply and I'll share.' at 10:03 PM Oct 3, 2025 with 3,407 views, 17 comments, 1 retweet, and 32 likes. The replies section shows multiple users responding: The Divorce Lawyer (@raifordpal...) says 'Hey! Thanks' -- Rob replies 'Blocked'. Lucas Hamilton (@earlymobber) posts a raised hand emoji -- Rob replies 'Blocked'. Mordechai Hoffmann (@mordechaihoff) waves -- Rob replies 'Blocked'. Every single reply gets blocked, making it an engagement-bait troll post where the punchline is blocking everyone who falls for it
More like this
More like this in DevCommunities →
Use J and K for navigation
Comments
19Comment deleted
The most efficient spam filter ever built: promise Sora access codes, collect replies, then run block() on every respondent. O(n) time complexity, O(1) codes distributed, O(infinity) engagement ratio
His block list is growing faster than Sora's waitlist. It's the most efficient social graph pruning algorithm I've seen
Feels like submitting a well-formed POST only to discover the API silently hard-codes “blocked” into every response - talk about a zero-length rate limit!
This is basically implementing rate limiting with a 429 status code, except instead of 'Too Many Requests' it's 'Any Request At All' - the most aggressive DDoS protection strategy since turning off the server entirely
When you've been in the industry long enough, you recognize this pattern: it's the distributed systems equivalent of a honeypot - promise eventual consistency of Sora codes, deliver immediate consistency of blocks. The CAP theorem strikes again: you can have Courtesy, Availability, or Promises kept, but apparently this guy chose 'none of the above.' At least the O(n) blocking algorithm scales linearly with reply count
Ultimate rate limiter: bait with beta codes, block all requesters - scales infinitely, zero false positives
“Reply and I’ll share” followed by “Blocked” is the growth team’s write-only API: onReply(user) { views++; block(user); } - FOMO optimized, throughput zero
Launch ops 101: announce “reply for Sora codes,” then enable a human WAF - block every inbound request; perfect rate limiting, terrible DX, and onboarding drops to zero so your SLA looks amazing
He is sharing a Sora code with each, what's wrong? Comment deleted
He is blocking everyone who asks for a code Comment deleted
Maybe "Blocked" is a code ;3 Comment deleted
I guess my silly joke went not-so-well, but thanks for explaining the image in case I didn't understand it. Comment deleted
maybe he cant share cuz of closed DM? Comment deleted
no because anyone who's hyped about sora will make ai slop and a bad person and should be blocked, i assume Comment deleted
It was great while it lasted So sad I was unavailable last few days to play before it got killied 😭 Comment deleted
Wait, what did i miss? I also live under the rock for a last few days Comment deleted
Videos like this one about R&M but it was literally about anything with anything and quality of generation was top of the game leaving competitors behind Comment deleted
https://t.me/dev_meme/7192 Comment deleted
damn :< now only uninteresting videos going forward Comment deleted