The Sentinel logo received eleven slices from the light arcs in the reveal trailer. I've seen a lot of people speculate that this is intended as a hint of when another announcement is. A lot of people are guessing it is supposed to hint at 11/11/27 for another announcement, as the light slices hit their peak when there is 27 seconds left int he video

While I wouldn't personally jump fully onboard with this, this would not be the first secret message hidden in Bethesda marketing materials if it turns out to be true.

@manolo this doesn’t look like macOS.

The Sentinel logo received eleven slices from the light arcs in the reveal trailer. I've seen a lot of people speculate that this is intended as a hint of when another announcement is. A lot of people are guessing it is supposed to hint at 11/11/27 for another announcement, as the light slices hit their peak when there is 27 seconds left int he video

While I wouldn't personally jump fully onboard with this, this would not be the first secret message hidden in Bethesda marketing materials if it turns out to be true.

some progress in my quest to have a somewhat less shitty head voice

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.

#History #DigitalHumanities #DataViz #Histodons

@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

@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.

#CatsOfMastodon #Caturday

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/myrepo instead of forge.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.

#codeforge #fediverse #fedidev

@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?

Tomorrow is "everyone lies about Aaron Swartz day" which is almost as bad as April Fool's

@jaz

Where were you when tosti machine broke?

I was bed
Woke up
Tosti machine broke
No

@Canageek I'll check it out, thanks!

big sur never gets old

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/myrepo instead of forge.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.

#codeforge #fediverse #fedidev

#Harmony was featured on a popular Japanese online publication!

https://gigazine.net/news/20261107-harmony/