17 Matching Annotations
  1. Apr 2020
    1. Finally, from a practical point of view, we suggest the adoption of "privacy label," food-like notices, that provide the required information in an easily understandable manner, making the privacy policies easier to read.
  2. Mar 2020
    1. Why would a company want to have one system for people in France, Germany, and Italy and a separate one for people everywhere else?
    2. “It’s strange to say, ‘Yeah, we’re going to respect the privacy of Europeans more than all other human beings all over the world,’”
  3. Jan 2020
  4. Nov 2019
    1. I always prefer strictness, bad behavior should be uncovered as soon as possible or you are effectively encouraging it, which means they'll soon be back asking why it doesn't work for X and Y. Fix the problem at the source. I don't really care, but IMHO doing this seems like a charitable thing but it's actually the opposite.
    2. In a sense, the current behavior is the best behavior, because it never works, you will never get the impression that it does in React.
  5. Sep 2019
    1. The theory says that in distributed systems everything is eventually consistent but the pragmatic view of the real world says that we need to be real careful on what we choose to make eventually consistent.
  6. Jan 2019
  7. getincredibles-fe.herokuapp.com getincredibles-fe.herokuapp.com
    1. What's the stage your project is currently at?

      This is a required field (add * at the end) Please remove the first option 'stage at which my project is currently at' from the dropdown as it's not an option one can choose.

      Please also match the look and feel of this to the other drop downs..e.g. this one is grey, fonts seem different and it also animates/appears on the screen in a different way

  8. Nov 2018
    1. “The role of the hospitalist often is to take recommendations from a lot of different specialties and come up with the best plan for the patient,” says Tejal Gandhi, MD, MPH, CPPS, president and CEO of the National Patient Safety Foundation. “They’re the true patient advocate who is getting the cardiologist’s opinion, the rheumatologist’s opinion, and the surgeon’s opinion, and they come up with the best plan for the patient.”
  9. Jun 2017
    1. no data loss will occur as long as producers and consumers handle this possibility and retry appropriately.

      Retries should be built into the consumer and producer code. If leader for the partition fails, you will see a LeaderNotAvailable Exception.

    2. By electing a new leader as soon as possible messages may be dropped but we will minimized downtime as any new machine can be leader.

      two scenarios to get the leader back: 1.) Wait to bring the master back online. 2.) Or elect the first node that comes back up. But in this scenario if that replica partition was a bit behind the master then the time from when this replica went down to when the master went down. All that data is Lost.

      SO there is a trade off between availability and consistency. (Durability)

    3. keep in mind that these guarantees hold as long as you are producing to one partition and consuming from one partition.

      This is very important a 1-to-1 mapping between writer and reader with partition. If you have more producers per partition or more consumers per partition your consistency is going to go haywire

    1. Kafka consumer offset management protocol to keep track of what’s been uploaded to S3

      consumers keep track of what's written and where it left off by looking at kafka consumer offsets rather than checking S3 since S3 is an eventually consistent system.

  10. Nov 2016
  11. Nov 2013
  12. Sep 2013