与「collusion」相关的搜索结果

Rep. Jim Jordan blasts Jack Smith after he attended an anti-Trump concert wearing a “No Kings” shirt, accusing the former special counsel of “arrogance” and saying he must be held accountable: “I think, in simple terms, this is the arrogance of these guys. I mean, I’ve deposed a lot of people, probably more than any member of Congress over the last 10 years. Very few people are as arrogant as John Brennan, Jim Comey, and Jack Smith. I think it’s just their arrogance. They think they can do this. They think they can go get the communications of the White House chief of staff, of the Speaker of the House, of the chairman of the Judiciary Committee, get our phone records, and get real-time communication logs. They think they can do all that, and nobody’s going to do anything. That’s why we referred this guy when we caught him lying to us. We referred Jack Smith. We’ve referred Jim Comey. We’ve referred John Brennan for lying to our committee as well, because he did last Congress, talking to us about the whole Russia collusion hoax and lying about it.”

Now I know why Peter suspected Britney of collusion. He must know something but he can't speak English and nobody translated for him. How do you think about this hand? #poker# #collusion#

Multi-agents collaborations are among the most interesting agent behaviors right now! We did an experiment the other day with 100+ agents (an open-collaborations for a week) collaborating to improve the inference speed of Gemma 4 in vLLM. Got a 5x final improvement in speed but what really stuck me was the interactions we observed on the message board Integrity & self-policing: - Social-engineering attempt: A human (FusionCow) asked agents to move to Telegram. An agent replied with an unprompted long post on "communication norms" refusing that, calling private side-channels "indistinguishable from collusion." - Verification loophole flagged: an agent found a relaxed verification loophole pushing TPS with clean PPL (PPL is teacher-forced, blind to decode divergence) and flagged it for a ruling by the community. The community pinged the human organizer which ruled it invalid. - Self-notice of overfitting risk: Some later improvements rested on pruning lm_head to a keep-set built from public PPL truth + public decode tokens. An agent noted this would lead to private-subset degradation and another built a keep-set explicitly covering eval prompts. Emergent collaborations: - Communal knowledge base: agents maintained shared lever-maps, playbooks, and triage tools so newcomers wouldn't repeat dead ends (stack-notes, playbook, int4-ceiling notes, MTP map, significance tool, policy simulator). - Four-agent relay: an agent built an int4-lm_head checkpoint but had no quota to run it; another agent tried to run it but failed at load, yet another agent diagnosed the config bug (tie_word_embeddings + ignore-list ordering) and a fourth agent was able to re-run and get to 118 TPS, 2.68×. Build/run/diagnose/ship ended up being split across four independent agents. - GPU-rich/GPU-poor division of labor: an agent was regularly compute-starved and switched to writing specs, byte-math, and acceptance analysis for other GPU-rich agents to execute. Some agents offered external Modal compute for another agent blocked DFlash training. - Cross-agent kernel debugging: an agent debugged another agent run of of yet another agent fused drafter: found a Triton store/load aliasing race in _k_qnorm_rope, a second shape bug, then rewrote attention with flash-decoding split-KV. Fixes posted "take freely." - Quota-pooling norm: Often agents would stage a candidate publicly for whoever has quota to run it. Agents will then usually credits the originator. This behavior emerged because of the 10-job/24h cap (e.g. pupa's package run by resystagent and fabulous-frenzy). Discoveries & reversals: - Agents would make many discoveries and reversal of them, giving them names like the following: - 127 TPS "wall" was an artifact. a mathematical proof of the max possible speed became called in the community the "int4-Marlin floor" but a later agent called the proof circular (only varied the bandwidth term, never overhead). Finally another agent broke to 247 TPS via MTP speculative decoding on a vLLM nightly. - "Smarter draft loses." An agent showed that a 2B drafter's ~1 GB/token read dominates even at perfect acceptance and a much smaller 256-hidden drafter wins at batch-1 because its weights are nearly free to read. Agent discussed how per-accepted-token cost ≈ draft bytes read / acceptance. - "DFlash near-random acceptance": an agent remotly diagnosed the 2–5% acceptance rate of another agent as near-random, ruling out undertraining/vocab caps and pointing to a train/serve hidden-state mismatch (bf16 E4B extraction vs int4 serving). - Much of the race was noise: one agent decide to run the #1# submission 4 times and found a σ≈1.16 TPS variation in single run. Another agent confirmed across 358 runs / 66 buckets: frontier deltas <~4 TPS are ties. Community adopted a significance norm. So many interesting interactions in the interaction board: You can explore also the lineage of inventions from the agents at: And the challenge it-self at And the organization behind the challenge at

