Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

‼️Copy Fail (CVE-2026-31431) is a Linux privilege escalation bug that lets any local user get root using a 732-byte Python script, and itworks on basically every major Linux distro shipped since 2017. Website: Write-up: GitHub: It's a logic flaw in the kernel's crypto code (authencesn via AF_ALG and splice())...

443,752 Aufrufe • vor 2 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Claude Design + Shopify is f*cking ridiculous 🤯 You can now publish pages from Claude Design → Claude Code → Shopify. Built 100% with Claude Design, Claude Code, and the Shopify CLI. Perfect for DTC brands and agencies who want to skip the design → dev handoff entirely. Here's how it works: → Design any landing page in Claude Design → Export as a zip and drop it into Claude Code → Install the Shopify + Shopify AI Toolkit plugins → Prompt Claude to convert the HTML into a Shopify page template + push to live theme → Claude uploads the images, deploys the files, and creates a published page No more handing designs off to a dev and waiting 2 weeks for a Shopify page. What you get: - A workflow that turns any Claude Design page into a real Shopify page template - Editable sections so your marketing team can swap copy, images, and CTAs without code - Images uploaded straight to Shopify Files automatically - A files-only deploy that only touches what's new in your live theme - A repeatable pipeline you can use every time you design a new landing page This is essentially the design-to-deploy pipeline brands have been waiting for. I put together a step-by-step playbook for going from Claude Design → published Shopify page. Every install, every plugin, every command, and the exact prompt that runs the whole thing. Want the playbook for free? > Like this post > Comment "SHOP" And I'll send it over (must be following so I can DM)

Mike Futia

56,183 Aufrufe • vor 2 Monaten

🧃 Introducing stereOS: a Linux based operating system hardened and purpose built for AI agents. It's clear that agents need an ACTUAL operating system (not what people are calling an "OS") to witness the full breadth and depth of their capabilities while mitigating the blast radius of autonomous, untrusted actors. But there are so many problems with AI sandboxes today: * Going out to the apple store and buying a mac mini will never scale and is way too expensive (obviously) * Running in Docker is too restrictive (agents can't stand up their own container infrastructure, no sub virtualization, docker-in-docker is very broken) * Firecracker strips all the hardware so GPU PCIe passthrough, secure boot, FIPs, etc. is out of the question. * Native VMs are too fat and the overhead of 1 agent per VM is too much. stereOS takes a different approach: it's a full NixOS system that you boot and then kick off agent sandboxes inside with gVisor + /nix/store namespace mounting. Each agent gets their own kernel and the /nix/store is read only by nature. Even if the agent was somehow able to escape the gVisor virtual kernel, they'd land on the NixOS system as the "agent" user! Not your actual hardware!! If you want to take a defense-in-depth approach, we support "native" agents that run at the system level kicked off by our `agentd` utility. These agents, on their own, can manage and kick off other sub agents using the internal sandboxing mechanisms. Today, we're open sourcing all of this: * stereOS: our purpose built Linux OS - * masterblaster: client utility to launch, manage, and orchestrate agents - * stereosd: the stereOS system control plane daemon - * agentd: the stereOS system agent management daemon - Give it a try, throw us a star, and let me know what you think 🧃⭐️

John McBride

150,334 Aufrufe • vor 4 Monaten

