Show newer

@IceCubesApp
Where is the best place to report an apparent bug? Here, GitHub, AppStore?
Such things are an infrequent occurrence/observation in my use of the app but after a few days off-grid the ‘unread post count’ seems to have lost count.

@neil
Thank-you, (begins reading).
Horizon is/was not a single computer system: it is/was a complex integration of many. Windows server platforms thru the interations of those products since 1996, Unix servers through various interations of platforms over the same period, dozens of application software components some of which were bespoke developments, some of which were turnkey products.
Recently PO attempted to migrate it to Azure & failed, hence Fujitsu continues to deliver the service.
I’ll be interested to understand how the book addresses such a complex ‘computer’.

@feld @saxnot @nixCraft
Wasn’t aware of the inlet de-icing issue.
Thank-you for explaing.
This plugged/emergency exit door scenario should never have been permitted. If a cabin configuration requires an additional emergency exit, put it in. If it doesn’t,
don’t. Without good reason, don’t compromise the integrity of the fuselage.
The only reason to adopt the ‘plug door’ is to provide resale-ability to LCCs that exploit high density seating. Jeez, why not install even main deck cargo door & plug at original construction time?

@feld @saxnot @nixCraft
The requirement wasn’t ‘redesigning the fuselage’ it was to design an entirely new aircraft.
The present series of 737 is a frankenplane. The powerplant evolution has brought issues at every iteration due to short undercarriage legs designed to accommodate ground clearance for 1960s era low bypass turbojets.
Its avionics evolution has brought issues too: fundamentally a replicated/L-R side config where pilots expected to read the displays & ‘vote’ whether L or R presented the correct information (FBW & other common safety critical systems are triplex).

The Post Office scandal is shocking—but not surprising

The systems failures that led to this miscarriage of justice are all too familiar—and without some remarkable stokes of legal luck they might never have come to light

By me, at Prospect

prospectmagazine.co.uk/ideas/l

I wonder if they'll put Alan Bates on a commemorative stamp?

Levelled up on the labelling machine for this year. Love a good labelling machine.

@jon
If only tech bros took the train, imagine the uses they’d contrive for (physical) robots & AI. All luggage space, no passengers. 😂

@davidallengreen Your second paragraph summarises the debacle perfectly.
Oddly, I found that the examples of arrogance that I encountered within the Fujitsu project were readily overcome with pragmatism.

"What I want is to support some kind of reply-control feature."



That's what we've been doing all along and the primary driver behind the current architecture change. The underlying assumption of the "Facebook-derived side" of the fediverse as opposed to the 'Twitter-derived" or microblog side is that every conversation is a container and the container owner has control of the container - especially with regard to what goes in it and also control over comments and audience. Everything goes through them. We've tried several ways of doing this before recently settling on Collection operations. A basic model for this is FEP-400e; though we've enhanced it a bit by adding the context.

In FEP-400e, the 'target' is the conversation container, but also like FEP-400e we don't want to include the entire collection on every reply, but we do need to know the owner. So FEP-400e provides a model for this wherein the target is an incomplete activity stub which  contains an id, the type (Collection), and also attributedTo - which is the conversation owner. You can send replies to the actor of the inReplyTo, but if you want it in the container, you will need to send a copy to the target->attributedTo. They are the only ones who can add your comment to their conversation container.  They can also remove it. Either it gets Add'ed to the Collection or it was rejected. We don't waste any resources being polite to spammers with Accept and Reject. We owe spammers nothing.

@nixCraft Does the EU ruling mention the PD specification at all?
USB-C is merely the physical spec for a connector.

@bloor
Air fryer or conventional oven?
You’ve just remined me I need a croissant & a coffee.

@TheSnoopySnoop
That is a very nice shot, the background of the city skyline is class.

@neil @revk
I can attest to 100Mb (hopefully, soon to be back with AAISP) but often a few minutes for direct dnld, the impatience!

Show older
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.