< ^ txt
Sat 27 Apr 2019 10:33:20 AM EDT
Slept from midnight to nine.
Woke for a bit around five.
High of fifty-two today.
Sunny until rain after five in the evening.
Goals:
- Move old blog posts?
Done. (December 2012)
- Check out Sway window manager
Done.
- Play with D&D stuff
Done.
Ten-minute walk in the morning.
Looks like Sway is still pretty immature, unfortunately.
No Debian packages, either.
Watched Freddy vs Jason on Netflix.
Fun.
The slapstick beats in the fight at the end were a little odd, but I like the "who would you rather" Three Stooges foreshadowing at the beginning.
Wished Jay a happy birthday.
https://www.newyorker.com/magazine/2017/11/27/the-serial-killer-detector
> Thomas Hargrove is a homicide archivist. For the past seven years, he has been collecting municipal records of murders, and he now has the largest catalogue of killings in the country—751,785 murders carried out since 1976, which is roughly twenty-seven thousand more than appear in F.B.I. files. States are supposed to report murders to the Department of Justice, but some report inaccurately, or fail to report altogether, and Hargrove has sued some of these states to obtain their records. Using computer code he wrote, he searches his archive for statistical anomalies among the more ordinary murders resulting from lovers’ triangles, gang fights, robberies, or brawls. Each year, about five thousand people kill someone and don’t get caught, and a percentage of these men and women have undoubtedly killed more than once. Hargrove intends to find them with his code, which he sometimes calls a serial-killer detector.
> Hargrove created the code, which operates as a simple algorithm, in 2010, when he was a reporter for the now defunct Scripps Howard news service. The algorithm forms the basis of the Murder Accountability Project (map), a nonprofit that consists of Hargrove—who is retired—a database, a Web site, and a board of nine members, who include former detectives, homicide scholars, and a forensic psychiatrist. By a process of data aggregating, the algorithm gathers killings that are related by method, place, and time, and by the victim’s sex. It also considers whether the rate of unsolved murders in a city is notable, since an uncaught serial killer upends a police department’s percentages. Statistically, a town with a serial killer in its midst looks lawless.
What might a simple, cheap, user-friendly ActivityPub server/client look like?
Storage on Amazon S3.
Static binary (Go) user client runs on localhost for reading and posting.
That's pretty cheap and simple.
But what about mobile users?
You'd need someone to host a public, always-on connector service, minimally.
And then we wander back into the charity/pay toilet/ad-supported model that requires a central admin.
(Jeez, there don't seem to be any generic ActivityPub mobile clients.)
https://schub.io/blog/2019/01/13/activitypub-final-thoughts-one-year-later.html
A few weeks ago, following a routine update, videos in Chromium started playing in red and yellow only on my home machine.
Disabling hardware acceleration in chrome://settings fixed the colors, but took me back to the days of horrible tearing, especially when scrolling.
The solution: leave hardware acceleration enabled, but turn off "Hardware-accelerated video decode" in chrome://flags/.
Googling this issue revealed nothing, so it's probably local to my machine and it's old Radeon HD 6670.
(Weirdly the various dubious benchmarking sites seem to indicate I wouldn't get any performance boost from a more modern R5.)
Maybe it's time to just upgrade my process; onboard graphics might be good enough and better supported by Linux.
The i5-9400 might be an OK upgrade.
A Radeon RX 560 maybe?
Another ten-minute walk in the early evening.
No rain yet.
Servings: grains 5/6, fruit 3/4, vegetables 4/4, dairy 0/2, meat 6/3, nuts 0/0.5
Brunch: mandarins, carrots, avocado, two eggs, corn chips, grapefruit, coffee
Lunch:
Afternoon snack: carrots, mandarin
Dinner: Chinese
91/65
< ^ txt