Confusion about what it means toown a book leads people to a falsereverence for paper, binding, and type—a respect for the physical thing—thecraft of the printer rather than thegenius of the author.

It will be seen from the foregoing that care isrequired in the appKcation of the card system,and that neglect must sooner or later lead to failure. There wasindeed a time when it seemed doubtful whether the card systemwould survive the first attempts. It was even tried and abandonedby some. These early failures were in the main due to the absenceof expert labour and to the higher order of accuracy required ascompared with the book system. The systems were not thenplanned out with that care that is bestowed upon them now. Onesystem would be started and presently there would be a decisionto alter it so as to fall in with riper experience. In the absenceof one system consistently adhered to the files soon got into achaotic condition until at last they had to be abandoned, for infact they had become useless.

I think the above answers what you actually wanted to know, but to go ahead and answer the question you explicitly asked...

"A surveyor from Roberval will be in the parish next week. If anyone wishes his land surveyed before mending his fences for the summer, this is to let him know.

As Thoreau said, “We do not ride on the railroad; it rides upon us”;and this is what we must fight, in our time. The question is, indeed,Which is to be master? Will we survive our technologies?

We do not ride on the railroad; it rides uponus. Did you ever think what those sleepers are thatunderlie the railroad ? Each one is a man, an Irish¬man, or a Yankee man. The rails are laid on them, andthey are covered with sand, and the cars run smoothlyover them. They are sound sleepers, I assure you.And every few years a new lot is laid down and runover; so that, if some have the pleasure of riding on arail, others have the misfortune to be ridden upon.

But lo!men have become the tools of their tools. The manwho independently plucked the fruits when he was hun¬gry is become a farmer; and he who stood under a treefor shelter, a housekeeper.

one of the greatest martial arts artists ever was bruce lee who i actually read a lot of his writings

But if we are downloaded into our technology, what are the chancesthat we will thereafter be ourselves or even human?

What they say is this is due to is new EU policies about messenger apps. I'm not in the EU. I reckon it's really because there's a new Messenger desktop client for Windows 10, which does have these features. Downloading the app gives FB access to more data from your machine to sell to companies for personalized advertising purposes.

If it's dangerous, note it in the class/method Javadocs, don't just blindly slam the door shut.

Please can we (a) retain case information from the email address the student uses to set up their account (in case their mailbox is case sensitive), and use that when sending password reset emails, etc., but also (b) when checking credentials for login or setting up an account, treat the email address as non-case-sensitive. The upshot would be if someone registered with Student@City.ac.uk, all emails would go to Student@City.ac.uk, but the student would be able to log in with student@city.ac.uk, and if someone later tried to set up an account with student@city.ac.uk they'd be told that the user already exists.

Although there's an argument for keeping case sensitivity for the local mailbox (as they can be case sensitive, depending on how they're set up, though I haven't come across case sensitivity in university emails), the domain part of the email address is not case sensitive and should not be treated as such. Please can we (a) retain case information from the email address the student uses to set up their account (in case their mailbox is case sensitive), and use that when sending password reset emails, etc., but also (b) when checking credentials for login or setting up an account, treat the email address as non-case-sensitive. The upshot would be if someone registered with Student@City.ac.uk, all emails would go to Student@City.ac.uk, but the student would be able to log in with student@city.ac.uk, and if someone later tried to set up an account with student@city.ac.uk they'd be told that the user already exists.

If you are storing email addresses then you probably should store them in their original case (the recipient at least) to be safe. However, always compare them case-insensitively in order to avoid duplicates.

However, it's difficult to rely on a case-sensitive email address in the real world because many systems (typically ones that have to handle data merging) don't preserve case. Notably systems that use email addresses for user IDs, or any system that has to collate data from multiple sources (CRMs, email broadcast systems, etc) will either normalise case or treat them case-insensitively.

However, for all practical purposes in the modern age, I believe you can consider email addresses to be case insensitive.

a SHOULD is always trumped in RFCs by a MUST. The fact that hosts SHOULD do something means that they might not and I just wanted reassurance that, in reality, the SHOULD is a bit more widely adopted than its definition implies.

