#Blizzard, hear me out! Here’s a proposal for #WoWForever to solve WoW’s gold inflation problem permanently! Almost every version of WoW eventually runs into the same problem: the gold supply keeps growing without any hard monetary limit. Over time, this inevitably creates inflation. Gold loses purchasing power, prices rise, and new or returning players enter an economy where veteran players have accumulated wealth for years. There is a simpler solution: Give every server a hard, fixed gold supply. For example: 100 million gold total. Forever. Think of it as the server’s monetary base. Gold dropped by mobs would no longer be newly created. Instead, mobs would distribute gold from a global server pool. The amount of gold mobs drop would dynamically depend on how much gold is currently available in that pool: • Lots of gold in the pool → mobs drop more • Little gold in the pool → mobs drop less Gold spent by players flows back into this pool and can then be redistributed through gameplay. NPC purchases such as skills, professions, repairs, mounts, etc. would return 100% of the spent gold to the server pool. Trading systems like the Auction House could also recycle part of the circulating gold back into the pool through transaction fees. This creates permanent circulation instead of permanent monetary expansion. NPC prices should also be dynamic. If a large percentage of the total gold supply is being held by players and very little gold is actively circulating, prices for essential services like skills and professions should decrease. That prevents new players from being priced out simply because veteran players are sitting on large gold reserves. The game economy would continuously adapt to the purchasing power and availability of gold. Over the very long term, the general price level might gradually decline, potentially resulting in mild persistent deflation. But that wouldn’t necessarily be a problem if the game world itself dynamically adjusts to the purchasing power of gold. One possible consequence of persistent deflation is that players may initially hoard gold. Imagine someone accumulates a large amount of gold, stops playing for three years, and then returns. Because prices have fallen in the meantime, their old savings could suddenly have significantly more purchasing power. But this effect is naturally self-correcting. The moment that player starts using that increased purchasing power, the saved gold begins circulating again. They get the benefit of having saved, as they should, but once they spend it, that purchasing power is transferred to other players and gradually redistributed throughout the economy. In other words: hoarding can temporarily concentrate purchasing power, but spending automatically starts reversing that concentration. The important part is: Gold would finally become truly scarce. No endless monetary expansion. No inevitable long-term inflation. No need for increasingly absurd gold sinks every expansion. Just a closed monetary system where the same gold continuously circulates between players, NPCs, and the game world. For a version of WoW designed to exist forever, its currency should be designed to exist forever too. @Warcraft @Blizzard_Ent @Warcraft_DE

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 – security.muse.ai. 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.

A tiny demo of what I am gonna show today at genmedia conf from @fal wiht h3 max director and reference to video, and also possible link with robotics (more to come about that and other models used) All the code will be available at the end of the day on my X

Deepseek Harness Now Has Image and Video Generations Built in with Qwen 2.1 and Minimax H3

the jev release is giving react major version drop vibes. just a massive crashing wave, everyone rethinking fundamental stuff and thinking through the implications of a novel new primitive. wonderful.

Can we all just pause for a sec and reflect on how fucking important Tailscale is, and how nobody ever talks about them? I don't think I've ever seen a more useful service with a more invisible corporate footprint.