191 Matching Annotations
  1. Jan 2024
  2. Nov 2023
  3. Oct 2023
  4. Sep 2023
  5. Aug 2023
  6. Jul 2023
  7. Jun 2023
  8. May 2023
    1. My (Entirely-Unsolicited) Thoughts on the most Casual Crue™'s 10th:

      Ya know, my memory isn't so great anymore, but I remember my then best friend and most respected music authority resting pretty confidently in an argument about this sound, and those who peretuated it: that it was by nature/declaration substanceless, and therefore, those invested in it were either just superficial or.. idek anymore. Ingenuine, maybe?

      I don't think I was even placating with him when I mostly went along with it - it did seem important to invest in more abrasive (read: edgy bs) pursuits. I thought I was resisting "nostalgia" and even invested most of my twenties trying to start an online culture/electronic music magazine in direct editorial opposition to regurgitation. Imo, though, any actual exposure to self-described "vaporwave" makes it very plain how utterly useless it is to cry nostalgia because - crucially - whatever form of it that may or may not be an established marker of this voice is completely devoid of the illness that has absolutely pervaded, destructively, throughout all manner of expression and exploitation in the past 10 years.

      It is just not a constraining or negative force, here. I would propose, even, that it's been made, here, into the most powerful form of critique there possibly could be.

      And the grief!!! and the mania!! In any sort of ... worldly-participatory context, it should not be some gargantuan leap for even the most cynical, repressed, bitter 50-something white music writer army to make the connections, here. Our tears are fucking digital, idiot.

      ...ANYway, sorry. I don't actually have any business talking about music, but I can express my big, soppy as hell appreciation for the nigh-inconceivable amount of quantitive life force for which this milestone is a handy opportunity to reflect.

  9. Apr 2023
  10. Mar 2023
  11. Nov 2022
    1. Then don’t use the phrase “replacement character”, because a) it’s not a character at all, and b) it’s specifically not the character with the Unicode name REPLACEMENT CHARACTER, and c) people easily get confused with issues like this.
  12. Oct 2022
  13. Jun 2022
  14. Feb 2022
  15. Jan 2022
    1. Next, let’s say that your ticket is correct (so you made through security just fine!) and the gate number in your ticket says “Gate 24” but you walk to Gate 27. The attendant cannot authorize you to go through that gate because it’s not the right gate for your ticket.

      They have these mixed up! (Which is understandable, because 401 is misnamed "Unauthorized but should be named "Unauthenticated")

      Checking if authenticated (which, if it fails the check, should return 401 for authentication error) comes first,

      and then checking if authorized (which, if it fails the check, should return 403 for authorization error)

      See https://hyp.is/wRF7wHopEeynafOqKj81vw/stackoverflow.com/questions/3297048/403-forbidden-vs-401-unauthorized-http-responses

    2. In other words, an “incorrect ticket” is similar to messing up your credentials: wrong username and/or password and you receive back a 403 Forbidden. Using the correct credentials but trying to access a resource that is not allowed for those credentials returns you a 401 Unauthorized.

      They have these mixed up! (Which is understandable, because 401 is misnamed "Unauthorized but should be named "Unauthenticated")

      Checking if authenticated (which, if it fails the check, should return 401 for authentication error) comes first,

      and then checking if authorized (which, if it fails the check, should return 403 for authorization error)

      See for example https://www.loggly.com/blog/http-status-code-diagram/

    3. You can also think that 403 happens before 401, despite the natural number order: you will not receive a 401 until you resolve a 403.

      They have these mixed up! (Which is understandable, because 401 is misnamed "Unauthorized but should be named "Unauthenticated")

      Checking if authenticated (which, if it fails the check, should return 401 for authentication error) comes first,

      and then checking if authorized (which, if it fails the check, should return 403 for authorization error)

      See for example https://www.loggly.com/blog/http-status-code-diagram/

    4. These two sound pretty similar to me. And to make things even more confusing, 403 “Forbidden” says that the server refuses to “authorize” the request but it’s code 401 that is called “Unauthorized”. 😵
  16. Oct 2021
  17. Sep 2021
    1. Sanitary Tee and Wye are parts of the drain vent system. If you are doing plumbing works, you may have to use them in some sort. However, they look almost similar, and this confuses a lot of people. Especially to choose the one that best fits your drain system.
    1. Notice that the plugin is placed in the resolve.plugins section of the configuration. tsconfig-paths-webpack-plugin is a resolve plugin and should only be placed in this part of the configuration. Don't confuse this with the plugins array at the root of the webpack configuration object.
  18. Apr 2021
    1. In many computing contexts, "TTY" has become the name for any text terminal, such as an external console device, a user dialing into the system on a modem on a serial port device, a printing or graphical computer terminal on a computer's serial port or the RS-232 port on a USB-to-RS-232 converter attached to a computer's USB port, or even a terminal emulator application in the window system using a pseudoterminal device.

      It's still confusing, but this at least helps/tries to clarify.

    1. However, some users didn’t know that they could interact with and click on the text field. It looked like an empty box. The line affordance under the old text fields was not clear to some users. The line was confused with a divider.
    2. The label and input were confused with body text, especially in dense compositions.
  19. Mar 2021
    1. Not to be confused with tree (graph theory), a specific type of mathematical object.

      Confusing: https://en.wikipedia.org/wiki/Tree_(data_structure) says

      Not to be confused with tree (graph theory) "Tree (graph theory)"), a specific type of mathematical object. but https://en.wikipedia.org/wiki/Tree_(graph_theory) redirects to https://en.wikipedia.org/wiki/Tree_structure and https://en.wikipedia.org/wiki/Tree_structure is in category Trees (data structures) So is one a subtype/hyponym of the other ... or what?? How are they related? Skimming the articles a bit, esp. the first paragraph which clearly states as much ( :) ), I believe the answer is: a tree (data structure) is an implementation (in a programming language) of / or a "type that simulates" a hierarchical tree structure. a tree (data structure) is the computer science analogue/dual to tree structure in mathematics

    2. Not to be confused with trie, a specific type of tree data structure. Not to be confused with tree (graph theory), a specific type of mathematical object.
    1. An equation is any expression with an equals sign, so your example is by definition an equation. Equations appear frequently in mathematics because mathematicians love to use equal signs. A formula is a set of instructions for creating a desired result. Non-mathematical examples include such things as chemical formulas (two H and one O make H2O), or the formula for Coca-Cola (which is just a list of ingredients). You can argue that these examples are not equations, in the sense that hydrogen and oxygen are not "equal" to water, yet you can use them to make water.
    1. You’d think :empty would be it, but it’s not. That’s for matching things like <p></p>… container elements with nothing inside them. Inputs are no-content elements already.
  20. Dec 2020
  21. developer.mozilla.org developer.mozilla.org
    1. In a browser, the chrome is any visible aspect of a browser aside from the webpages themselves (e.g., toolbars, menu bar, tabs). This is not to be confused with the Google Chrome browser.
  22. Nov 2020
    1. There is no rerender, when you call listen, then all scroll events will warn on chrome. See this entry from svelte: breaking the web

      Even the author of this library forgot this about Svelte?? :) (Or maybe he didn't and this response misunderstood/falsely assumed that he had.)

    1. if the value given in value is contained in the array that is the value for the field for the form

      distinction:

      • the value given in value prop of Field
      • the value for the field for the form (formState.values[field_name])
  23. Oct 2020
  24. Sep 2020
  25. Aug 2020
  26. Apr 2020