Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

SONY DIDN'T KILL DISCS. IT COUNTED THEM TO DEATH sony's public case rests on one number: 85% of purchases, by its own latest count, are already digital. the number is real. the trick is who it erases. the data below: alinea analytics' estimates. - the 85% includes every game...

74,863 görüntüleme • 2 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

These are the brakes responsible for stopping a Bombardier CRJ900, an aircraft that can weigh more than 38 tonnes at takeoff. Unlike the single discs on a car, each main wheel uses a multi-disc brake stack. Hydraulic pistons squeeze alternating rotating and stationary discs together, converting the aircraft's kinetic energy into enormous amounts of heat. At around takeoff speed, a fully loaded CRJ900 carries roughly 100 mega-joules of kinetic energy, with just four main wheel brakes responsible for absorbing a substantial part of it during a rejected takeoff. The real engineering challenge isn't generating enough friction, but surviving the extreme heat. The discs experience repeated extreme heating and cooling cycles, gradually wearing away the friction material. A complete set of four CRJ900 brake assemblies can cost roughly $280,000-300,000 in new brake pads and hardware. If we scale this to the Airbus A380 and it gets even harder to comprehend. At up to 575 tonnes, the world's largest passenger airliner has 16 braked main wheels using carbon brake stacks. Those assemblies represent roughly $2.5-4 million worth of brake hardware. Airlines don't replace all of them together at a fixed number of landings each brake is wear monitored and changed or overhauled individually. At maximum braking, these brakes absorb so much energy in just seconds that the discs can glow red hot, approaching 1,000°C all while bringing hundreds of tonnes of aircraft safely to a stop. Source, Aviation Tech

Ammanichanda

17,241 görüntüleme • 12 gün önce

The largest theft in history has already happened. The people behind it just cannot open what they stole yet. Right now, intelligence agencies and criminal groups are quietly copying the world's encrypted data, bank records, medical files, state secrets, private messages, and storing every byte untouched. They cannot read any of it. They are collecting it anyway, because they know the key is about to be invented. The strategy has a name, harvest now, decrypt later, and in 2026 it stopped being theory. Washington declared this the Year of Quantum Security in January, backed by the FBI, the NSA, and NIST. Canada ordered every federal agency to file a migration plan by April. Europe set its deadline for December. Governments do not impose operational deadlines on a someday problem. They do it when the clock is already running. Here is what moved the clock. Every password, every transfer, every secret on Earth is protected by one assumption, that a certain math problem is too hard to solve. Quantum computers solve exactly that problem. For years the machine that could do it looked decades away. Then in late 2025 Google's Willow chip cracked the hardest part of building one, and in March 2026 Google's own researchers estimated that breaking the encryption behind Bitcoin might take fewer than 500,000 qubits, down from 20 million, and could run in minutes. The day this becomes real has a name, Q-Day, and the latest estimates place it between 2030 and 2033. Now make it concrete. Roughly 6.5 million Bitcoin, about a third of every coin that will ever exist, worth close to 500 billion dollars, sit in addresses that have already exposed the very key a quantum computer needs. That includes the coins of Satoshi, the anonymous creator. On Q-Day they become, in the researchers' own word, trivially stealable. It would not look like a crash or a whale selling. It would look like half a trillion dollars of the most secure money ever built simply walking out the door. The asset designed to trust no one and no institution turns out to rest on a single unverified bet, that one math problem stays hard forever. This is what sits beneath the entire digital world. A bank balance, a Bitcoin, a classified cable, all of it is real only because of a proof you supposedly cannot forge. Quantum breaks the proof. Everything we call secure is true only until someone finally checks, and for the first time the check is visible on the horizon. You cannot know whether your data has already been copied. You cannot know the exact day the key arrives. The trust holding up the digital age is a clock counting down to a zero no one can see. The honest counter matters. No machine on Earth can break this encryption today, and serious cryptographers still argue the real threat is a decade or more away. The timeline is far from certain. Quantum-safe codes already exist, the migration has started, and Bitcoin can move its coins to safety before Q-Day if it acts in time. The danger is not that everything breaks tomorrow. It is that anything which must stay secret into the 2030s, a state secret, an identity, a private key, is being stolen today and is already on the clock. The breach is not coming. It is already here, sitting in storage, perfectly encrypted, waiting for a machine that does not exist yet to read it out loud. Research and opinion, not investment advice.

