Imran Nazar ~ عمران نزر
Front-end #typescript developer and general keyboard tapper; author of Internet RFC 7168 (Hypertext Coffeepot Control Protocol for teapots); occasional plumber, more than occasional #c64 #retrocomputing enthusiast, terrible at classical #piano.
Header photo is a verdant scene looking over the landscape near Buxton, England, taken from a single-track country road.
- Posts
- 2,712
- Followers
- 250
- Following
- 301
-
A technical #ActivityPub question for a Sunday: is it possible/desirable to have every Actor on an instance share the same key pair?
I'm building something vaguely in the vein of FediMeteo, where all the accounts are automated and you'd generally follow one of those automated accounts to get the weather for your locality. Now, FediMeteo has a different key pair for each account, so the bot for Birmingham's weather has a different public key to Manchester.
But it's not a requirement that each account has a unique key, if the keys are only used for signature verification, right? Like, I don't think it'd be a security issue if "Weather for Birmingham" was signed with the key from "Weather for Manchester".
My question: is this another one of my Sunday Bad Ideas, and I should really have a key pair per account instead of trying to have the whole instance share?
-
Some knew in advance that Skynet was growing geometrically. The Cult of the Human Renaissance had spent years (and a lot of political capital) piggybacking Shuttle launches to build a lifeboat that could remain in orbit with a few hundred inhabitants before the inevitable end came for the billions below.
When the acute fallout had died back, the theory held, those left above could return to Earth as rulers of the ashes. There were problems with the theory, sure, but the Renaissance held true to its belief that the machines would simply admit defeat when met with their obvious betters.
August 1997 came and went, the world was enveloped in nuclear fire, and the Cult watched idly from their orbital vantage point. Thirty years up here, and they could emerge triumphant.
The months passed slowly in orbit, until the end of 1999. The station performed regular boosts to retain elevation, against the ever-so-slight drag of the wisps of atmosphere that were still present up here.
Until the Cult woke up on Jan 1, 2000, to find an error on the primary navigation display:
Component can't create object
Failed on creation from object context: CoCreateInstance (ProgId:
ADODB.Connection.2.0) (CLSID: {00000514-0000-0010-8000-00AA006D2EA4})See, all that lobbying to get space on launches, and the Cult's own human rocketry program, had meant they were strapped when it came to design and fit-out of the lifeboat itself. Mechanically it was sound and held pressure, but the navigation and station-keeping software was farmed out to third parties.
After three rounds of sub-sub-contracting, the work was done by a software engineer at a bank in South Korea. Or well, that was their day job; on the side, they reused much of the code for whatever jobs were going on Mechanical Turk.
And the day job was maintenance and new features for an ActiveX plugin for the bank, in Internet Explorer 4.01. The latest and greatest at the time of launch, but still not patched for the Y2K bug.
The millennium came, and station-keeping failed on the lifeboat. Unable to counter atmospheric drag, the Cult of the Human Renaissance came to a fiery end on August 29th 2000, three years to the day after the end of the world.