503 Matching Annotations
  1. Sep 2020
  2. Aug 2020
  3. Jul 2020
    1. Both acronyms and initialisms are made up of the first letter or letters of the words in a phrase. The word acronym typically applies when the resulting thing can be read as a word; for example, radar comes from "radio detection and ranging" and scuba comes from "self-contained underwater breathing apparatus."
  4. Jun 2020
    1. In addition, if the option, An administrator must always approve the comment, is set in Administration > Settings > Discussion, this e-mail address will receive notification that the comment is being held for moderation. Please note this is different than the address you supplied for the admin user account; the admin account e-mail address is sent an e-mail only when someone submits a comment to a post by admin.

      They're trying to make a distinction between "administrator" address and "admin" (short for administrator) account. Hmm. Maybe they should have called them different words. Anyway, this could be made less confusing.

    1. In systems engineering and requirements engineering, a non-functional requirement (NFR) is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors. They are contrasted with functional requirements that define specific behavior or functions

      This is a strange term because one might read "non-functional" and interpret in the sense of the word that means "does not function", when instead the intended sense is "not related to function". Seems like a somewhat unfortunate name for this concept. A less ambiguous term could have been picked instead, but I don't know what that would be.

  5. May 2020
    1. In progressive enhancement (PE) the strategy is deliberately reversed: a basic markup document is created, geared towards the lowest common denominator of browser software functionality, and then the designer adds in functionality or enhancements to the presentation and behavior of the page, using modern technologies such as Cascading Style Sheets, Scalable Vector Graphics (SVG), or JavaScript.
    1. The main difference between a decoupled CMS and a headless CMS is that the decoupled architecture is active—it prepares content for presentation and then pushes into the delivery environment—whereas a headless CMS is reactive—it sits idly until a request is sent for content.
    1. sorry but it's not what I asked for. Hiding recaptcha when user didn't agree on cookies is something that everyone knows that they can do. Many 3rd parties has some magic parameter which blocks the cookie, but doesn't block the functionality of the element, and I'm looking for something like that
    1. In the context of first-order logic, a distinction is maintained between logical validities, sentences that are true in every model, and tautologies, which are a proper subset of the first-order logical validities. In the context of propositional logic, these two terms coincide.

      A distinction is made between the kind of logic (first-order logic) where this other distinction exists and propositional logic, where the distinction doesn't exist (the two terms coincide in that context).

    1. EU consumer law applies to contracts or other legal relationships between consumers (on one side) and professionals, businesses, companies on the other (B2C). It does not apply to B2B (e.g. a supermarket places an order with its fruit supplier) or C2C relationships (e.g. I sell my old bike over eBay).
    2. 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. However, please note the following: it will depend on how those subdomains are defined. Are they just subsections of a project that belongs together like help.example.com or blog.example.com (and many other possible arrangements that are part of one and the same setup)? In such a case, using the same policy is appropriate. Problems arise when completely different projects which have little to do with one another and whose data collection practices also differ so significantly that they require different privacy policies.
  6. Apr 2020
    1. Running the same code in the browser and on the server in order to avoid code duplication is a very different problem. It is simply a matter of good development practices to avoid code duplication. This however is not limited to isomorphic applications. A utility library such as Lodash is “universal”, but has nothing to do with isomorphism. Sharing code between environments does not give you an isomorphic application. What we’re referring to with Universal JavaScript is simply the fact that it is JavaScript code which is environment agnostic. It can run anywhere. In fact most JavaScript code will run fine on any JavaScript platform.
    2. Isomorphism itself is not purely a JavaScript thing. You can also build an isomorphic application in Dart or even use two different languages/stacks to render the same result. In fact there are many “isomorphic” applications which render a full HTML document on the server using PHP, Java or Ruby and use JavaScript and AJAX to create a rich user experience in the browser. This was the way things were done before the rise of Single Page Applications. The only real reason isomorphism is tied to JavaScript is because it’s the only language widely supported in the browser, and so at least part of the whole thing will use JavaScript. There’s no such thing as Isomorphic JavaScript, only isomorphic applications.
    1. In math, idempotence describes only unary functions that you can call on their own output. Math-idempotence is, “If you take the absolute value of a number, and then you take the absolute value of that, the result doesn’t change on the second (or subsequent) operations.” Math.abs is math-idempotent. Math-idempotence only applies to functions of one parameter where the parameter type and return type are the same. Not so useful in programming.
    1. 1- Validation: you “validate”, ie deem valid or invalid, data at input time. For instance if asked for a zipcode user enters “zzz43”, that’s invalid. At this point, you can reject or… sanitize. 2- sanitization: you make data “sane” before storing it. For instance if you want a zipcode, you can remove any character that’s not [0-9] 3- escaping: at output time, you ensure data printed will never corrupt display and/or be used in an evil way (escaping HTML etc…)
    1. There is a fundamental difference between these two kinds of content: the user comments are stored in our databases, which means their Markdown syntax can be normalized (e.g. by adding or removing whitespace, fixing the indentation, or inserting missing Markdown specifiers until they render properly). The Markdown documents stored in Git repositories, however, cannot be touched at all, as their contents are hashed as part of Git’s storage model.
    1. Many hackers and security crackers turn their talents toward professional ends, of course, and some security crackers got where they are only through professional advancement, but one definitely need not have a professional interest to pursue the path of either a hacker or a security cracker.
  7. Mar 2020
    1. A single consent form is useful when consent is requested for a single purpose. Here: analytics

      This seems like an important distinction:  Probably (?) you can only use a simple Agree/Disagree consent request if you only have a single purpose/category that you are obtaining consent for.

      As soon as your site has multiple categories to need consent, then you must allow individual consent/refusal of consent for each individual category/purpose.

      This is alluded to just a little bit further on:

      Consent should also be granular; users must be allowed to selectively decide what types of tracking, analytics and other activities their data can be used for.

  8. Jan 2020
  9. Dec 2019
  10. Nov 2019
  11. Jul 2019
    1. It is different from iterative development because it does not focus on a single release of the product, service or result and it typically makes use a complete team instead of one broken by functional areas.

      distinction from Iterative styles

    2. PMI® describes life cycles as generally either being adaptive or predictive. In the simplest terms, these two concepts represent constantly evolving planning where the project is broken into small components over a less determined timeline versus project planning that is done in a linear fashion with a specific development plan structured specific scope, schedule and cost estimates.

      Key distinction - adaptive vs. predictive

    Tags

    Annotators

  12. Dec 2018
    1. il n'est pas possible d'identifier plusieurs niveaux d'énonciation

      Attention, là je crois que tu t'avances trop! Tu dis à la fin du paragraphe: "Selon la théorie de l'éditorialisation il y a des dynamiques scripturales qui font émerger des organisations spatiales desquelles émergent ensuite des éléments qu'on peut hypostasier en auteur, éditeur, support, architexte etc." et je suis d'accord avec cette phrase, qui est un peu le noyau de la méta-ontologie. Mais si les énonciateurs, l'énonciation, voire les dispositifs collectifs d'énonciation émergent, alors ils existent. Mais s'ils existent, pourquoi interdire l'identification de niveaux? Pourquoi appauvrir a priori la description, l'analyse...?

  13. Nov 2016
    1. "There is not a writer in our classrooms today who will not be producing something with a digital writing tool in her or his lifetime."

      Almost all of the tools that I think most folks put in the digital writing camp are binary doppelgangers of their analogues. For example, Power point as used is mostly a flip chart with more bells and whistles. Note taking apps are 3X5 cards with a digital twist. Even hypothes.is is just marginalia with a social bent. So what I propose is that what we teach is how to apply ANY tool to the task at hand. What that means is that we need worthwhile work for our students and we need to do that work using the tools at hand. And by 'tools' I mean digital, analog, and any other that can be pressed into the larger service of gather, making sense of and sharing the problems and questions and solutions and stories of the world.

  14. Feb 2014
    1. I t i s t h i s b e d r o c k p r i n c i p l e o f c o p y r i g h t t h a t m a n d a t e s t h e l a w ' s s e e m i n g l y d i s p a r a t e t r e a t m e n t o f f a c t s a n d f a c t u a l c o m p i l a t i o n s . " N o o n e m a y c l a i m o r i g i n a l i t y a s t o f a c t s . " I d . , § 2 . 1 1 [ A ] , p . 2 - 1 5 7 . T h i s i s b e c a u s e f a c t s d o n o t o w e t h e i r o r i g i n t o a n a c t o f a u t h o r s h i p . T h e d i s t i n c t i o n i s o n e b e t w e e n c r e a t i o n a n d d i s c o v e r y : T h e f i r s t p e r s o n t o f i n d a n d r e p o r t a p a r t i c u l a r f a c t h a s n o t c r e a t e d t h e f a c t ; h e o r s h e h a s m e r e l y d i s c o v e r e d i t s e x i s t e n c e . T o b o r r o w f r o m B u r r o w - G i l e s , o n e w h o d i s c o v e r s a f a c t i s n o t i t s " m a k e r " o r " o r i g i n a t o r . " 1 1 1 U . S . , a t 5 8 . " T h e d i s c o v e r e r m e r e l y f i n d s a n d r e c o r d s . " N i m m e r § 2 . 0 3 [ E ] .

      No one may claim originality to facts because facts do not owe their origin to an act of authorship. The distinction is one between creation vs discovery.

  15. Nov 2013
    1. What men avoid by excluding the liar is not so much being defrauded as it is being harmed by means of fraud. Thus, even at this stage, what they hate is basically not deception itself, but rather the unpleasant, hated consequences of certain sorts of deception.

      Critical distinction regarding the process of "selection"; from his central thesis.

  16. Sep 2013