Shanaka Anslem Perera ⚡

185,548 görüntüleme • 2 ay önce

this is worth more than most five figure courses 16 claude agents audit an entire repo at once, a second fleet re-checks every finding on fresh context, and the whole thing runs off one diagram instead of a prompt i ran it against my own code and got back 11 endpoints where i never checked who was logged in, 3 of which the verifier threw out before they ever reached me this is Graph Engineering, the layer above prompting, and it runs on the agent you already pay for: - write your plan out, then ask one question at every "and then": does the next step actually read what the previous one produced - the seams that fail that question were never dependencies, so those jobs run at the same time - the arrows that survive are your real edges, and the longest chain of them is your floor that no number of agents shortens - want it faster, cut a false edge instead of adding a worker - fan the independent work out, one agent per item, no shared state between them - send every finding to a separate agent on fresh context, because a model recognises its own writing 73.5% of the time and grades it kinder once it does - make that verifier check a real signal like a passing test, never the worker's own word that it finished - shard the fleet across worktrees so parallel workers stop overwriting each other, one rule frozen into every worker: never git stash, never git reset - merge only what came back verified, into one report instead of twenty open chats the catch is the ceiling. at 95% independent work 16 agents return 9.14x rather than the 16 you would guess, and even 256 only reach 18.6x, because the merge and the verify stay serial however wide you fan coordination itself is free plain code and every agent underneath it is billed, so start at twenty files and widen once it works bookmark this, the whole method with all six ready-to-run graphs is written out in the article ↓

Argona

157,312 görüntüleme • 1 ay önce

this is more useful than my entire degree Elon Musk's rocket company signed a $60,000,000,000 deal for Cursor in June, and eight days ago the two of them put a worker on sale for $200 a month: it gets its own computer in the cloud, signs into your accounts, clicks through your real apps, and hands back finished work instead of a draft for you to paste i ran one against my receipts folder on sunday and got back 14 filed, 2 it held because they needed a card number, and a saved method i never wrote myself Grok Bot is the one you train by doing your own job in front of it, and the whole handover fits in four messages tonight: 1. write out one job you did today the way you would brief a new hire: what has to be finished, which sites and files to work from, what to hand back, and where it stops and asks you 2. let it run once on something safe to get wrong, then correct the result until it is worth your name 3. say "save what we just did as a skill", and add the one rule about what always needs your approval 4. say "run that skill every weekday at 8 and post the result here. if the source is missing, tell me instead of using yesterday's numbers" xAI wrote that order into its own manual: one real job, then the saved method, then the clock. a schedule sitting on top of a method nobody checked replaces two hours of your clicking with two hours of your mistake turns out you never get to pick the brain, and that is the part i would argue about: the manual says there is no model picker for members or admins, no plan to add one, and the bill follows whichever model answered bookmark this, then open the piece below: which jobs deserve a worker of their own, and which ones quietly burn the seat ↓

Argona

21,946 görüntüleme • 1 ay önce

I deleted all my Polymarket positions at 2am on a Tuesday because I realized I was winning 54% of my bets and still down $11,400. It took me three weeks to understand that sentence. Fifty four percent wins. Why is the balance shrinking? The math was brutal once I finally saw it. I was buying outcomes at 55 to 65 cents feeling smart because my picks kept winning. But the payout at those prices was so thin that one loss wiped out five wins. My edge was maybe 3% and the spread was eating 4%. I dug into the data hoping to find a way to trade better and instead found a number that made me want to close the app. 70% of all Polymarket addresses are in the red. And the profits? Captured by 0.04% of wallets. Four thousand addresses out of 1.7 million own almost everything. I was playing a game where 96% of participants exist to fund the other 4%. But the trades of those wallets are public. Every entry, every exit, sitting on the blockchain. I started tracking them manually. One wallet broke me. It started January 6 with $50. By the time I found it the balance was close to $500,000. Pulling $20 to $30K a day on 15 minute BTC, ETH and SOL markets, exploiting the fact that Binance updates faster than Polymarket odds. A few seconds of lag, hundreds of times a day. I scrolled its history for an hour trying to find a losing streak. Could not. That is when I stopped doing this by hand. Set up PMX. Alerts the second a tracked wallet moves, one tap copy. → Link to bot: Three weeks of shadowing instead of trading. Made back $4,200 of my $11,400 hole. Not because I got smarter. Because I stopped pretending I was the edge. The game on Polymarket is not about being right. It is about standing behind someone who already is. I am still not in profit. But for the first time in four months my balance moves the right direction and I sleep through the night. That is worth more than any win.

