With non-unique units paladins can only be countered by upgraded halberdier, heavy camels or a huge mass of arbalesters. Monks counter them in small numbers but in late game when they're massed they're almost unstoppable unless you have halb/camel in equal numbers.
Well even arbalesters get slaughtered by Paladins, unless we are able to push them behind a wall or a corner with only a very tiny attack area for the Paladins.
I think even in open ground if you have a big enough group you can still trade well. Ethiopian arbs fire 25% faster. If you micro the arbs to focus on individual paladinsthey can one shot paladins and their attack surface area increases with the sqrt() of their numbers. For sure it's a lot more work than spamming halb.
We're a startup building a device which gives seniors access to the digital world, with a card-based interface. We're looking for help with our main product, which is based on Android. Everything's built on Kotlin, rabbitmq & multiplatform compose for the companion app. Bonus points for experience with: BLE, IR, HDMI CEC, NFC, Swift (for the companion app), ansible, German.
If you're interested, send me an email at simon@family.cards
It looks very similar to the “secure boot” mechanisms in Windows and other commercial client OS.
Strikes me as very dangerous though on the web where there are so many paths for malware to get in and this could get in the way of plugging the holes.
No, it's similar to attestation APIs like android SafetyNet (now called Play Integrity API) that are used to check that "your ROM is valid according to Google".
Secure boot can protect you eg. against malware gaining write access and modifying your system. I see it as user protection, as long as you can sign the trust chain. This is what GrapheneOS is doing as far as I know.
A trust chain beginning at the bootloader is what will ultimately enable this API, though, because that's what SafetyNet/Play Integrity API relies on. If you don't have a locked bootloader, or you're not running stock Android, you won't pass SafetyNet/Play Integrity (at least the higher tiers of it).
It was also dangerous for your PC: as soon as people ceded the ability to led their parties control what we run on our devices--such as by "only firmware signed by Apple can run on my phone"--we lost this war.
> It was also dangerous for your PC: as soon as people ceded the ability to led their parties control what we run on our devices--such as by "only firmware signed by Apple can run on my phone"--we lost this war.
If that's how "we lost this war", then it was lost before it even started. Even before Apple released their phones, it was already the case that phone firmware came only from the phone manufacturer. That is: phones come from a different lineage than PCs, and were never as open as general purpose computers ended up being.
I mean, those were by and large fixed function devices and while phone calls are certainly a form of communication they aren't really networked devices. And... while it was technically possible to update the software on them, most people never did.
There were only a scant handful of years where there even existed phones where this could matter... but now this same mentality is being applied to every new category of device--all of which acting as general computing devices--based on these precedents.
We're working on a device to allow seniors to access the digital world with a haptic interface. We support video calls / photo sharing / content / telemedicine / exercises to bridge the generational gap in digital services.
This will not diff well if you add a new row at the beginning. It's the same problem with non-trailing-commas, but moved to the front instead of the end.
