Digging in, fork and knife in hand, to an entire universe of problem-modeling I have never needed to deeply consider that has had decades of research put upon it in the form of #postgis .
I'm glad, a little less than halfway into my career by the standard retirement schedule, that there are problems I haven't touched at all. Keeps me young.
Earlier this year, I became aware of STANDARD EBOOKS, a donation-dependent group of edtiors and layout experts who have been doing the amazing work of taking out-of-copyright books, turning them into top-quality ebooks, and then releasing them for free.
Some of the books they've done are in the Internet Archive here:
https://archive.org/details/standardebooks
They're seeking 75 patrons in December to keep themselves afloat, consider donating to this amazing cause.
The meta this year is encouraging swerve drive, but it's a lot to ask of young teams to put eight motors on a robot.
Let me introduce you to synchro-drive (https://groups.csail.mit.edu/drl/courses/cs54-2001s/synchro.html). In its simplest configuration, two motors drive all the wheels on the robot: one turns them all synchronously and one spins them all synchronously. This is done using belts and your favorite flavor of right-angle gear chain.
It does have the one unusual property that while the drive train can drive in arbitrary directions, it can't turn the chassis. So for FIRST Robotics, one would have to couple it with a solution for swiveling whatever end-effector your robot has to finish the job. And slippage on the turn chain would be killer because there's no way mid-match to turn the wheels independently of each other. But if you can tolerate the challenge of keeping tension on your belts or chains, this can be way fewer motors than swerve.
Video of a synchro in action: https://www.youtube.com/watch?v=nurCA5Q4_hw
"""
Now family, I know you're worried about me and my time in the hospital. But fear not, for there is a god watching over me in my hour of need.
And that god is Crom, who wants me dead.
So I go now to battle for my right to draw one more breath in this ragged existence, to spite him who looks upon us with gloomy judgment.
Grieve not my fate, o kin! For I shall wrest my right to live from his dark grasp! And should I fail? Hah! Then I shall at last meet him face-to-face, and my fists will drag answers from his silent mouth!
"""
Losing GOP candidate arrested in string of shootings at New Mexico Democrats' homes - https://www.nbcnews.com/news/us-news/losing-candidate-arrested-shootings-new-mexico-democrats-homes-rcna66027
So, a half-million dead. Unknown millions left too sick to return to their former jobs. A dire need for juvenile and elder daycare. Early retirements from people who can't risk being exposed to covid. People just quitting because covid will kill them.
Just. The short-term thinking of "get back to normal" rides on refrigerated trucks full of corpses and people like me unable to leave the house because we want to live.
https://www.axios.com/2022/12/16/the-missing-workers-who-are-never-coming-back
On tuning playable character design to get from the abstract concept to the fun of action.
@SwiftOnSecurity I 100% am of the mind that service / help desk is the first line of defense in cybersecurity. Not only do you get to see the types of issues and fixes that are common for your environment, you are often the first to notice when things are a bit ‘off’. Service desk is a great source of threat intelligence for an org that all too often overlooked.
I know this article and the intended interesting part of the kohberger murder case is supposed to be the genetic forensics, but I found how they used the absence of his phone data useful notable as well. Hiding is hard, and sometimes stands out more. https://slate.com/technology/2023/01/bryan-kohberger-university-idaho-murders-forensic-genealogy.html
language, sexual imagery, disturbing imagery
"So I've got this act. I get a bunch of artists together, they make art. They publish it online in a ubiquitous communications platform that makes it trivial to see and copy their art, but the law says you can't **copy** it without some limitations so they figure they're fine.
So then a bunch a' eggheads, they come in, wave their dicks around, they build a machine that makes new art based on art someone made that gets fed into it. Then **they put that machine in front of the public.** The public puts all the artists outta work creating just the filthiest things imaginable, like they tell the machine to draw "George W. Bush fucking a bomb as the bomb is falling on Iraq, only Iraq is Saddam Hussein with a huge vagina." Just terrifying stuff. And now everyone hates the pictures and hates the eggheads and the artists hate the eggheads and the pictures and themselves and most of all, **everyone hates art.**"
"Well that's a hell of an act. So what do you call it?"
... my prediction is that we'll probably see some nodes converge around a common language / expectations of utility, and then outliers.
"Oh I like this one... it offers the Base Kit but also the Search Extension. Don't know how I feel about the AutoBan shared-list banning though."
An issue that will be both a positive and negative for #mastodon moving forward:
Mastodon is a protocol, not a single service. This means that what individual *nodes* do on that protocol differs based on the node you're on. Mine, for example, allows full-text comment searches and following topics by regex, not just hashtag.
This will be a pro because the ability to build different features atop the protocol will encourage development and diversity. Never care about spoiler tags? This node lets you disable them. This node lets you regex for which ones you auto-show and which ones stay hidden. This node lets you specify trusted users where spoiler-tags are auto-shown, etc. Let a thousand flowers bloom.
This will be a con because users actually hate complexity and it takes a particular mindset to be excited about the answer to a simple question of "Does Mastodon support X" being "It depends."
"A good idea is something that does not solve just one single problem, but rather can solve multiple problems at once."
~Shigeru Miyamoto
Career software engineer living something approximating the dream he had as a kid.