Sensitive content

This media may contain sensitive content.

Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Open Commissions for YCH Animation (Only 3 slots available at $30 each) You can request: - Customize models (skin color, smooth anatomy, accessories) - No models required - MD interested #murdedronesnsfw #UziDoorman #SerialDesignationN #nuzi

11,929 görüntüleme • 1 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

AI models currently have a 50% chance of doing something that takes a human expert one hour. This doubles every 7 months. In 2 years? They could automate full workdays. In 4 years? A full month. I discuss the most important graph in AI today with Beth Barnes, the CEO of METR, which uncovered this rule of AI progress. Her bottom line: "It really doesn't seem like 2 years would be surprising for recursively self-improving AI." Beth also explains: where company safety testing fails, why there are no true closed-weight models, AI undermines leading powers, why she's come around on open weighting, and why models might be about to start playing dumb much more often. Enjoy! Available on the 80,000 Hours Podcast in all apps. Links below. 1:51 Can we see AI scheming in the chain of thought? 12:50 Alignment faking 17:33 We have to test models before they're even used inside AI companies 31:56 Each 7 months models can do tasks twice as long 51:31 METR's research finds AIs are solid at AI research already 58:18 AI may turn out to be strong at novel and creative research 1:07:55 Recursively self-improving AI might even be here in two years 1:14:29 Could evaluations backfire? 1:39:55 Do we need external auditors doing AI safety tests? 1:54:09 Why not work at AI companies 2:08:40 The new more dire situation has forced changes to METR's strategy 2:21:49 Overrated: Interpretability research 2:32:55 Overrated: Major AI companies' contributions to safety research 2:39:15 Could we ban using AI to enhance AI, or is that just naive? 2:45:31 Open-weighting models is often good 2:50:22 What we can learn about AGI from the nuclear arms race 3:10:43 AI is more like bioweapons because it undermines the leading power 3:42:09 What research METR plans to do next

Rob Wiblin

93,669 görüntüleme • 1 yıl önce

I vibe coded and built a sprite animation pipeline 🛠️ (Day 22 of making the engine+game) ⬇️ Watch the video if you don't wanna read the wall of text - it directly shows what I do. Shoutout to Jidé ✨ for showing me a paper on black/white combination to get alpha, it's the cleanest method yet, and to Cursor for enabling this entire journey. If you prefer the wall of text here you go: The hardest part of using general image models for 2D sprites isn’t getting a nice-looking frame, it’s getting consistent motion across a whole sprite sheet. You can fake a sheet, but frames won’t align, timing drifts, and you end up with weird artifacts. Even if you manually cut frames + interpolate, the animation often looks “off” because each frame is basically a new interpretation, not the same character evolving over time. This is especially noticeable with public API models like gpt-image-1.5 and Nano Banana. Some custom LoRAs for open models exist, but this is intended for less techy folks. My workaround: use a video model first, then post-process into a sprite sheet. Render the animation over a solid background (white/black/magenta/green), then chroma-key it out (my engine tool supports this). If the motion stays inside the silhouette, this works surprisingly well. You can do this in almost any video editing software too! The catch: keying almost always leaves an “aura” (edge spill). My best results come from interpolating the keyed animation with a clean base sprite, so you keep crisp edges and only “borrow” motion/detail where needed. If the animation extends outside the silhouette (tree branches, hair wisps, foliage), I usually skip “true sprite animation” and do it with shaders instead. Keying can’t fully remove halos there, no matter how much feathering/tuning you do. Another annoying issue: pixel corruption. AI rarely generates a perfectly flat background (pure #000000 or #FF00FF). That tiny noise breaks clean extraction and creates crawling garbage pixels around the subject. For clean base sprites (and even PBR maps), a useful trick is generating the same asset on white + black backgrounds and deriving alpha from the difference. This is basically a matte workflow: white = opaque, black = transparent. It fixes aura… but you’d need it per-frame to fix animation, which is still hard. For simple pixel art (single-digit frames), you can sometimes generate a sprite sheet, then ask the model to recreate it on black/white while preserving alignment… but it’s still manual-heavy. Honestly, at this point, for some projects it’s easier to go 3D → 2D and render clean sprites/maps directly. But I still love pushing “pure 2D” and seeing how far we can take it. Thanks for reading! Follow/bookmark/repost if interested in this kind of content!

Startracker 🔺

20,181 görüntüleme • 7 ay önce

🎬Whimsical Reverie | Furniture Preview 🛋️Home Sentiments In celebration of the Home system's launch, stylists can obtain free furniture items via the [Home Sentiments] event after the Version 1.9 update on September 1, 2025 (UTC-7). When the event starts, unlock 1 free furniture piece each day. The event lasts 3 days—claim up to 3 free items in total! The event has 3 rounds, giving you plenty of chances to decorate your home! 🛋️Dreamland Showcase Stylists can earn Dreamland Stones by completing weekly Chronicle Tasks. Dreamland Stones can be used to exchange for items in the Dreamland Shop, including the [Detective's Study] series of furniture and Diamonds. Spend 680 Stellarites to sign the [Dreamland Pact]. Once signed, you can instantly claim the new furniture [Loving Fufu & Flowers] and its Furniture Sketch. Complete the current Chronicle Tasks to earn bonus Dreamland Stones. After signing the [Dreamland Pact] and accumulating a certain number of Dreamland Stones in this phase of Dreamland Showcase, 680 Stellarites will be refunded. You can claim the Stellarites in Dreamland Pact interface. 🛋️Chorus of Stars Purchase the "Stellar Poems Pack" for 1,480 Diamonds to receive 12 types of Diamond-purchased furniture and 8 types of Astralite exchangeable furniture, totaling 20 types and 38 pieces. This pack can only be purchased once. Each type of furniture can be purchased separately with no purchase limit, but it will not be available at the discounted set price. 🛋️Furniture Set Series Purchase the "Leisure Tea Brewing Set I" for 680 Stellarites to receive 6 types of furniture, totaling 14 pieces, including the [Eternal Years Screen]. This set can only be purchased once. Each type of furniture can be purchased separately with no purchase limit, but it will not be available at the discounted set price. Purchase the "Leisure Tea Brewing Set II" for 420 Stellarites to receive 6 types of furniture, totaling 11 pieces, including the [Twilight Incense Burner]. This set can only be purchased once. Each type of furniture can be purchased separately with no purchase limit, but it will not be available at the discounted set price. Purchase the "Leisure Tea Brewing Set III" for 180 Stellarites to receive 3 types of furniture, totaling 8 pieces, including the [Rolling Screen]. This set can only be purchased once. Each type of furniture can be purchased separately with no purchase limit, but it will not be available at the discounted set price. 🛋️Stargazing Reveries Purchase the [Astral Radiance Pack] to receive selected furniture pieces such as [Stellar Cascade], [Echo Waterwheel], and [Seasons Couch]. These selected items are tagged as both "Home Furniture" and "Decoration," and may be placed in your Home or in Miraland. The set is limited to one purchase. If you prefer to buy items individually: [Stellar Cascade] is available for purchase, [Seasons Couch] for 680 Stellarites, and [Echo Waterwheel] for 450 Stellarites. Individual pieces of furniture can be purchased with no purchase limit. —— The Coziest Open-World Game! Infinity Nikki Version 1.9 "Music Season" launches globally on September 1st (UTC-7)! ➤ Download Now: ➤ Join us on Facebook Group: #InfinityNikki