Blaze

13,874 görüntüleme • 7 ay önce

Sold 32 coins. Bought 1,550. 48 times more, at a 15% discount, into the crash the market blamed on the sale. Strategy disclosed today that while everyone panicked over its $2.5 million Bitcoin sale, it was quietly buying the dip that panic created. 1,550 Bitcoin for $101 million, at $65,332 a coin, far below the $77,135 it sold for and below its own cost basis. The bears called the sale the first crack, a forced liquidation, the start of the death spiral. The answer was a buy 48 times the size of the sale that scared them. This is the machine we described: a state-contingent allocator. Above its funding line, it turns market access into Bitcoin. The sale was the exception. The buy is the rule. It also closed the question the sale opened. The cash reserve behind the preferred dividends had thinned to $900 million, about six months of cover. He rebuilt it to $1 billion in the same week. But watch how, because that is the real story. He funded none of it with coins. He funded it with $181 million of freshly issued stock, then spent it on Bitcoin and the reserve. The coins were never the funding source. The equity is. That is the flywheel working exactly as built, and the cost of it surfacing at the same time. Every turn now runs on issuing shares, and the premium that once made each share buy more Bitcoin than it diluted has compressed hard. He bought low. He sold his own stock low to do it. So the question quietly turns. It was never whether Saylor sells his Bitcoin. He just proved again that he buys far more than he sells. It is what each turn of the engine now costs in dilution, and how long the market keeps paying a premium worth that cost. He bought the dip. The dip was partly his own making. And he paid for it in equity, not coins.

Shanaka Anslem Perera ⚡

142,587 görüntüleme • 3 ay önce

sorry, they just did WHAT someone gave a machine one disease name, the leading cause of blindness in the developed world with 1.5 million americans already in its path, and it came back pointing at a drug that has sat in pharmacies for years under a different label: 551 papers read in 30 minutes against the 294 hours a human would have needed, and the loop that did it is public on GitHub most agent setups answer one question at a time, so the ceiling on the work is the quality of the question you happened to think of this one was handed a single question and wrote the second one itself. turns out that follow-up is where the real find was: a target called ABCA1, upregulated threefold, in an experiment no human ordered i read the whole paper looking for the trick, and the trick is structural. that is the second question, and it is the gap between an assistant and a factory: - hand the loop a field rather than a task: it was given a disease, and choosing the mechanism was part of its job - make it rank before it spends: 151 papers in, ten candidate mechanisms out, scored against each other before anything touched a bench - split reading from judging, so the agent that forms the theory is a different agent from the one grading it - close every cycle on physical reality: the verdict was an experiment, and another model's opinion was never allowed to stand in for one - feed each result back as the next question rather than a log line, which is the step almost nobody builds - search what already passed inspection first: the winner was an approved compound with a safety file already on record - write down what the round learned before opening the next one, so round two starts where round one stopped my read, and i think it is the uncomfortable one: reading was the entire bottleneck in that field, and everybody spent the decade optimising the writing. people ran every physical experiment here, the analysis agent needs a domain expert writing its prompts, and the authors decline to call this the leap it resembles. the thinking got replaced, and the hands did not so the question i cannot answer for my own setup: which step of your loop still stops dead until you sit down and type something bookmark this one. the four parts that turn one model into a line that runs like this, the queue, the rooms, the write permissions and the gate, are built file by file in the piece below ↓

Argona

32,475 görüntüleme • 1 ay önce