Valkyrie is the local storage layer of the modular storage system that I planned:

There's a higher layer called Freya to parse IRIs and map them to objects in Valkyrie instances. This is similar to the Controller in an MVC framework, but we are thoroughly agnostic about whether the IRI comes from a HTTP Location header

That would be beautiful... But I'm not going to be able to build that right away, at least not with clean lines of separation that would make it reusable and fun to share. Nope. I'll be building a #canard :psyduck:

@alcinnz On the point of multiparty episodes though, it's not limited to Doctor Who. I've always thought Stargate SG-1 and Atlantis were very good at having multiple layers of plot arcs. Some that follow into the next episode, some that appear through a series, and some that just appear occasionally, referring back to previous events to provide overall continuity and showing that some actions have consequences that last beyond the episode they start in.

@alcinnz The weeping angels were certainly a good villain though - definitely a move back to the classic Who days of taking an ordinary everyday object and giving it a dark side.

They are a Commons of strategic importance that needs to be free and clear of the corrupting effect of vested interests like the "Big 5" (Google, Microsoft, Facebook, Amazon, and Apple if you're not familiar with that label) who wield greater influence than most countries, a situation which has already been disastrous for the state of IT in the world today.

I have come to the considered conclusion that the way to fix the dire state of technology in schools, governments, and organisations does not involve the global giant tech corporations or their sponsorship/largess. It involves gov'ts working with small local companies and communities of interest. Gov'ts need to realise that software is critical infrastructure, like roads and power grids. And they need to be open and permissionless (with a well defined set of impartial rules) to use & join.

Electronics that are fully turned off are immune* to water. You can actually wash the inside of a computer without damaging it, if you do so carefully and dry it correctly. The problem is, most modern electronics are never fully off (even if they have auto-power-off water sensors), and people have a tendency to turn them back on before they're dry.

* as long as it dries out before something rusts or it gets turned on

Disclaimer: Do not carelessly get your electronics wet after reading this post. You can still easily damage them if you do something wrong.

I've started a thing at

The Yong Henge trilogy is a suite of games embracing the best traditions of literary speculative fiction

The current page is a feed console, the no-JS adaptive grid layout that I originally built for a multi-account Mastodon client UI. It's a 2 color layout so as to avoid competing for attention with in-game artwork. The games are adapted from 2 post-PBeM games and a later variant of the play by email game that inspired the original creator and the console is an attempt to combine the social and playing experiences in a unified interface

The web server is Turbo, an asynchronous framework built on LuaJIT, running behind Apache until I need to set up a caching proxy. I'm not a big fan of frameworks, but this is a good use case

This episode has perhaps the best "bootstrap paradox" (though I don't consider those a real paradox, just time travel weirdness) in the form of a DVD easter egg on select titles, which showed David Tennant's Doctor engaging in half a conversation saying weird things.

And ofcourse the episode mentioned there being forums online trying to figure out what he means.

The angels also sent him and Martha back in time, and as such they're largely absent from this episode.

One of my (many) favourite time travel stories is the Doctor Who episode Blink introducing the Weeping Angels.

It follows one-off protagonist Sally Sparrow as she explores an old abondaned building. On one trip she explores it with her freind Nightengale who's sent back in time right after her grandson knocks on the door, to tell Sparrow that Nightengale had lived a great life in the past.

Then she flirted with an investigator, and shortly receives a call from him as an old dying man.

A couple weeks ago @wmww was over and we talked for a while. He had an idea I'd like to put up here having let it sit for a bit.

The government should give organizations like Mozilla money based on the amount they accomplish, essentially buying free software for the world. The amount provided should be determined by competition amongst the various organizations, to encourage efficiency and effectiveness, but should be adjusted at a limited rate to insulate against political swings.

@alcinnz In the long run, we basically need to reinvent everything, and I already have ideas which would put a high cost to using (complex) client-side scripting and would rely as much as possible on standardized templating and fetching. But completely eliminating JS is not a magical solution, as you're not eliminating the underlying issues with it.

Last year Apple announced that to allow for Augmented Reality in iOS Safari they were supporting Pixar's Universal Scene Description (USDZ) format rather than W3C's WebVR.

This is the approach I want browsers to take! Because it's an entirely seperate MIMEtype implemented outside of WebKit.

As for whether it's an open standard, at the very least there's a public specification:

To make this a reality I ask webdevs to provide machine-readable downloads (adhearing to existing standards) for any data they visualize using JavaScript. Though it's unreasonable of me to ask you to stop using JavaScript there, I can only ask you to provide an alternative.

And I'll keep integrating the AppStream standards into my browsers to help your readers install a compatible app. I think that may possibly be the most valuable feature of Odysseus.

fuck disney 

The most fundamental mistake I see most browsers making is to think The Web has to do everything. They appear unwilling to accept help from other native apps.

Certainly it's great if you can publish anything to the Web, but browsers should focus on just text, images, and maybe videos. It can dispatch anything else to other apps.

Thereby allowing end-users to process and combine information however they want, and not require standards just to be written to bridge an app's backend and frontend.

anybody have advice on #privacy-oriented email services? trying to migrate away from google

fuck disney 

Show more

For people who care about, support, or build Free, Libre, and Open Source Software (FLOSS).