HNHacker News
TopNewBestAskShowJobs

georgia_peach

423 karma · joined February 9, 2022

submissionscomments
georgia_peach··on Pornhub: Judge rules Visa can be sued in abuse claim
Can't speak for matheusmoreira, but I think Visa should handle payments & law enforcement should handle diddlers. Turning payment processors into an extra-judicial enforcement system on top of the existing one is a mess in so many different ways (jurisdiction, lack of due process, arbitrary enforcement, financial motives, conflict of interest, lack of transparency, etc...).
georgia_peach··on Pornhub: Judge rules Visa can be sued in abuse claim
Money, probably.
georgia_peach··on Pornhub: Judge rules Visa can be sued in abuse claim
Visa cut off Gab.com, on their own initiative, for incidentally carrying posts by the Pittsburgh shooter. Why didn't they exercise the same judgement against PornHub for incidentally carrying vids of child sexploitation?

They opened themselves up to this line of legal reasoning.

georgia_peach··on TI-83 Plus One More
I remember when these started taking over. Last semester's calculus class became next semester's "calculator" class. Okay for a few budding programmers; an educational decline for everyone else. And I never understood the programming appeal. Circa 1996, a thrift-store commodore was still a cheaper & better programming experience.

I was also fairly pissed about having to pay $100+ on a calculator which was wholly unnecessary for learning "area under the curve" and "slope at a point". College is such a shakedown.

georgia_peach··on Review of 17α-ethynylestradiol in water across 32 countries: Estrogenic effects
This is a diversion, not a direct answer to the question asked.
georgia_peach··on Review of 17α-ethynylestradiol in water across 32 countries: Estrogenic effects
Ideology doesn't factor into this. There is something in the water that shouldn't be there, and someone put it there---largely without permission. And what constitutes a "low dose" frequently changes by several orders of magnitude depending on who does the study, and who paid for the study.
georgia_peach··on Climate is now core to Rockefeller Foundation mission
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC1653469/pdf/amj...
georgia_peach··on The WHO gets hysterical about Monkeypox
> We report 528 infections diagnosed between April 27 and June 24, 2022, at 43 sites in 16 countries. Overall, 98% of the persons with infection were gay or bisexual men, 75% were White, and 41% had human immunodeficiency virus infection; the median age was 38 years. Transmission was suspected to have occurred through sexual activity in 95% of the persons with infection. In this case series, 95% of the persons presented with a rash (with 64% having <10 lesions), 73% had anogenital lesions, and 41% had mucosal lesions (with 54 having a single genital lesion). Common systemic features preceding the rash included fever (62%), lethargy (41%), myalgia (31%), and headache (27%); lymphadenopathy was also common (reported in 56%). Concomitant sexually transmitted infections were reported in 109 of 377 persons (29%) who were tested. Among the 23 persons with a clear exposure history, the median incubation period was 7 days (range, 3 to 20). Monkeypox virus DNA was detected in 29 of the 32 persons in whom seminal fluid was analyzed. Antiviral treatment was given to 5% of the persons overall, and 70 (13%) were hospitalized; the reasons for hospitalization were pain management, mostly for severe anorectal pain (21 persons); soft-tissue superinfection (18); pharyngitis limiting oral intake (5); eye lesions (2); acute kidney injury (2); myocarditis (2); and infection-control purposes (13). No deaths were reported.

https://www.nejm.org/doi/pdf/10.1056/NEJMoa2207323

georgia_peach··on The Wang 2200 (2008)
DOS was barely an operating system, so the programs had to bundle their own drivers & speak directly to the hardware for anything more than disk/compute. Because of this, that one little 8/16 change cut Wang off from the lion's share of the PC software library--first man to the gold rush, but without a pick or a shovel.

It's a shame they didn't make it though. From a technical perspective, the old man knew what he was doing.

georgia_peach··on The Wang 2200 (2008)
To be fair, I think An shot himself in the foot long before the boy took over--by making a "PC" with a 16-bit bus when the standard was 8-bit. From a computer engineering perspective, it was the obvious and correct thing to do. From a business perspective, it was an epic fail.
georgia_peach··on Arguing from compassion (2021)
On the one hand, he's right. On the other hand, I feel gaslit by the fact that, superficially speaking, someone has built a brand & an income around a BS token like "starmanning". I mean, we've all cast pearls before swine from time to time, but how many of you have managed to make a career out of it?
georgia_peach··on OpenXanadu
As someone who has read that book, & owns it, I can attest to the fact that Ted knows more about how computers work than most people who call themselves professional programmers (I know, I know, low bar..., but even so).