While email addresses are only partially case-sensitive, it is generally safe to think of them as case insensitive. All major providers, such as Gmail, Yahoo Mail, Hotmail, and others, treat the local parts of email addresses as case insensitive.

According to RFC 5321, the local part of the email address is case sensitive. This means that, in theory, SoMething@something.com is not the same as something@something.com. However, email providers have the liberty to treat the local parts as both case sensitive and case insensitive.

Are Email Addresses Case Sensitive? Technically, the answer is yes. However, email addresses are typically not case sensitive; if you type your email address into a form and accidentally capitalize one or two letters, it probably won’t prevent the sender from emailing you.

The local part does, in fact, take the case into account, as per RFC 5321. However, Email Service Providers (ESPs) are aware of the potential confusion that could result from allowing upper-case letters.

In short, while it’s technically possible to make the part before @ case sensitive, most popular email servers do not allow that. 

Most big email providers like Gmail, Outlook and even company email address hosted on Google Suite are not case sensitive. Just to avoid any unnecessary confusion. However, in extreme cases, some large companies, implement case sensitivity on their server as some people can often have the same first and last name. But in general, this creates more confusion, than the usability, which is why most standard email providers avoid case sensitivity. 

Either way, at some point almost everyone started treating addresses as case-insensitive.

Despite it being commonplace to “fix up” email addresses by lowercasing them — or, in financial/government contexts, uppercasing them — email addresses are clearly defined as case-sensitive in the only standard that matters.

Since using case insensitivity is so widespread, take their sign up email address and make it lower case. Whenever they try to log in, convert that to lowercase as well, for comparison purposes, when you go to see if the user exists. As far as sign up and sign in go, do a case insensitive comparison. If the person signs up as Steve@example.com, you'll still want to allow them to sign in later with steve@example.com or sTeVE@example.com.

But you should also keep track of the email address that they signed up with in a case sensitive fashion. Any time you send an email to them, be sure to send it with that original casing. This allows the email server to handle it however it feels like it needs to. So even though the person may always be signing in to your site with steve@example.com, if they signed up as Steve@example.com, you'll always send email to Steve@example.com, just to be safe.

The de facto standard is to treat local mailboxes as case insensitive, but the official standard says case matters (though even the official standard mentions the de facto standard).

So yes, the part before the "@" could be case-sensitive, since it is entirely under the control of the host system. In practice though, no widely used mail systems distinguish different addresses based on case.

In short, you are safe to treat email addresses as case-insensitive.

Since the case sensitivity of email addresses can create confusion and delivery problems, most email providers and clients either fix the case if the email address is entered in the wrong case, or they ignore upper-case entries. Not many email services or ISPs enforce case-sensitive email addresses.

It is safe to predict that in the near future intelligence tests will bring tens of thousands of these high-grade defectives under the surveillance and protection of society. This will ultimately result in curtailing the reproduction of feeble-mindedness and in the elimination of an enormous amount of crime, pauperism, and industrial inefficiency. It is hardly necessary to emphasize that the high-grade cases, of the type now so frequently overlooked, are precisely the ones whose guardianship it is most important for the State to assume.

People know it’s bad but not how bad. This gap in understanding remains wide enough for denialists and minimisers to legitimise inadequate action under the camouflage of empty eco-jargon and false optimism. This gap allows nations, corporations and individuals to remain distracted by short-term crises, which, however serious, pale into insignificance compared with the unprecedented threat of climate change.

个人学习可能取决于他人行为的主张突出了将学习环境视为一个涉及多个互动参与者的系统的重要性

I do not care to include the epistemological status (claim, idea, quote etc) anymore as I was not actively searching for it and it was nebulous in practice, as you've found out.

Let’s say the recipient is considering unsubscribing. He or she may be too busy to search through the email to find the unsubscribe link, so he or she just clicks “Report as SPAM” to stop the emails from coming. This is the last thing any marketer wants to see happen. It negatively impacts sender reputation, requiring extra work to improve email deliverability. With the list-unsubscribe header, you will avoid getting into this kind of trouble in the first place.

