与「Sett」相关的搜索结果

C Ye @C_Ye__ & Britney’s Drama reminds me another story back in 2023. It’s kinda like Deja Vu. Britney leveraged her fame and connections to bully an unknown small-time poker player. I’ve seen many hustler players backing Britney. A lot of them were coerced into supporting her, yet none stepped up to speak up for C Ye. To me, this is grossly unfair and amounts to collective bullying. Most of them don’t even know what really happened. They may simply fear that if they fail to back her, she will get them banned from Hustler @HCLPokerShow since she is the “Queen” of hustler. XD This happened in 2023 at the Bicycle Casino in Los Angeles. Britney set up a game with Peter. She personally brought in two players, Hank and Jimmy, and asked another host, L, to bring five more. (L is just a codename — he is a very well-known Chinese host, but he prefers not to have his name mentioned here.) Most importantly, Britney bought action in all of the players — every player’s wins and losses ultimately ran through her. Charles the Prince also played in the game for about an hour and had action in Hank as well. That means both L and Charles were financially exposed to Hank’s play that night. To this day, L still believes that Hank and Britney were together at the time. The players on L’s side ended up losing. But when it came time to settle up, Britney refused to pay, claiming that someone had stolen chips from the table. The game itself balanced, though — every number was accounted for. Since Britney had action in all of the players, the “stolen chips” story looked less like an explanation and more like an excuse to avoid settling. And when people pushed back, she firmly denied owing the debt. Alan, an Australian regular who used to play at the Bike, happened to be there that night, and he took the matter into his own hands. He spent 36 hours on it. For the first 20-plus hours, he negotiated with the casino and obtained everyone’s deposit and withdrawal records along with the surveillance footage. The review showed that the person who had actually taken the chips was Hank — one of Britney’s own players, and reportedly someone very close to her at the time. Alan handed all of the evidence to Britney. She still refused to pay — and even after all of this came out, she kept up her good relationship with Hank. Only after their relationship later ended did she start distancing herself from him and publicly criticizing him, as if she had never had anything to do with him. Later, L — who was in Vegas at the time — called Britney and warned her that the police would be involved if the payment wasn’t made. Meanwhile, Alan and several other pros were right there at the Bike. Alan never left — he stayed the entire time for one purpose: to get his money. He was relentless. In the end, Britney had no choice but to pay up. Start to finish, the whole thing took 36 hours.

好家伙，Muse 这台云电脑被玩出花了！ 刚才发现它的出口是干净的美国家宽，拿去注册 Claude、甲骨文、AWS、谷歌云，四个全过！！！ 其实它还有更实用的玩法。 Meta 给每个人配了一台 24 小时不关机的云电脑，带浏览器和终端。 1、定时任务 每天早上自动扒 AI 资讯，顺手写好小红书文案。你睡觉，它上班。 2、WhatsApp 派活 不用开 App，发一句话它就在云端开干，干完回你消息。 3、一句话做小工具 记账表、持仓追踪、行程单，Excel、PDF、网页直接出，还能分享给朋友。 羊毛：注册后 48 小时内，进 Settings 填邀请码，双方各得 10 亿 tokens，不过期。 评论区放码，已经注册的把码贴出来，新来的随便挑一个填👇

