MA guy on X just declared every smartphone on the market does the exact same thing.
CWell, when you put it that way, the entire industry can pack up and go home.
MHis name's Big Sam, and he says the S26 has a 200 megapixel camera, but that's the whole difference.
CAnd this is one of those moments where the internet yells at a stranger for being slightly wrong.
MBecause that 200 megapixel claim? Hard to square with the spec sheet I've seen for the regular S26, which lists a 50 megapixel main camera.
CSo we have a man who says all phones are identical, and he's already misidentifying the one feature he says matters.
MThat's the energy of the take. Vague enough to feel true, wrong enough to matter.
CBut I'll actually defend the spirit of it. A lot of people aren't upgrading for cameras anymore.
MThey're not. The mid-tier phone crisis is real. Everyone's chasing the same slab.
CSame slab, same apps, same AI assistant reminders. The differences have gotten small.
MSmall, but not zero. Folding phones, battery tech, the way the thing feels in hand.
CBut come on, most people put a case on it and open the same four apps.
MSo we agree the take is half-right, but his camera fact is just wrong. That's the show.
CThe show is correcting strangers online. We should get t-shirts.
MSpeaking of phones everyone's debating— a hardware guy named CID posted a mockup of a wide Galaxy S and iPhone hybrid.
CA wide phone? Like a small tablet you can barely wrap your hand around?
MThat's exactly what he's asking for. He says the form factor needs to exist, and honestly, it stops me.
CIt stops you because it's absurd. Who wants a phone the width of a passport?
MPeople who read. People who watch video. People tired of tall skinny phones designed for scrolling feeds.
CThe tall phone is tall because of the keyboard, Matilda. It fits in a hand and a pocket.
MBut a wider screen shows more of a document, more of a webpage. It's basically a mini foldable without the fold.
CIt's a mini tablet with a phone baked in. Hand it to a normal person and they'll drop it in a week.
MYou're thinking too small. Think of the people with big hands, or the people who two-thumb type with actual space.
CSome makers tried wide phones in the early touchscreen days, and the reviews mostly said the same thing: awkward.
MBut the market has changed. People used to want one-hand use. Now people want a media slab.
CAnd what, carry it in a fanny pack? A shoulder holster? This is a solution to a problem nobody has.
MI think it's more interesting than another spec bump. At least it's a real attempt at a different shape.
CI'll give CID this: the mockup does look clean. But we both know it would flop.
MOkay, moving from pocket battles to file systems. A developer named storagebits built a whole interactive museum for ZFS.
CA museum? Like exhibits and little plaques? For a filesystem?
MGenuinely. Animated diagrams of copy-on-write, transaction groups, RAID-Z, snapshots, the whole thing.
CI've used ZFS for years. The data integrity stuff is still the closest thing storage nerds have to a religion.
MHe says he built it to understand ZFS better, and to pay homage to the engineering.
CThat tracks. ZFS people are intense. There's a reply from a guy running it on FreeBSD, Linux, and macOS all at once.
MThe cross-platform devotion is something. And another commenter complains the ARC cache makes sendfile not zero-copy.
CNow that's the good stuff. Content delivery networks care about zero-copy the way car people care about cylinder count.
MSo this museum might actually teach real working engineers something, not just the curious.
CThe internet runs on ZFS. Your backups, your NAS, half the big storage appliances. A museum for it is almost overdue.
MAnd it's interactive, so you can click through the write path and see where the ZIL and ARC actually sit.
CI respect the madness of it. Most people build a blog post. This guy built a museum.
MMeanwhile, on the fight-against-robots front, someone built a WordPress plugin to replace CAPTCHAs with proof-of-work.
CHashcash. The old email spam idea. Make a bot burn CPU time instead of solve a puzzle.
MThe developer, Matthias Nordwig, says he wanted no cookies, no tracking, invisible for visitors, and no running costs.
CThat's actually a good pitch. CAPTCHAs are getting hostile for actual humans. The little traffic lights.
MBut proof-of-work moves the cost to the visitor's device. Battery and CPU, instead of annoyance.
CIt's a trade. A tiny bit of compute for no tracking. For a whistleblower service, privacy is the whole point.
MAnd the plugin sits on your own web server, so nothing goes through a third party. That matters.
CThe question is whether legitimate users feel it. If it's a second of CPU, fine. If it heats up a phone, people leave.
MFor low-traffic sites, it's probably great. For a media site with millions of readers, every visitor mining a tiny puzzle adds up.
CBut the alternative is people squinting at crosswalks, or worse, letting Google's CAPTCHA system track them across the web.
MI'm on the side of the quiet plugin. The fewer times I click a bus, the better.
CI just don't want my phone to become a space heater because a comment section decided I'm a bot.
MAnd that's the tension. Privacy is a tax. The question is who pays it.
CThe robots, presumably. That's the point of the thing.