Germany: http://www.monster.de/ Netherlands: http://www6.monsterboard.nl/
I can highly recommend NL as a great place to live.
947 karma · joined November 5, 2010
Germany: http://www.monster.de/ Netherlands: http://www6.monsterboard.nl/
I can highly recommend NL as a great place to live.
Or, as partiallypro says, are they only sending the contents of e.g. browser search fields?
If the answer to the first question is yes, then this is a keylogger. If partiallypro is correct, then calling it a keylogger is disingenuous. By that logic you could call my mail client a keylogger, because it saves drafts to a folder on an IMAP server.
Email in profile, feel free to get in touch if you want more detail.
> Meanwhile, few warn against widespread surveillance, the repurcursions from the use of drones, etc.
The repercussions from drones could become worse if they are upgraded to include entirely autonomous AI, where there is no human involved in the "should I kill this person?" decision.
That being said, in this case these three dots have been joined up multiple times already, so there really is nothing new here. The interesting challenge is in reducing latency so that remote games are actually playable when the server is not on the same LAN.
Assume for the sake of argument that Nexmo is based in the UK. Using this exploit to access someone else's Nexmo.com account would be a violation of the Computer Misuse Act.
Writing a blog post detailing exactly how you achieved this would be a public admission of violating the Computer Misuse Act.
Another example: Person A publishes instructions detailing how to exploit this issue. Person B follows the steps, and causes financial harm to Nexmo. Nexmo sues Person B for exploiting their systems, and also names Person A in the lawsuit because their publication led directly to Person B's actions.
I'm not certain either of these cases would hold up in court, but there is certainly a risk that Nexmo would take the second approach. In the OP's shoes, the safest thing is not to publish. I'm not saying that's the right choice - just the safest from a legal perspective.
Let's say you are responsible for four team members who share support tickets. Support tickets begin arriving at 9am. One of the team is consistently ten minutes late, meaning the other three need to pick up the slack for him.
Forget about the management - this is unfair to his colleagues.
Blasphemy is subjective. What is blasphemy to one person is common sense to another.
Poorly.
Do you mean a Beowulf cluster of mobile phones? It seems like it would be woefully inefficient to say the least.
- each node in the cluster has an expensive screen attached to it, which would presumably be permanently disabled to reduce cooling/power costs. This is a waste of money. Same goes for bluetooth, accelerometers and anything else that is not directly contributing to the cluster. The cost of the screen etc. could have purchased more processors instead.
- temperature management would be incredibly inefficient. How would you cool a rack of 1000 phones/tablets? Server chassis are designed with this in mind. Phones/tablets are not.
It's an interesting idea to think about, but nobody is going to produce a cluster powered by iPhone 6s which is capable of competing (financially or computationally) with a cluster powered by servers designed for this purpose.
So in this case you would push an encrypted message, and your app would decrypt the message before displaying its contents.
http://www.pyimagesearch.com/2014/01/27/hobbits-and-histogra...
Fox News displayed the entire video of the Jordanian pilot being burned alive by ISIS, yet censored the buttocks of a man featured in a segment on nude beaches.
Note that six million is the high end of the estimate, with the low being a (still rather high) four million.
This study included things like hospitals, prisons and sewage works. When talking about council-operated CCTV it does not make sense to use the six million figure.
The study estimates 1 in 70 of these cameras are controlled by the local government.
This could work well for scheduled events as well as your weekend fishing example.
"Fostering a X culture" is a common phrase outside of the EC.
That's true. I think we're essentially on the same page here.
I guess I'm still using the old definition of lock in. Poor example: a proprietary Microsoft format that can only be understood by MS software. There is literally no alternative to using MS software if you want to access files created using this format.
Does "high switching cost" == "lock in"? I think it is a grey area. I would not consider myself locked in to Lambda if I had made the decision to host my app there, although I do see there is a high switching cost.
However, if I used RDS Postgres and Amazon decided to prevent me from creating database dumps to migrate to a self-hosted Postgres, then I would be very unhappy because that would be an arbitrary restriction with no purpose except to keep me on AWS.
> To me, it seems like the cost of moving this to some other platform is quite a bit higher than the cost of moving something from, say, EC2.
I agree completely with this. Let's say this was implemented on EC2 instances running Ubuntu, and configured with something like Salt or Puppet. The cost of moving to a Digital Ocean box would be negligible.
However, the application level can be easily moved to another platform. You could host the handler function code on an EC2 instance or bare-metal server. Little would change in the app code, except the API endpoint to which requests are sent.
So IMHO there is no lock in in the traditional sense, but there is a switching cost if you want to move to another platform.
Do you know what features this service had that made it worth $30k for 5 days access? Did they have some unique and useful features, or was it more about the available bandwidth/RPS that could be generated?
In this case the client has sent an invalid request so the response should be 400 Bad Request or 422 Invalid Data, with details of the error in the response body.