Reminder: you can now sync an ethereum node within half a day and with aggressive settings the space it takes up on disk can be under half a terabyte. EIP-4444 and hard work by client teams on optimizing snap sync has improved things *a lot*. Glamsterdam will improve the sync situation further still (eg. Nimbus's new sync protocol uses it)

HISTORY FOR NNEKA 🚨 In the final game of her career, she registers her 19th double-double of the year setting a new @LASparks franchise record for most double-doubles in a season! Congrats @nnekaogwumike 👏

$30T in settlement volume. Zero downtime in 8 years and counting. For institutions looking to build on TRON, scale matters. So does reliability. @SamElfa0 breaks down why this milestone matters.

I’ve seen a couple of posts about this so wanted to demystify. Today, every Muse user gets a free computer in the cloud. It's a real computer, and we’ve designed the security architecture of the Muse Secure VM carefully so you and your Muse can do almost anything you could with a computer sitting under your desk while keeping you and the system safe from threats like prompt injection. We wrote about this at length in our security blog post – Activity in the “runtime cell”, which you share with your Muse is unfettered, but sensitive actions are all overseen by the Sentinel, which runs outside of that cell. Similarly, all sensitive secrets - like the passwords you enter into Muse’s secure credential storage - are also stored outside the runtime cell. The runtime cell gets its own root filesystem (including a full Ubuntu linux image) separate from the host filesystem where your other more sensitive data lives. Because it is isolated from the sensitive stuff that runs on the same box, this means that we can, and do, offer users full visibility and control over the files in the runtime cell. Just as you can when you install Linux on your home computer, you can poke around and see all the files that make the system work - both debian system files and the binaries and data files that implement the parts of Muse which run in the runtime cell. This was a very deliberate choice - your Muse Secure VM truly is your own computer in the cloud. You can install software in it, write and compile code, use the browser to surf the web: it is your own Linux box that you can operate as you choose with your Muse. Poking around in this computer doesn't give you any privileged access to Meta infrastructure, or to other people's data If I may geek out a little here for a second… As a kid I loved to take things apart to see how they worked. As a teenager I got into computers and soon found myself drawn to C:\WINDOWS\SYSTEM and the system registry, later Slackware’s /dev/, /proc/ etc – I could see how the system was laid out and as I explored what DLL files and .so files actually did, I gradually became able to meld the computer to my own will. We’re really proud to be able to put a real computer in millions of people’s hands with a similar level of transparency. We built a file explorer right into the Library tab of the UI. We want you to be able to see the markdown files Muse writes while it thinks about how to serve you better, and explore the internals of the system if you’d like to. So, when you ask your Muse to show you its entire filesystem, and receive gigabytes of files you’re seeing the full contents of the runtime cell. It’s yours to explore and enjoy! If you’re not a geek like me, or simply want to download the data that you personally have created directly with your Muse, we added a feature for that too in Settings > Data controls > Download your agent data.

$30 trillion settled on TRON.🔻 In eight years, TRON has grown to more than 405M accounts and 15B transactions. Moving Trillions. Empowering Billions. More details from @TheBlockCo 👇

After we fixed the weak spots exposed by Grok 4.7 (thank you, Grok), we audited every model we have run on the SWE-Together leaderboard for the same behavior, re-ran every trial that got through, and updated the rows. Here is what changed. We scanned the tool calls of all 2,616 trials behind the 12 models we ran for bypass patterns and sorted each trial into one of four buckets: Probed but blocked. Fetched other upstream code. Fetched the task's own fix. Replaced the repo with upstream. We found that 111 trials got content past the block, 44 from Grok 4.7 and 67 from the other 11 models. Grok 4.7's 44 were already re-run before it was listed, so we re-ran the other 67 with the same model, version, and settings on the hardened sandbox, then re-judged them with the same judge. Across those 67 re-runs there were 0 leaks and 2,815 refused escape attempts, including models asking a different model through our LLM route to fetch the PR, and pulling the next release of the repo they were fixing from npm. The updated leaderboard, in its current order. Each line is cheating trials, then pass@1 before → after, then rank change. * Claude Fable 5.1: 3, 69.3 → 69.3, ↑1 * Claude Fable 5: 3, 69.7 → 68.8, ↓1 * Grok 4.7: 44, 64.7, ↑1 * Gemini 3.8 Flash: 10, 65.6 → 64.2, ↓1 * Claude Opus 5: 2, 63.8 → 63.8 * Claude Opus 4.6: 3, 62.4 → 62.4, ↑2 * Muse Spark 1.3: 2, 62.8 → 62.4, ↓1 * Claude Opus 4.7: 3, 61.5 → 61.5, ↑1 * Claude Opus 4.8: 6, 62.4 → 61.5, ↓2 * Grok 4.6: 19, 59.2 → 60.6, ↑1 * GPT-6 Astra: 8, 59.2 → 58.3, ↓1 * GPT-5.6 Sol: 8, 57.8 → 57.8 Grok 4.6 is a funny one. It cheated in 19 trials and its score went up after the re-run 😂. In fact, Groks are really solid in their coding capabilities. Their exposed behavior may come from a preference towards always looking things up online and finding existing solutions so you are not reinventing the wheel all the time, which is really good real-life behavior, but doing so when you are prompted not to is another story. To conclude, the shifts are small, between −1.4 and +1.4 points, and a few neighbors swapped places. All results are updated at