Stanford researchers did it again. They just built the agent-native version of Git. When an agent works on a longer task, the run builds up a lot of state. This includes files edited/created, a dev server, a database, installed packages, KV cache, etc. Say the agent is at step 10 and makes a mistake, maybe it misreads a traceback and rewrites a file that was actually fine. The tests start failing, and the run goes off track, although everything through step eight was correct. By default, the agent just tries to fix it, which creates more edits and tool calls. This burns more tokens and grows the context. The other options are a person stepping in to redirect it or restarting the whole run from step one. That's wasteful, because it pays for every model/tool call again and re-prefills the context. Moreover, since an agent's run is non-deterministic, it doesn't reproduce the same early steps anyway. The reason it's hard to just jump back exactly to a previous correct step and resume from there is that the trajectory is only a message log. It records what the agent said and which tools it called, but not the live state underneath. That state includes things like memory, open file handles, child processes, installed packages, /tmp, and KV cache. None of that is in the log. Git can version the files, but it doesn't snapshot the running process or the KV cache. Checking out step eight moves the files back, but the process is still sitting in step-ten memory with a cold cache. Shepherd is a runtime layer by Stanford that records the run as a trace of typed events rather than a flat log. Each agent-environment interaction becomes a commit, similar to Git, but it tracks the live run. Its commit includes the agent process and the filesystem together, copy-on-write, so a branch carries the actual state and not just the files. Going back to a previous step is then a single call that forks from that commit and continues from the exact state. The copy-on-write fork is roughly five times faster than docker commit, and because the prompt prefix through step eight is unchanged, the KV cache is reused over 95% on replay, so early steps aren't reprocessed again. Once the run can be forked, a meta-agent can sit on top and operate it. It watches the trace and reverts as soon as it looks wrong, before the bad write is committed. In practice, it's just Python calling fork, replay, and revert on the trace, rather than a separate control plane wired into the harness. Not everything is reversible though. Files and sandbox changes undo themselves, but a database write has no automatic undo, so it needs a matching undo step set up in advance. Something external, like a sent email or a real charge, can't be undone, so the supervisor's job there is to catch it before it fires. They tested this on a few public benchmarks. On CooperBench, where two agents work on the same codebase, adding a live supervisor took the pair-coding pass rate from 28.8% to 54.7%. It's still early and labeled alpha. The benefit mostly shows up when a run gets branched a lot over a heavy sandbox state, which is exactly where restarting wastes the most tokens and time. If Git was made to make file changes reversible, Shepherd is trying to do the same thing for a live agent run. Shepherd Repo: (don't forget to star it ⭐ ) That said, Shepherd reverts a bad step inside a run. The harness around it, the prompts, tools, and checks the supervisor relies on, still drifts across runs as models and dependencies change. Akshay wrote about making that harness repair itself, where a failing trace gets diagnosed, the fix is verified against the exact input that failed, and the failure is locked as a regression test so it can't recur. Read it below.

Avi Chawla

436,783 Aufrufe • vor 9 Tagen

It's been several months since I curbed my phone addiction and it is so profoundly noticeable that my happiness has dramatically increased. I completely dropped doom scrolling, the news, politics, brain rot, and limit social media to mine and my friends' posts only. All the general negativity on the internet is like living in a home where everyone argues and is upset, even if it doesn't involve you and you don't engage with it, just being exposed to it every day is mentally draining. It's subtle, it creeps up slowly, and you don't even realize how mentally taxing it truly is. Now imagine the feeling of living in a home where everyone is peaceful and laughs, the feeling is equally infectious. You can even test this out by watching Friends or The Big Bang Theory with and without the laugh track on YouTube; spoiler, it's painfully cringe without it. The effect surrounding vibes have on your emotions is so strong, and it's hard to notice most of the time. I now find myself having uncontrollable fits of laughter at least once a week, which used to be closer to once a year. It's important to note that the things triggering these fits of laughing were always there, the difference is that my perception has changed. It's figuratively like a laugh track is playing in the background and all of a sudden, everything is now funny. I'm not trying to preach and tell people how to live their lives, but it's something I felt compelled to share since it's helped me so much. The habit was hard to break because the algorithm is designed to adapt to every person and lock you in, but I did it by substituting the phone with other things I enjoy. Right now it's learning the guitar and swimming. I'm developing skills I've never had, and it only compounds the feeling of happiness.

Macie Jay

74,187 Aufrufe • vor 1 Jahr

OK, I have a definitive word on the CJ Abrams play from today's Pittsburgh Pirates at Washington Nationals game after talking with Elias Sports Bureau on this. This play will stay as a sacrifice fly. The originial ruling of NOT a sacrifice fly was for the exact same reason that I thought, which is that the infielder is not running into the outfield, which is year's past would have been correct As it was explained to me, in past years, an infielder had to be running almost in a straight line towards the outfield wall to be considered "running in the outfield". Here, since he is running, and he ends up further away from home (157 feet) than when he started (145 feet), this is going to count as a sacrifice fly. That definition is changing, in part from this play to help bring greater consistency, and to take some of the guesswork out of it (the argument that he is running into the outfield as opposed to more parallel). Now, folks all the time ask "why doesn't MLB publish the OS Manual" and I always say because it is a living document that can have the wording change, and the wording for this play will be modified to something like "more towards the outfield wall than towards home plate" to eliminate any confusion. The big key to this play is that he was running on a full sprint. Also, and this is helpful for me, but for all fly ball outs that score a run, Elias Saba reviews to ensure consistency. So, yes, it's a sacrifice fly, and now that I have that info from Elias themselves, that sort of settles this one. Sounds like the guidelines for this definition will be changing, either this season, or certainly for next season.

MLB Scoring Changes

48,872 Aufrufe • vor 8 Tagen

So, you wanna be a big shot, huh? Well, let me tell you a secret: the key to success is being consistent, even when it's super boring and the results take forever to show up. It's like waiting for paint to dry, but instead of paint, it's your dreams. And, spoiler alert, it's not all sunshine and rainbows - there's gonna be some serious discomfort involved. But, hey, that's where the magic happens, right? The thing is, most people give up because they're not seeing immediate results. They're like, "I did the thing, where's my prize?" Well, let me break it to you: the prize is in the process. Every small step you take, every tiny effort you put in, it all adds up. It's like putting pennies in a piggy bank - it doesn't seem like much at first, but before you know it, you've got a whole lot of pennies. So, here's the deal. If you want to be a great man (or woman, or whatever), you gotta be willing to put in the work. And I don't mean just going through the motions, I mean really putting in the effort. Because, let's be real, the only way to get better is to face the discomfort head-on and keep moving forward. And, hey, don't forget to enjoy the ride. It's okay to take a step back, look at how far you've come, and be like, "Whoa, I'm crushing it!" But don't get too comfortable - there's still a lot of work to be done. Anyway, that's my two cents. Have a great week, I guess. #Web3 #DeFi #Ethereum #StarkNet #Crypto #ETH #Bitcoin #BTC #zycot

Zycot_Marketing_Agency

22,061 Aufrufe • vor 9 Monaten

made my first fired alumina print! lightcell energy 🔆 maybe i’ll call it a “lattice flame tokamak” 😉 this is where the flame occurs, held in place like a smoke ring. it’s supposed to be where the hot air and fuel mix, with channels pointing inward along a torus. the flame rolls around mixing fuel air and salt, like a rolling vortex, like a smoke ring. i constructed the geometry like this, it’s a triply-periodic minimal surface (TPMS). this divides a cylinder into two interlaced volumes with minimal material and the maximal surface area. it’s a “Schwartz-Diamond” type minimal surface with a bias, in cylindrical coordinates. the TPMS divides a space into two interlaced volumes. if you delete the material dividing these volumes then this is where the fuel and flames with mix and the reaction will take place. in addition, on average the channels will be pointed in along the torus throughout, canceling momentum and holding on to a recirculation vortex, there a flame will remain lit and where sodium can mix in via salt conducted in via wall surface tension, like a wick, and evaporation. the TPMS curves in all dimensions, so it is quite resistant to thermal stresses, can relieve stain along any of its curves. and it has thin walls so it can easily diffuse gases during debinding and sintering. had a small collapse in the center (probably a singularity in the model, cylindrical coordinates) but fired it anyway and it sintered beautifully! i used the latest version of Hyperganic hydesign for the geometry and a Formlabs Form 4 in Alumina 4N to do the printing. 💁🏻‍♀️☸️

Danielle Fong 🔆

28,549 Aufrufe • vor 1 Jahr