Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

New open source library: kugiri (区切り). Already running in production on several of my sites, now public. It splits text into lines, words and characters, the thing every text reveal needs. The difference is where it cuts. Most splitters guess where a line breaks, and the guess falls apart...

42,898 görüntüleme • 6 gün önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

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

As of this morning, every brand-new Car sold in Europe is mandated by law to watch its “driver”, and the reason to worry is the opposite of what everyone is screaming about. The camera is not filming your face. The law explicitly bans that. It rather tracks your eyes. The danger is not what it does today. It is what it is now physically positioned to do tomorrow. This became binding across all 27 countries today, the 7th of July 2026, and no member state can opt out, because road safety is an EU competence and EU law overrides national law. Every new car and van, roughly 18 million of them a year, must now carry an infrared camera, usually on the steering column, that follows the driver's gaze. Look away too long, six seconds under 50 kilometers an hour, three and a half above it, and the car warns you with a sound, a light, or a buzz in the seat. The stated reason is real. Distraction causes up to 30 percent of crashes, and the Commission projects the wider safety package will save 25,000 lives by 2038. The outrage dissolves on contact with the actual text. The law actually fully forbids facial recognition and any biometric identification of anyone in the car, and the footage is legally barred from leaving the vehicle. No recording, no transmission, no police feed. As written today, this is a safety beeper, not a spy. But look at what already sits beside it. Think about it.. come on!! Europe's cars already run always-on systems that do transmit, the automatic crash caller that dials emergency services, the black-box event recorder, and over-the-air software that rewrites the car remotely overnight. The sensor was just made universal. The wall keeping it private is a single legal paragraph, and the same law already schedules its own review for 2027 to read cognitive state and body movement, while suppliers openly sell using the identical mandated camera to watch the passengers too. So this is the quiet architecture of every threshold. The permanent thing is physical, a camera now bolted into 18 million dashboards a year. The thing protecting you is a mere sentence, and sentences are the easiest part of any system to revise. Europe hardwired the eye. It left what the eye may see as the one part that can still be changed later. Hmm 🤨

Shanaka Anslem Perera ⚡

650,189 görüntüleme • 2 ay önce

I just built a Meta ad policy checker in Claude Code that catches rejections BEFORE Meta does 🤯 Drop in your ad copy → it pulls Meta's LIVE Advertising Standards, checks every line against the actual policy text, and hands each ad a verdict: Cleared for launch, Fix before launch, or Grounded. All inside Claude Code. Perfect for media buyers and DTC brands who've had ads bounced — or an account restricted — and never got a straight answer why. If you're finding out about policy problems only after the rejection email, resubmitting the same ad and praying, losing days of delivery while the appeal sits in review, and every bounce quietly teaches Meta to trust your account a little less... This runs the review before Meta ever sees the ad: → Drop in your ad copy (one ad or a whole batch) → It reads each ad and figures out which of Meta's policies apply → Scrapes the live policy pages from Meta's Transparency Center → Flags the exact phrase that violates, with Meta's own policy quoted next to it → Rewrites the risky lines so the message survives but the violation doesn't → Renders a dashboard: every ad, every finding, every fix in one place No guessing which word killed the ad. No resubmit-and-pray loops. No stacking rejections on your account history. What you get: → A verdict on every ad before you spend a dollar → The violating phrase + the policy citation, side by side → Rewrites that keep the selling intent → A report you can hand straight to your team or client Built 100% in Claude Code. No API keys, no Meta login. I'm giving away the complete Claude skill file. Want the skill for free? > Like this post > Comment "META" And I'll send it over (must be following so I can DM)

Mike Futia

17,467 görüntüleme • 1 ay önce