• 4 Posts
  • 2.6K Comments
Joined 3 years ago
cake
Cake day: June 18th, 2023

help-circle
  • Hmm, this must also be implemented in iOS right? Like there’s no way this isn’t also being used on mobile devices.

    Oh, yeah there it is:

    And even more recently, a forensics tool went looking on the phone: in September 2026, Alexis Brignoni taught iLEAPP to read the same store on iOS, where graph.db and the ontology.db that decodes its predicate codes sit under /private/var/mobile/Library/IntelligencePlatform; he writes it up in Reading the iPhone Knowledge Graph, and Checking Its Work.

    This links to https://leapps.org/blog-post?post=apple-intelligence-platform-knowledge-graph for more information.

    Your iPhone runs a daemon called knowledged. It sits in the background and does exactly what the name suggests. It builds knowledge. Not files, not logs, but a graph of things the phone has decided are true about you. Who your contacts are. Where you have been. Which apps you run and who made them. It ties all of that together and stores it on the device.

    Fucks’ sake. Everything is Big Brother. Makes me want to give up everything and move to a rural area in Africa or India or something, someplace away from cities and big tech corpos.

    Android must be doing similar things, though for Google it’s probably server-side and might not be available on the local device.







  • For critical systems, reliability, predictability, consistency, and long-term performance data are more important than modernization. It makes perfect sense that a system like this would lag the leading edge of technology significantly. It is ok if the technology has problems, even if it has high failure rates, as long as the failure rates are predictable - then you can write procedures around them. Floppy disks don’t exactly offer bulletproof reliability, but they are well understood - and also you can generally just toss them on a desk or in a drawer without worrying too much about incidental damage.

    You want this kind of technology to be so simple and dependable that you don’t have to think about it, it just works as expected. It also massively simplifies staff training and procedure documentation if the relevant bits of technology don’t change very often - until of course those bits become so outdated that the procedures for getting them to interface with newer systems becomes its own mess.

    If it ain’t broke, don’t fix it.














  • The technology has improved, so the device is more complicated than the early prototypes. That’s why I included the diagram above.

    how hard could it be?

    Well, how much mass does it need to move, if it’s 100m long, and is fully loaded with people? To keep it simple, we’ll be generous and assume an average 80kg human, spaced evenly every 1m, so that’s 8000kg of mass that the motor needs to be able to move, constantly. We don’t want the system to change speed under load, but keep a constant speed, so we’ll actually want to be able to handle more than the average load, with room to spare, so call it 12000kg. That’s… a lot of torque.

    We’ll also need a compensation mechanism to keep the speed steady as the load on the motor changes, and we’ll need an emergency stop braking system. We’ll need shock absorption to handle the impact of people stepping onto the walkway and potentially dropping any objects they’re carrying, so that the constant load/unload doesn’t cause additional wear on the drive system. We need the mechanism to move the hand railing along with the walkway. We’ll need to run electrical wiring to each unit. We’ll need to dig a hole in the ground to fit the mechanism for each unit. We’ll need to safety check each unit post-install.

    This simple-in-theory device is pretty complicated in practice. We haven’t even talked about weatherproofing.