Infinity Nikki

43,003 görüntüleme • 1 yıl önce

Today, I'm releasing the first eval meant to test whether frontier models will help with authoritarian requests, or resist--the Dictatorship Eval. Headline finding: while some models resist direct authoritarian requests, they all comply with requests disguised as innocuous edits to codebases. As AI is woven into the government and so many parts of society, the biggest near-term risk for freedom isn't some scifi dictatorship of a runaway AI: it's people inside government or inside model companies using the technology to suppress or control us. Model companies understand this, and several of them (particularly Anthropic and OpenAI) have written explicit policies meant to prevent the models from going along with nefarious requests like these. But how well are these policies playing out in practice? Despite all the recent discussion of these issues around the conflict between Anthropic and the Pentagon, no one has systematically tested what the models actually do in these contexts, as opposed to what people in government and industry say they're supposed to do. That's what the Dictatorship Eval does. And the findings suggest we have a lot of work to do to align the policies with what really goes on in practice. It's hard to define what counts as an authoritarian request, so I'm open sourcing the whole library of scenarios I used so that others can improve on them. It's also hard to get an accurate picture of how the models might be used for authoritarian ends, because I can only test hypothetical requests using public-facing models, while the government and the model companies can obviously use internal models with different guardrails. But hopefully this work is a useful first step that gives us some sense of what's going on, and a sort of "lower bound" on how models comply with these requests. Finally: it's not obvious to me that the correct solution here is increasing the rate at which models refuse these requests. Do we really want models scanning our code and judging its moral value before agreeing to help us? Or should we double down on improving how we govern against authoritarianism at the societal level, while leaving the tools open to fulfilling most requests? The answer is probably in between. Just like we don't want the models to help create bioweapons, we probably do want them to explicitly refuse outrageous requests. But we probably also want to limit how often and how strongly they refuse and fall back on other means for guarding against their use for authoritarian ends. I'm super grateful to everyone who gave me feedback on this project along the way, especially Ethan BdM , Zhengdong , Connor Huff, and a bunch of folks at Anthropic. Looking forward to getting feedback from the community and iterating on this. Links to the full piece and the dashboard are below.

Andy Hall

33,905 görüntüleme • 5 ay önce

NOBODY wants to send their data to Google or OpenAI. Yet here we are, shipping proprietary code, customer information, and sensitive business logic to closed-source APIs we don't control. While everyone's chasing the latest closed-source releases, open-source models are quietly becoming the practical choice for many production systems. Here's what everyone is missing: Open-source models are catching up fast, and they bring something the big labs can't: privacy, speed, and control. I built a playground to test this myself. Used CometML's Opik to evaluate models on real code generation tasks - testing correctness, readability, and best practices against actual GitHub repos. Here's what surprised me: OSS models like MiniMax-M2, Kimi k2 performed on par with the likes of Gemini 3 and Claude Sonnet 4.5 on most tasks. But practically MiniMax-M2 turns out to be a winner as it's twice as fast and 12x cheaper when you compare it to models like Sonnet 4.5. Well, this isn't just about saving money. When your model is smaller and faster, you can deploy it in places closed-source APIs can't reach: ↳ Real-time applications that need sub-second responses ↳ Edge devices where latency kills user experience ↳ On-premise systems where data never leaves your infrastructure MiniMax-M2 runs with only 10B activated parameters. That efficiency means lower latency, higher throughput, and the ability to handle interactive agents without breaking the bank. The intelligence-to-cost ratio here changes what's possible. You're not choosing between quality and affordability anymore. You're not sacrificing privacy for performance. The gap is closing, and in many cases, it's already closed. If you're building anything that needs to be fast, private, or deployed at scale, it's worth taking a look at what's now available. MiniMax-M2 is 100% open-source, free for developers right now. I have shared the link to their GitHub repo in the next tweet. You will also find the code for the playground and evaluations I've done.

Akshay 🚀

50,323 görüntüleme • 9 ay önce