If this were a forum, instead of a plantation, I could post selections from it, and you could see for yourself.

georgia_peach··on OpenXanadu
Ted wrote a book ("Computer Lib/Dream Machines", 1974). He still sells it! Ted has known how computers work, in high detail, for longer than most of us have been alive.
georgia_peach··on OpenXanadu
Everyone does the color-rays thing first, because that's the easy part. At the heart of his vision are several non-trivial, unsolved problems. Most of these are still non-trivial & unsolved. Instead of clearly identifying & expanding upon these problems, one-by-one, & posting a bounty, he blames his programmers. The man does not like programmers.

It is ridiculous. Going by the "Computer Lib" book, and when it was published, it's obvious that Ted knows enough about how computers work, and has had more than enough time to write the thing all by himself--if his only problems were programming ones.

In a way, I am glad he failed. A Google-scale Google is bad enough. Adding a Google-scale Elsevier into the mix is not a plus.

georgia_peach··on Porn use and men's and women's sexual performance
The Reign of Quantity and the Signs of the Times

Latest example: Taylorism, applied to the bedroom.

georgia_peach··on Ask HN: How do you feel about developer environments moving to the cloud?
No. No no no no no no no no no. No.

No no no no no no, no no no no no no no no no no. No no no no no no? No! No no no no no no no, no no no no. No no no no no, no no no no no no no no no no.

No no. No no no.

(borrowed from Caitlin Johnstone)

georgia_peach··on Hg Init: A Mercurial Tutorial
Mercurial @ Facebook & Mozilla, per Wikipedia:

> Although Mercurial was not selected to manage the Linux kernel sources, it has been adopted by several organizations, including Facebook, the W3C, and Mozilla. Facebook is using the Rust programming language to write Mononoke, a Mercurial server specifically designed to support large multi-project repositories.

Mercurial @ Google:

> Speaking of Google, their Mercurial rollout on the massive Google monorepo continues. Apparently their users are very pleased with Mercurial - so much so that they initially thought their user sentiment numbers were wrong because they were so high! Google's contribution approach with Mercurial is to upstream as many of their modifications and custom extensions as possible: they seem to want to run a vanilla Mercurial out-of-the-box as possible. Their feature contributions so far have been very well received upstream and they've been contributing a number of performance improvements as well. Their contributions should translate to a better Mercurial experience for all.

https://groups.google.com/g/mozilla.dev.version-control/c/hh...

georgia_peach··on Jurassic Cloud
The main log provides CoW-like functionality, & archive logs provide snapshot-like functionality. Having the DB & the file system duel over these responsibilities is trouble waiting to happen.
georgia_peach··on Jurassic Cloud
Read what I wrote more carefully. Checksumming is error detection only, while parity schemes can handle both error detection & correction. Checksumming blocks in software that are already being checksummed in hardware is redundant. Parity, on the other hand, is an essential part of any data redundancy system.

For a transactional database, XFS + hardware RAID is going to be a more reliable setup than ZFS + JBOD. Database logs are similar in function to CoW, & the fancier DBs have time-machine features similar to snapshots. Having filesystem & software struggling against each other to solve the same problem, but with different solutions, is a situation that invites so many Heisenbugs. That, and a good RAID controller is going to handle drive-reported errors sooner and more gracefully than a ZFS scrub.

georgia_peach··on Jurassic Cloud
My computers from 15 years ago, PC or Mac, did all of these things--even high-res FPS games--beautifully. If all you do is surf/email/music/video/games--and I don't think it requires a citation to believe that this is the lion's share of users--current speeds are beyond sufficient.

The quality issues in modern machines are the byproduct of a quantity-cult pissing contest rather than necessity. If anything, the excesses are only wasted by sloppier software (which was enabled by the excess to begin with), piggier websites, covert crypto miners, etc. Wirth's law is a vicious cycle.

And it's a false economy: cut corners on the clean-up of discarded speculative branches, get some great numbers on the latest benchmark; the chipmakers who stoop to this get an edge in the market, but by the time it hits the consumer (who has no understanding of such things), the mitigation costs exceed the original "improvement". Because it is such a multi-variate & workload-dependent situation, it may not be cut-and-dry fraud, even though it smells a lot like it.

georgia_peach··on Jurassic Cloud
Checksum vs parity. I would wager that the drive firmware also detected the error. This is why I think ZFS checksumming is largely redundant. Parity / error correction over a zpool being another issue entirely.

