10 Matching Annotations
  1. Nov 2023
  2. Jun 2021
    1. Anne: I was not present at your survey, so I don't know much about you. So maybe we could just start by you telling me about the circumstances for you, going to the US, how old you were, your first impressions, why you went or your family went.Mike: When I was really young, I had gotten accident that required surgery and I needed to get that surgery done, so when I went to the hospital and get it done there was actually a couple of people from a criminal organization that were supposed to, I guess, kill somebody in there. I remember this like it was yesterday. I had a little breathing mask on and the doctor was telling me to breathe when he counted the eight, I could just hear the gunshots.Mike: And I remember waking up in a bus, because my mom had gone inside the hospital, grabbed me and got on the bus. And I remember waking up kind of like, "Where am I?" And she ended up telling me all that happened, because of that we decided—well, my mom decided—that she wanted a better life for us. So we ended up crossing the border to Arizona. It actually took us three days.

      Mexico, before the US, Migration from Mexico, Reasons, Violence

  3. May 2021
    1. Also, it is definitely NOT okay to recommend --force on forums, Q&A sites, or in emails to other users without first carefully explaining that --force means putting your repositories’ data at risk. I am especially bothered by people who suggest the flag when it clearly is NOT needed; they are needlessly putting other peoples' data at risk.
  4. Apr 2021
  5. Mar 2021
  6. Jan 2021
    1. As an example, recall the Sync and Send marker traits we discussed in the “Extensible Concurrency with the Sync and Send Traits” section in Chapter 16: the compiler implements these traits automatically if our types are composed entirely of Send and Sync types. If we implement a type that contains a type that is not Send or Sync, such as raw pointers, and we want to mark that type as Send or Sync, we must use unsafe. Rust can’t verify that our type upholds the guarantees that it can be safely sent across threads or accessed from multiple threads; therefore, we need to do those checks manually and indicate as such with unsafe.
    2. As with references, raw pointers can be immutable or mutable and are written as *const T and *mut T, respectively. The asterisk isn’t the dereference operator; it’s part of the type name. In the context of raw pointers, immutable means that the pointer can’t be directly assigned to after being dereferenced. Different from references and smart pointers, raw pointers: Are allowed to ignore the borrowing rules by having both immutable and mutable pointers or multiple mutable pointers to the same location Aren’t guaranteed to point to valid memory Are allowed to be null Don’t implement any automatic cleanup
  7. Apr 2019
    1. LastPass has always been stressing that they cannot access your passwords, so keeping them on their servers is safe. This statement has been proven wrong several times already, and the improvements so far aren’t substantial enough to make it right. LastPass design offers too many loopholes which could be exploited by a malicious server. So far they didn’t make a serious effort to make the extension’s user interface self-contained, meaning that they keep asking you to trust their web server whenever you use LastPass.
  8. Nov 2017
    1. We know that there are few sticky security and implementation issues

      Which is probably why @judell’s tate doesn’t show up in Chrome on my system and there’s weirdness with the scrolling once we accept to load unsafe scripts.