Re: A survey of nearly 32,000
They can probably stretch to 64k as they could get away with using an unsigned integer.
11 publicly visible posts • joined 28 Aug 2014
Switched over to a Fenix 5 after my Pebble Steel, averaging 12 days between charges. I'm not rushing back.
Can't really see the market for a 4 day watch, it's not smart enough to compete with Android or Apple devices, and it doesn't have the fitness smarts of a Garmin, Suunto, TomTom etc.
I really wish they'd commit properly to the dex device and add proper Linux support. It immediately changes the phone from just a phone to a dual function unit that justifies the extra cost.
Keeping Android up to date is another must have feature now. If Google and now Nokia can do this then Samsung will have to up it's game.
It is my understanding that most modern phones now Amanda's their mac addresses when negotiating with access points - specifically to stop shopping malls etc from tracking them. This will also apply to the underground network. They won't see the same device id entering and exiting. They'd better check this before they invest too much.
Lambda in this sense is the AWS lambda service rather than the programming pattern of lambda functions. An AWS lambda service is a serverless piece of code written in Node.js or Python typically. It's entry point is exposed via API gateway as a restful end point that your mobile app consumes.
I'm surprised that banks are still capturing messages directly on SWIFT terminals. I'd expect they'd have all moved to STP (straight through processing) by now. Using this, the core banking app will validate all components of a transaction and it will be consistently reported and reconciled. Using a dual capture channel for messaging will always be a security risk as there's too many places to hide things. SWIFT's network is pretty robust, but at some point there is human input and banks should assume responsibility for guarding those points. Disclaimer - I built STP functionality between SWIFT systems and banking apps for a 3rd world bank 20 years ago, so this is not something new.
Just finished reading the pdf.
Basically we can reasonably assume that they are capable of capturing the full flow of internet traffic on there own.
What had always been the hard part is to trace back from a dynamically assigned ip address to a physical Mac (or IMEI on mobiles). This allocation, and it's relation to a username and billing contact always occurs inside the isp and is invisible to gov unless they specifically request it. Once they get this, all data can be traced to a named individual.
This is why they can state that they don't want the url or ip addresses - they already have that.