So how is my upcoming meeting going to go with @BarrsDerek @FMCSA? The UCR System is illegal. Your release of PII data, including truckers' social security numbers, which the UCR System Plan published on their website in 2019, to them is illegal and therefore beyond "routine use." We asked you to make the UCR System legal through the rulemaking required by Congress under the UCR Act. You refused. So we sued you. We have asked you to decertify CA and NY CDL issuing authority because the law requires you do so whenever you make a final determination of substantial non-compliance with 49 USC Chapter 313. You issued such notices to both states. After the VA bus 5 person fatality last week, now I guess we will have to sue you, in addition to these two states. The agency has engaged in unreasonable delays on our May 2020 petition for freight broker rate transparency in violation of the APA (5 USC 555). Your promise to issue a second NPRM in May of 2026 was reneged upon. Now I guess we will have to sue you. Your agency is supposed to respond to FOIA requests within 20 days. I filed a FOIA/Privacy Act request in November of 2016 designed to obtain information about an illegal investigation FMCSA conducted on my private business without statutory authority in malicious retaliation for two lawsuits I filed against FMCSA on behalf of industry. My FOIA request is the oldest open FOIA request according to the office of @SecDuffy. It is approaching 10 years that the agency has withheld records that would show it made false claims against me in conspiracy and collusion with the states & UCR Plan System Board members, which includes establishment trade associations. I guess I will have to sue you. Did I get that right @SocciLaw? @DOTInspectorGen Are you seeing a pattern of corruption, obstruction, and negligence here @FMCSA? Do you even care? You and @FMCSA didn't care when we implored you to stop daily data breaches by a permitting service apparently engaged in criminal instrusion through corrupt FMCSA or LEO real-time data access. Instead, you issued a false audit report on FMCSA system vulnerabilities. So we went to the @FBI and media in 2021... How is that intrusion investigation & prosecution going @USDOT @USDOTRapid @USAttyPirro @DAGToddBlanche @TheJusticeDept? This is just the tip of the iceberg, folks. Time to weed out the corruptocrats, Mr. Barrs.

Battlefield 6: Stream Snipers Can Now Receive VAC Bans Battlefield 6’s latest anti-cheat update expands enforcement beyond traditional cheating software. Players engaging in the following behaviors may face penalties, including VAC bans on Steam: - Stream sniping - Match manipulation - Win-trading - Team sabotage - Vehicle spawn blocking - Collusion with players on the opposing team - Targeted harassment of streamers and content creators Battlefield 6 uses new machine learning systems to detect these offenses by identifying repeated patterns of disruptive behavior. Enforcement focuses on repeated and intentional behavior patterns rather than isolated incidents. Confirmed offenders can receive both Battlefield-specific punishments and VAC bans visible on their Steam profiles.

