X ALGORITHM UPDATE 🚨 X just stopped cutting new posts first, and that should help small accounts (I check it daily with Claude and share updates worth sharing with you) tl;dr: - X can only check 2,800 posts each time you open your feed - new posts used to be last in line, so they got cut first - now everything gets cut equally, new posts included - posts labeled low quality or misinfo now show a warning, and people can't like, reply or share them - no score changes this time lesson learned: your new posts now get a fair chance to be seen. Your first 2 hours still matter most. full details: - How it worked until this week Every time someone opens For You, X collects around 3,700 posts it could show them: posts from people they follow, popular posts, posts liked by similar people, and brand new posts. But X only has time to check 2,800 of them. So it just took the first 2,800 in line. Brand new posts were at the back of the line. When there were too many, they were the ones left out... and a post that never gets checked can't be shown. - What changed Now everything gets cut by the same amount. 25% too many? Every type of post loses 25%, new posts included. Nobody goes first. - Why small accounts should care Those brand new posts are under 2 hours old, with under 8 likes and under 500 views. That's where most posts from smaller accounts are. My read: they now get a fair chance instead of being cut first. How often X actually hits the 2,800 limit isn't in the code, so I can't tell you how big the difference is. - Low quality and misinfo posts now show a warning If X labels your post as low quality or misinformation, people who don't follow you see a warning on it, and they can't like, reply, repost, bookmark or share it. The code doesn't say what gets a post that label. Here's a recap of what you should be doing: - a new post gets its extra push only in its first 2 hours and first 200 views, so post when your people are online - likes carry more weight than ever at 0.66 each - people sticking around pays, the time-spent score is 50% higher than two weeks ago - a read of 10+ seconds after someone opens your post adds 0.4 - the boost favors the post with the best like rate from its first viewers - accounts up to 50K can get one fresh original lifted to roughly 16th - nothing beats a copy link share, it scores 20 - replies, quotes and DM shares each score 5 - talk with your mutuals, replies between you score 20 instead of 5 - originals are the only posts that travel outside your follower base - the 1st and the 32nd like each open a new route to strangers - your 2nd post in the same feed is worth 62% of the first, so pick your best one - videos still need 10+ seconds to qualify for the video lists - earning a follow adds 4 - a pinned post with a bad link can flag the account for 7 days, worth a quick check What you should NOT be doing: - posts that get labeled low quality or misinfo now carry a warning, and nobody outside your followers can like or share them - video alone won't carry you, an open counts 0.02 and the watch 0 - hide-worthy posts cost more, "not interested" sits at -52.27 - a post at 3am burns its 2 hour window before anyone sees it - a tap that turns into a bounce is worth only 0.3 - replies and reposts don't get past your followers - insults get your post hidden from anyone who doesn't follow you - adult media in 3 of your last 5 posts puts a label on your account - disguised content in videos gets checked from 64 likes, harder at 512 - self-reply chains under big accounts risk being zeroed - one account label and non-followers stop seeing you entirely - low-rated links don't belong in your pinned post - recycled wording can get tagged as copypasta spam - strangers tagged plus a low quality link is a pattern X flags - engagement bait has no size exemption - several posts in a row end up competing with each other - hashtag stacks add nothing - bookmarks are still worth 0 - 48 hours in, For You is finished with a post

banned for reverse engineering work? that’s wild oh well, -$500, and a bunch of banked resets) but gained motivation to get 3 more machines and finish my cluster. i have never used openai to exploit or find vulnerabilities, only local reverse engineering which tripped daybreak.

Security called me at 6:12 AM today. "Patch every PHP server immediately." I asked what happened. "Two critical vulnerabilities. Remote code execution. No authentication required." Cool. How many PHP servers do we have? According to inventory: 12 According to reality: Nobody knows. We found one running WordPress. Three running old internal tools. One under someone's desk. Two inside vendor appliances. A forgotten employee directory from 2016. And a server named: PHP-OLD-DO-NOT-TOUCH Naturally, that one runs payroll exports. Then we found a PHP 5.6 box. I asked who owned it. The documentation said: BRIAN. Brian left in 2019. We called Brian. He said: "Oh wow, that's still running?" Excellent. By 8 AM, leadership joined the incident call. CEO: "Can hackers actually get in?" Security: "Potentially yes." CEO: "Without a password?" Security: "Yes." CEO: "Then why do WE need passwords?" Not the lesson. Finance asked if we could wait until the weekend to patch because downtime affects revenue. Security explained that the alternative was letting strangers execute code on our servers. Finance asked for a cost comparison. At 9:17, someone suggested temporarily taking the vulnerable websites offline. Marketing refused. "Our campaign is live." So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover. We finally patched everything we could find. Then our scanner discovered another PHP server. Hostname: TEMP-PHP-2014 Uptime: 4,512 days. Nobody knows what it does. Nobody owns it. Nobody can shut it down. But every time we block network access, the warehouse stops printing shipping labels. Security has classified it as critical infrastructure. It is running PHP 5.4. The vulnerability has existed longer than half our employees. The emergency patch took four hours. Finding out what PHP actually runs took eleven. The internet isn't held together with code. It's held together with servers everyone is afraid to turn off.