saw movies? uh yeah i sure hope you have
OK, I just saw someone posting about a project called Terra Tempora (https://terra-tempora.com/?ref=mastodon), which claims to let you "scroll through history", searching for battles, treaties, and "tracking civilisations".
Unfortunately the whole thing is a classic object lesson in why we shouldn't entrust our understanding of history to data scraping and AI processing, which is pretty clearly a core basis for the project. Here's some examples.
@mattblaze
Also, both of these countries can run elections just fine with hand-counted paper ballots. Why can't the USA?
@iris_meredith Have you ever seen a US ballot? Are you aware that most US elections involve dozens of contests on the ballot, often more?
But whatever, you’re clearly the expert here.
The big pink Shakespeare-themed mug my friend commissioned me to make for his wife for Christmas is done and it's big, pink, and Shakespeare-themed
@ludovic I see your “everything should be expressed in real world terms”, but honestly: how many games even track the passing of minutes?
If it’s not something that has an actual impact, then why state it at all? Like if an effect lasts 1D6 minutes, you’re probably better just saying “until the end of the scene”. Of course, that requires that you define scenes, which a lot of players don’t like as a concept.
@andrewdoull To be clear, I'm not arguing about expressing everything in "real world terms". Like I said in the article, I'm totally happy running OSE or Dragonbane using "turns" and "stretches" because *they are useful* in the context of those systems.
In contrast, RQ's "full turn" makes no sense. There are only a handful of things that use "full turn", and none of them are central to the gameplay loop.
Proof that beside being quantic, cats also have magnetic poles.
I've been carrying around an idea for a federated code forge for a while. Two things sharpened it recently: Tangled's post on the federated code forge, which builds a forge on the AT Protocol, and a Jujutsu workshop (Korean) by Seongmin Lee (@boltless.me), who works at Tangled, held at @turingappledev.
My version would build on ForgeFed, the #ActivityPub protocol for code forges (spec), so that repositories, issues and merge requests federate the way posts already do. The idea is early enough that I haven't even come up with a codename. What I want from it, roughly:
- Git and Jujutsu (so-called
jj) as equal clients. Not Git hosting with Jujutsu support bolted on, but a forge that understands both, so what Jujutsu is actually good at, stacked changes, becomes a first-class unit of review instead of a pile of separate pull requests. - No owner layer. Since the point is federation, one instance represents one person or one organization, permissions are managed per server, and a repository lives at
forge.example/myrepoinstead offorge.example/owner/myrepo. - A migration path off GitHub that keeps the history. Importing the code is easy; importing the issues, pull requests and discussions with their original authors attached is the part that matters. I'd keep a placeholder for each GitHub account and let whoever owns that account prove it, after which the instance swaps in their fediverse actor, so attribution carries over. How to express that claim in ActivityPub is the part I haven't figured out. It may need a new FEP.
Where this stands: I haven't read the whole #ForgeFed spec, Fedify doesn't ship the vocabulary yet (fedify-dev/fedify#751), and I have too much else going on to start soon. If you've run a forge or implemented ForgeFed, I'd like to hear whether any of this makes sense.
My wife and I will be on the road for the next two weeks for Designercon in Las Vegas, so we're taking the opportunity tonight to restock the shop and decorate for Christmas.
I flipped on the Tv while we work, and kumiai-ki (the mighty labor union mech) was there!
@ajroach42
Hey, AJroach, if my road trip down the pacific coast goes well, I'm going to be arriving in Las Vegas in 2 weeks. You gonna have the spare time to meet up?
So Luxon could remain, but weaker than ever with Act and NZ First combining as a very big tail to wag the dog. With Willis out, this gives Seymour disproportionate negotiating power to become, l'horreur, Finance Minister.
Plausible, however brutal?
@JulianOliver Seymour has spent the last fortnight humbly accepting the job whenever anyone mentions it. He absolutely is rubbing his hands together this morning.
Tomorrow is "everyone lies about Aaron Swartz day" which is almost as bad as April Fool's
Where were you when tosti machine broke?
I was bed
Woke up
Tosti machine broke
No
@ludovic They are older, from the marketing of Cyberpunk 2020, they had repeated pro-gamergate comments and transphobic comments: I didn't follow them for a few years after that. It shouldn't be hard to search for 'GOG Gamergate" to get sources.
I haven't followed them for a few years after that, but I did hear a theory that CD Projektred sold them off to quit dealing with their PR issues, no idea how true it is, but it seems this keeps happening
@Canageek I'll check it out, thanks!
I've been carrying around an idea for a federated code forge for a while. Two things sharpened it recently: Tangled's post on the federated code forge, which builds a forge on the AT Protocol, and a Jujutsu workshop (Korean) by Seongmin Lee (@boltless.me), who works at Tangled, held at @turingappledev.
My version would build on ForgeFed, the #ActivityPub protocol for code forges (spec), so that repositories, issues and merge requests federate the way posts already do. The idea is early enough that I haven't even come up with a codename. What I want from it, roughly:
- Git and Jujutsu (so-called
jj) as equal clients. Not Git hosting with Jujutsu support bolted on, but a forge that understands both, so what Jujutsu is actually good at, stacked changes, becomes a first-class unit of review instead of a pile of separate pull requests. - No owner layer. Since the point is federation, one instance represents one person or one organization, permissions are managed per server, and a repository lives at
forge.example/myrepoinstead offorge.example/owner/myrepo. - A migration path off GitHub that keeps the history. Importing the code is easy; importing the issues, pull requests and discussions with their original authors attached is the part that matters. I'd keep a placeholder for each GitHub account and let whoever owns that account prove it, after which the instance swaps in their fediverse actor, so attribution carries over. How to express that claim in ActivityPub is the part I haven't figured out. It may need a new FEP.
Where this stands: I haven't read the whole #ForgeFed spec, Fedify doesn't ship the vocabulary yet (fedify-dev/fedify#751), and I have too much else going on to start soon. If you've run a forge or implemented ForgeFed, I'd like to hear whether any of this makes sense.
I still often think about the fact that Aaron Swartz was only 14 years old when he helped develop RSS..
Imagine what he could give us when given the chance 🙏
RIP Aaron♥️
@stux Reminds me to boost and support the humans who come my way.
Where were you when tosti machine broke?
I was bed
Woke up
Tosti machine broke
No
KSNT (Kansas): Topeka woman finds live bobcat stuck in car after morning commute 11/7/26
@ai6yr wild. Glad kitty gets to use another life.
“There is a small percentage of people, the four of us on this pod and all of our friends, who are the asset owners of America. And we have benefited in every weather condition.
…
And then there's everybody else who are wage earners, and the structural capacity of the American economy to support and grow wage earners is broken” - Chamath Palihapitiya
~~
An “are we the baddies?” moment for tech billionaires
He missed the mea culpa for the four of them on the pod and their friends celebrating the idea of Anthropic and OpenAI destroying the livelihoods of America’s wage earners so they could get even richer.
From my local 350 group:
"There's a bill in the U.S. Senate scheduled for a vote on Monday —
the so-called Bipartisan American Affordability and Jobs Act.
Don't let the name fool you.
This bill is stuffed with blatant environmental attacks. It would:
• Gut the Clean Water Act, making it harder to protect water and stop polluting projects.
• Weaken the Endangered Species Act, limiting its ability to protect imperiled species like North Atlantic right whales and monarch butterflies.
• Lock in decades of fossil fuel dependence instead of supporting clean energy.
• Fuel energy-hungry data centers by accelerating federal approval of new gas pipelines and infrastructure.
• Hand mining companies unprecedented rights to occupy and degrade public lands, while removing the people's right to oppose these projects."