We decided to follow their rules to stay in their affiliate program, because that's how we are able to actually run the site (without any ads).And if you look on the issue from the usability point of view, not having their price history isn't that big of a deal, unless the game is sold only on Amazon - and most games aren't - so you always have other stores to compare the price to.

4.2 Meaningful work and meaningful relationships aren’t just nice things we chose for ourselves—they are genetically programmed into us.

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.

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.

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.

If the ticket is incorrect or damaged, you cannot even go through the airport security: when they check your ticket, it will be refused. You are Forbidden to enter the boarding area of the airport.

status code 401 has been removed from that RFC

I'm trying to help in some way by bringing these issues to light so a discussion about them can take place.

the primary causes of extreme poverty are immaterial, theylie in certain deficiencies in education, organization, and discipline”(p. 159). Poorcountries, in his view, did not need more technology or physical infrastructure ormore foreign aid to eliminate poverty.

This library on GitHub solves the cross-domain problem, along with making sure the iFrame stays sized to the content when things change. github.com/davidjbradshaw/iframe-resizer

There are times to stretch individually and as a team, but there are also times to take advantage of what you already know.

Configuration style is exactly the same for env_bang and env_setting, only that there's no "ENV!" method... just the normal class: EnvSetting that is called and configured.

You could also opt to extend your Rails configuration object: Envy.init use: MyApp::Application.config MyApp::Application.config.my_variable # => ...

one of the following package repositories:

We’re the ones who code. The people you talk to are the people who work on your project. When you have a question, we know what we are talking about.

Neither question nor answer appears to understand the notion of semantic HTML. Height and width are presentational attributes regardless of where you put them. For semantics we establish what the image means to content in the alt tag. I don't remember why it was so important to width/height in the HTML but I suspect it was in case you hit browsers without CSS rendering. It's not a semantics issue. If anything it thwarts separation of concerns to a degree.

The reviewer made a mistake, either in actual play or just in writing the review.

Scholar@UC: University of Cincinnati's self-submission institutional repository

Essentially after any edit of any js file if we reload /qunit it takes us about 10 seconds for the page to render.

I was debugging our painfully slow reload times in Discourse when running qunit.

I don't get it. Can someone please explain? I've upgraded my Rails project to Sprockets 4, just to get source maps in production. Instead I got sourcemaps in development?

Before a bug can be fixed, it has to be understood and reproduced. For every issue, a maintainer gets, they have to decipher what was supposed to happen and then spend minutes or hours piecing together their reproduction. Usually, they can’t get it right, so they have to ask for clarification. This back-and-forth process takes lots of energy and wastes everyone’s time. Instead, it’s better to provide an example app from the beginning. At the end of the day, would you rather maintainers spend their time making example apps or fixing issues?

Fibar bi jàngal na taawan bu góor ni ñuy dagge reeni aloom.

Shepard said at the time, "They Live was the basis for my use of the word 'obey,' The movie has a very strong message about the power of commercialism and the way that people are manipulated by advertising. [...] One of my main concepts with the Obey campaign as a whole was that obedience is the most valuable currency. People rarely consider how much power they sacrifice by blindly following a self-serving corporation's marketing agenda, and how their spending habits reflect the direction in which they choose to transfer power."

Since we're not passing any inputs to ListAccounts, it makes sense to use .run! instead of .run. If it failed, that would mean we probably messed up writing the interaction.

As a workaround, I guess I'll have to disable my strict CSP in development, but I'd prefer to keep it strict in development as well so that I ran into any CSP issues sooner...

What this means is: I better refrain from writing a new book and we rather focus on more and better docs.

Can't have a steam library without MMX.

I feel like I should've paid more for this masterpiece.

My understanding of "programming to an interface" is different than what the question or the other answers suggest. Which is not to say that my understanding is correct, or that the things in the other answers aren't good ideas, just that they're not what I think of when I hear that term.

Creating more legally binding licenses and contracts just perpetuates the problem of law – a.k.a. state force – intruding where it doesn’t belong.

We do know what our customers ask us for: powerful desktops and laptops that work with them in their creative endeavors. And we know that Canonical is no longer interested in catering to them. So we're going to try and step up.