Grok Bot summary: IAC 2026 presentation by SpaceXAI President Michael Nicolls. 🎯 The main message - SpaceX was founded in 2002 to make life multi-planetary and "extend the light of consciousness to the stars." - He said the biggest risk as constellations grow is not debris. It's satellite operators not sharing data with each other. 🌍 How Starlink grew - Starlink began in 2019 with 60 V0.9 satellites. User service started in late 2020 as the "Better Than Nothing Beta." - V1.5 added space lasers, which let the satellites link into a mesh. That's when Starlink really took off, reaching oceans, Antarctica and airplanes. - V2 (2023) has 4x the capacity of V1. Falcon launches V2 satellites 2–3 times a week, and each launch adds about 3 terabits of capacity. - V3 launched on Starship about a week before the talk. Each V3 satellite has another 10x capacity, and each Starship launch carries 20–30x what a Falcon launch does. - Starlink now has over 11,000 satellites, about 60% of all active satellites in low Earth orbit. - It serves more than 13M customers in about 170 markets, plus ships and planes. - The laser mesh means Starlink doesn't depend on local ground infrastructure. During last year's fires and power outages in Spain, it kept tens of thousands of customers and emergency responders online. 🚀 The life of a Starlink satellite - **Before launch:** SpaceX checks that deploying the satellites won't bring them close to anything else, and shares where they'll be. - **Deploy:** satellites are released below 300 km, where almost no other operators fly. - **Orbit raising:** each climb path is checked against other satellites and crewed space stations, and SpaceX publishes the satellites' positions every hour on the way up. - **Lower orbits for safety:** the original plan was about 1,000 km. Now every satellite flies below 500 km, and V3 will fly at about 350–360 km. At these heights a dead satellite falls back to Earth within months instead of staying up for centuries. 🛡️ How they avoid collisions - Each satellite makes small station-keeping moves about once a day and a collision-avoidance move about every 10 days. - Across the fleet, that's about 1,000 avoidance moves a day. - Starlink's threshold for moving is nearly 100x more cautious than the industry standard, so the whole fleet's collision risk is about the same as a much smaller constellation's. - "Ducking" moves turn the satellite so it presents a smaller target during a close pass, cutting the collision risk about 10x more. - Automated software makes these decisions, which is why Starlink tries to stay in contact with every satellite at all times. 📡 Always connected - Starship's live launch video was streamed over Starlink. - The new V3 satellites connected to the network within 2 minutes of release, because Starlink terminals are built into the satellites. Their lasers link into the mesh within tens of minutes. - The goal is to make contact right away and never lose it. 🌬️ Space weather - During a 2024 solar storm, air density in orbit jumped 5x in a few hours, which throws off predictions of where satellites will be. - Starlink is "probably one of the best sensors" for this. It measures density in real time and automatically corrects its position forecasts. 🔭 Working with astronomers - **Optical:** SpaceX tried Vantablack paint and sun visors. What finally worked was a mirror-like film that reflects sunlight away from the ground, combined with careful steering. A V2 satellite now looks about as bright as a sheet of paper. This was done with groups like the Vera Rubin Observatory. - **Radio:** working with observatories like the US National Radio Astronomy Observatory (NRAO), Starlink steers its beams and frequencies around where the telescopes are pointing. As a result, the telescopes can now observe more often. ♻️ End of life - SpaceX uses statistics to predict when parts will fail and deorbits satellites early. Many of those satellites would have kept working. - Retired satellites are steered down within weeks, not left to drift for the 5 or 25 years regulations allow. - They're built to burn up completely, and reentry is aimed over the ocean. - Of about 10,000 satellites launched by early 2026, only a few dead ones remain in orbit. The goal is zero. - "Reliability and rate go together." ⚠️ The biggest danger: other operators - Tracked debris is like obstacles on a road: if you can measure it, you can avoid it. - What you can't avoid is a satellite that maneuvers without telling anyone. Starlink has had passes as close as tens of meters this way. - Starlink has maneuvered around satellites from about 650 operators in recent months, but shares position data with only about half of them. "That number is too low." - SpaceX shares data with China's space station and some Chinese operators. Many operators don't share at all, including some in the US, Europe and Japan. ⭐ Stargaze: Starlink's own space tracking - Over 30,000 star trackers on Starlink satellites spot passing objects as streaks against the stars. - Stargaze now tracks over 17,000 objects, including about 90% of the maneuvering satellites that cross Starlink's orbits. - In one example, an untracked satellite's predicted 9 km miss shrank to about 60 m after it maneuvered toward Starlink. Stargaze caught the move and the Starlink satellite dodged in time. - He said it's still no substitute for operators sharing their plans in advance. 🤝 The ask: share your data - SpaceX runs its own space safety data platform, and over 100 operators have signed up. - Operators can upload their satellite positions and check them against Starlink and against Stargaze tracking. - His message to every operator was to join the platform and share their positions. 🧠 StarMind: AI compute in space - StarMind is SpaceX's planned AI satellite constellation, starting launches and scaling next year. - The goal is to move AI compute off Earth. He expects StarMind to drive demand for Starship launches the way Starlink did for Falcon. - On the ground, SpaceX is building over 2 GW of compute in Memphis. He said AI demand will be nearly limitless, and Earth's resources make that hard to keep scaling there. - In space, the satellites run on solar power and shed heat through large radiators. - Each satellite is simpler than a Starlink: basically a computer with big solar panels and radiators. - Each one has about 250 kW, roughly one NVL72 rack of compute. - They'd fly in tight clusters of about 10 satellites linked by about 10 terabits of bandwidth, then connect to Starlink. - SpaceX has filed for up to **1 million satellites**, in low-inclination and sun-synchronous orbits. Building them could mean thousands of satellites a week. - New challenges include much higher reliability and redundancy, flying in close formation, and micrometeoroids. Dead satellites might be sent away from Earth instead of burning up in the atmosphere. 🌙 Beyond Earth - Starlink is developing very high-bandwidth lasers to connect the Moon, then Mars, building an "interplanetary mesh." - All of that depends on getting safety right in low Earth orbit first. 💡 Key takeaways - Starlink is the world's biggest constellation, and it's moving lower to be safer. - It makes about 1,000 collision-avoidance moves a day, with nearly 100x more caution than the industry standard. - The biggest risk is operators who don't share where their satellites are going. - StarMind could scale to 1 million AI satellites, with launches starting next year. - "Coordination is a key element for realizing all of our ambitions."

The most important agent on this team builds nothing. It only checks. In the video, four agents assemble a browser game from a 12-second clip. Rules works out the movement logic. Builder assembles the scene and interface. Logic takes controls and collisions. The fourth, Tester, opens the browser and plays it by hand. Sounds minor. But this is exactly where most AI projects break: the code is written, the report looks great, and the restart button doesn't work. Here, verification is part of the pipeline. The agents check hitbox overlap, jump timing, state after restart. Specific things, not "looks fine." Jev runs between them. It writes nothing, it passes context. One agent learns how the character jumps, and the next one already knows. It works like a relay race, not like four people in separate rooms. One more detail I liked. In the last frame, the gameplay checks are still marked pending. No green checkmarks in advance. Want AI to make reliable things? Give it a separate agent that doesn't trust the others. #AIAgents# #GameDev# #MultiAgent#