This is not to ding ZFS. If I were in Sun's position of having to take responsibility for 3rd-party manufactured drives, I'd have done the same thing. And circa 2006, the reliability of in-drive error detection may have been in a poorer state.

Never had a corruption issue the past 10 years that wasn't preceded by months of SMART errors/warnings.

georgia_peach··on Jurassic Cloud
XFS has a long and solid track record, but without the workload-dependent regressions which can be encountered in a copy-on-write filesystem. Decent hard drives have had internal checksums for ages. If the drive is even halfway functioning, it will catch the bad blocks--making that particular ZFS feature largely redundant, and databases that matter are going to be on a RAID anyway, which has its own additional layer of parity.

ZFS is fantastic for some applications, not so much for others.

georgia_peach··on Jurassic Cloud
I would prefer a computer that was slower, but worked the way it was supposed to (i.e. without rowhammer & spec-ex bugs, AMT/secret minix kernel, encrypted microcode mystery-meat, etc).

The typical user doesn't need to bean-count every microsecond. He desperately needs a computer that is his own tool rather than an infosec quagmire & the business-end of tech sector money-proboscis.

It is, sadly, the path of least resistance. "Big number good" is much easier for a consumer to grasp than the (qualitative) corners that were cut to achieve those big numbers. Lies, damn lies, & benchmarks!

The combinatorics of making distributed the new default are astronomical. That he dashes this all off so lightly, and in so little detail, makes me wonder if he's ever really done the work. Whether he has, or he hasn't, this is still 100% the wrong direction for anyone outside of a data center.

georgia_peach··on WordPerfect for UNIX (1992)
a mighty fine terminal sir
georgia_peach··on Slice of Life: Pizza Orders Soar in D.C. (1991)
The DC boys & girls really do like their pizza--especially the cheese pizza.

https://wikileaks.org/podesta-emails/emailid/55433

georgia_peach··on WordPerfect for UNIX (1992)
&& find out how to get it on OSes that aren't debian-based

&& find a decent FFI wrapper if my app isn't in C-land

&& read the docs

&& static link hassles so I don't have to sort-out dynamic-link hassles for every platform

|| round-up a collection of dynamic libsixel libs & figure out how to bundle them with my script if I'm not using a compile-to-machine-code language

vs

   b64 := base64.Encode(myImg)
   fmt.Printf("\x1b]1337;inline=1;size=%d:%s\n", len(b64), b64)
If it's a feature request where I'm really only handling it to shut a few people up, which route am I going to take?
georgia_peach··on WordPerfect for UNIX (1992)
Last time I evaluated this, sixel & base64 image placement relative to re-positioned cursor had slightly different behaviors across different implementations. I think the only one with well-defined placement/dimensions behavior was the Kitty format--which is unfortunately Kitty-only.

https://sw.kovidgoyal.net/kitty/graphics-protocol/

If the goal is to hot-patch graphics into existing TUIs, Kovid is probably on the right track with this. It needs to be something richer than what sixel or iTerm2 provide--with pixel placement, play/pause, scaling, etc. Though for a do-over of piping a UI over a (relatively) low-bandwidth wire, I think something like Sun NeWS would have been a simpler & more feature-complete approach.

georgia_peach··on WordPerfect for UNIX (1992)
> when when run chat programs inside electron apps, does it really matters?

From a dev perspective, it's a lot easier to base64 an image you already have, with a base64 that's already in your stdlibs, than to scour github for a passable sixel library to pre-rasterize that jpeg & reformat it as sixel. I say this as someone who's written a sixel conversion library.

> competing formats

It's not a very old format, yet already supported on 4-5 terminals last I checked.

georgia_peach··on WordPerfect for UNIX (1992)
The achilles heel of these old inline display protocols is that there's little to no reporting from the client side as to dimension/resolution/resize/interaction... And to fix this in a performant way, it would need the ability to handle as many of those events as possible on the client side, hence some kind of VM & endless mitigations for it--chrome all over again.

> something like xterm for linux that is more up-to-date

Dickey put a lot of effort into xterm--especially on the correct emulation of old protocols like tektronics. The GPU-accelerateds may be the new hotness, but I don't think many of those devs are interested in software archaeology like tektronics & sixel.

georgia_peach··on WordPerfect for UNIX (1992)
It's okay for low-color/solid-run images, terrible for everything else. Nachman's image mime blobs (iTerm2 style) is the superior approach. mintty/mlterm/rlogin/wezterm already support it. Kitty has an (incompatible) variant--same idea, but delivered in chunks.
← PreviousPage 3 of 12Next →