205 Matching Annotations
  1. Last 7 days
  2. Sep 2020
  3. Aug 2020
  4. Jul 2020
    1. As Shannon Larratt is interviewing Stalking Cat, he brings up a point that's quite interesting to me, and entirely relevant to the idea of privacy and unwanted celebrity we discussed earlier in this course.

      SL: "... uh you do- you do go to a fair number of tattoo conventions, and you must experience at least a minor celebrity status while you're there."

      SC: "Well, you know, in fact, I've only been to a couple conventions-"

      SL: "I guess- I guess it's just every one you go to, they will always photo you."

      SC: "Right, and my pictures have been plastered all over the place, and uh, it, in a way kind of irritates me, because these people're making money off of something I've spent a great deal of time doing, and I haven't gotten a dime out of it."

      SL: "Mmhmm."

      SC: "But uh, and uh, and they're basically using my picture to get themselves famous."

      SL: "Mmhmm."

      SC: "Or to get publicised."

      SL: "Yeah."

      SC: "But again, I did this for me, not for other people."

      SL: "Mmhmm."

      There's also been a positive side to this, as it encouraged self-expression amongst the public, and while not exactly normalising it, it allowed people who needed to do stuff like this to accept it and go for it. (But not those who are doing it as a trend.)

  5. Jun 2020
    1. This means you no longer have to declare inverse_of on two associations which have good names.

      ... which have good names.

      This implies that those names where the inverse_of cannot automatically be inferred are bad names. I disagree that a "good name" is at all related/dependent on that ability.

      What they should say here instead is:

      ... which have names that allow the relationship to be easily inferred.

      Or refer to these names as the "default" or "Rails conventional" names for these associations.

      But it is not necessarily a better name. A better name is, quite often, one that is more descriptive and specific.

      For example, just because by default if you use rails generate with a User model, it might (I don't remember; can it even generate associations?) create a belongs_to :user association doesn't mean that's the best name for it. belongs_to :author or belongs_to :owner, for example, being more specific, are likely better names. The model still needs a generic name like User because it may be used in various relationships, but the relationships themselves should pretty much never be called user because there's almost always a more specific name that better reveals/describes the relationship.

    1. Un planteamiento semejante impulsa a tener en cuenta la posibilidad de consecuencias imprevistas, a hacer explí-citos los aspectos normativos que se esconden en las decisiones técnicas, a reconocer la necesidad de puntos de vista plurales y aprendizaje colectivo

      Esta idea está relacionada con la referencia a la novela Hyperión, la inteligencia artificial que determinó que para seguir evolucionando necesitaba un par que lo confrontara en debate.

    1. I know you acknowledged your response was late and you're just trying to help but please don't resurrect very old threads.

      This is better than creating a duplicate new thread.

      There is no better place to respond to an existing topic than in the existing thread for that topic.

    1. This is a poor solution

      What's so bad about this solution? If it works, it works. And it only requires wrapping in 1 additional block. Pretty simple.

  6. May 2020
    1. Because the conditional connectives thus complicate the formal reasoning about programs, they are better avoided.
    1. A real-world example of this would be an e-commerce site that allows users to “hold” items in their cart while they’re using the site or for the duration of a session. In this scenario, the technical cookies are both necessary for the functioning of the purchasing service and are explicitly requested by the user when they indicate that they would like to add the item to the cart. Do note, however, that these session-based technical cookies are not tracking cookies.

      I'm not sure I agree with this:

      [the technical cookies] are explicitly requested by the user when they indicate that they would like to add the item to the cart.

      The only thing they requested was that the item be held in a cart for them. They didn't explicitly request that cookies be used to store information about items in the cart. They most likely don't understand all of the options for how to store data like this, and certainly wouldn't know or expect specifically that cookies be used for this.

      In fact, localStorage could be used instead. If it's a single-page app, then even that would be necessary; it could all be kept in page-local variables until they checked out (all on the same page); such that reloading the page would cause the cart data held in those variables to be lost.

    1. Motion Picture Association of America Chairman Chris Dodd stated that the coordinated shutdown was "an abuse of power given the freedoms these companies enjoy in the marketplace today."

      It's not an abuse of power. It's free speech. It's protesting against an awful proposed law.

  7. Apr 2020
  8. cursus.edu cursus.edu