12 Matching Annotations
  1. Dec 2022
    1. Include one or both of these headers in your messages:

      Actually, if you include List-Unsubscribe-Post, then you MUST include List-Unsubscribe (both).

      According to https://www.rfc-editor.org/rfc/rfc8058#section-3.1,

      A mail sender that wishes to enable one-click unsubscriptions places one List-Unsubscribe header field and one List-Unsubscribe-Post header field in the message. The List-Unsubscribe header field MUST contain one HTTPS URI. It MAY contain other non-HTTP/S URIs such as MAILTO:. The List-Unsubscribe-Post header MUST contain the single key/value pair "List-Unsubscribe=One-Click".

  2. Sep 2021
  3. Jun 2021
    1. In the context of git, the word "master" is not used in the same way as "master/slave". I've never known about branches referred to as "slaves" or anything similar. On existing projects, consider the global effort to change from origin/master to origin/main. The cost of being different than git convention and every book, tutorial, and blog post. Is the cost of change and being different worth it? PS. My 3 projects were using your lib and got broken thanks to the renaming. PS. PS. I'm glad I never got a master's degree in college!
  4. Apr 2021
    1. If you'd like to read more about the game's arguments, click here. 

      I'm not familiar with this term "arguments" used like this. Isn't this more referring to the motivation for this game?

  5. Nov 2020
    1. However, those descriptors gave a bit too much flexibility/dynamism to the class shape in order to be efficiently optimizable.

      I think this:

      However, those descriptors gave a bit too much flexibility/dynamism to the class shape in order to be efficiently optimizable.

      means:

      However, because those descriptors were gave so much too much flexibility/dynamism to the class shape, it could not be be efficiently optimized.

      rather than:

      In order to be efficiently optimizable, those descriptors gave much flexibility/dynamism to the class shape.

      In other words that flexibility/dynamism hindered optimization; it wasn't for the purpose of optimization (as "in order to be" could be interpreted as).

      The "too much" wording also contributed to the confusion for me.

      But maybe just dropping "in order" would have been enough for me:

      However, those descriptors gave a bit too much flexibility/dynamism to the class shape to be efficiently optimizable. or However, those descriptors gave a bit too much flexibility/dynamism to the class shape for them to be efficiently optimizable.

  6. Sep 2020
    1. Svelte offers an immutable way — but it’s just a mask to hide “assignment”, because assignment triggers an update, but not immutability. So it’s enough to write todos=todos, after that Svelte triggers an update.
  7. May 2020
    1. of, relating to, or being a grammatical case or form expressing means or agency

      I really need an example of this!

      It seems unusual that they specifically mention "a grammatical case or form". I've never seen a definition before that is anything like this one.

      How is this different from definition 1?

    1. to bypass work

      What does "work" mean here? I think maybe they mean to bypass profiling?