We don’t do politics, and we certainly don’t do religion. You’re bringing these here by using terms such as “politicians” or “evil”.

You stick with what you know. It's trouble free because you know how to use it. That's achievable on any of the main OSs, even (gasp!) Windows.

Can I use the title attribute?Yes. The content prop can be a function that receives the reference element as an argument and returns a string or element.tippy('button', { content(reference) { const title = reference.getAttribute('title'); reference.removeAttribute('title'); return title; }, });The title attribute should be removed once you have its content so the browser's default tooltip isn't displayed along with the tippy.

It must be called during the component's initialisation (but doesn't need to live inside the component; it can be called from an external module).

You should default to the most permissive option imo and there really is no reason to check anything until you really need to If it were left to me I'd just use optional chaining, as it also eliminates the need for no-ops

new Cmp will render to the DOM synchronously, so you don't have to worry about the content flickering because the component is rendered too late.

Headless: With React's DOM rendering for improved usage with CSS-in-JS and spring libraries. If you want greater control over your poppers to integrate fully with design systems, this is for you.

We can make content a function that receives the reference element (button in this case) and returns template content:

You can pass the element itself, which is useful for keeping event listeners attached (or when a framework is controlling elements inside):

Allows you to separate the tippy's positioning from its trigger source.

Sets whether the menu surface should open and close without animation when the open/close methods are called.

Adding layer of settings and complexity for the end user might also bring bad practices to keep a comfortable use of app’s by installing snap without confinement…

The “no-snaps” ship already sailed years ago…you folks missed that boat. It’s too late to wish for a return to the past. Snaps in Ubuntu have been happening for years already, and will continue regardless of any opinions expressed here.

But, I am a little bit confused about what to do now, mark your answer as correct and create new question, or create and EDIT block to this post?

You’re in good companyTrusted by leaders at some of the world’s most inspired organizations

you cannot pass around components very flexibly, you cannot take a component as a parameter

To stay up-to-date with the new parts, just follow this medium or observe me on Twitter. In case you need some help, remember that I am open for consultation.

emphasizing that 'this' and 'global object' are two different things not only in Node.js but in JavaScript in general

I love the Material Design System’s buttons just because their principles are really well thought through.

I hope @hperrin you're still alive to discuss about this and eventually for a pull request.

@monkeythedev I am curious how do you "organize" your work - You forked https://github.com/hperrin/svelte-material-ui and https://github.com/hperrin/svelte-material-ui is not very active. Do you plan an independent project ? I hope the original author would return at some times, if not, i'll see

Maybe @hperrin would be able to make an appearance and select a few additional maintainers to help out.

There is no rerender, when you call listen, then all scroll events will warn on chrome. See this entry from svelte: breaking the web

I prefer light stock taking games like American Rails.

I find the binding of Mini Express pleasant.

Ultimately, I’m an “are there tough decisions?” kind of gamer, and on that matter I’m torn. There are some turns and some positions and some situations that will play themselves. Sometimes obviously so, and sometimes after you think it out.

I’m fan of maps (in real life and in games), and the map play here is interesting

What vaults this well past SNCF for me (setup time aside), is the limited company choice; it prevents a feedback loop of sorts where a game devolves into running each company in the ground.

Who’s Using Snowpack?

Used by folks at

Never use x && y || z when y can return a non-zero exit status.

I think what the author intended to do was check if the second argument was a non-empty string (which is not the same thing as checking whether there are more than 1 argument, as the second argument could be passed but be the empty string).

However, this construct is not completely equivalent to if ... fi in the general case.

Some people try to use && and || as a shortcut syntax for if ... then ... else ... fi, perhaps because they think they are being clever.

You can support my work on this project through my other project, Tunnelgram.

Quick self-promotion plug (but in the name of altruism)

Over 4 million people trust CloudApp

unnecessary evil

Wondering how to get field state from multiple fields at once? People coming from Redux-Form might be wondering where the equivalent of Redux Form's Fields component is, as a way to get state from several fields at once. The answer is that it's not included in the library because it's so easy to write one recursively composing Field components together.