… aaand it’s gone – they did indeed decide to remove the option flag, as they always do

This will fix the problem, as long as the Chrome developers do not decide to remove this option.

Users will no longer have access to their Mint accounts on March 23, 2024

Fielding’s dissertation isn’t about web service APIs at all

I'd argue that when you find a programming language devoid of danger, you've found one that's not very useful.

For example, still not over the death of Google Reader after all these years? Why not host your own RSS aggregator like Sismics Reader that nobody can ever take away from you?

This allows the system designer to permit trusted programs to be run which a user would otherwise not be allowed to execute.

Configuring PyCharm: Open PyCharm with ‘Pytest Web Framework’ Press Ctrl+Alt+S > Project Click ‘Project Interpreter’ Select Python 3.6 Click ‘OK’ Go to write over 100500 automated tests!!!

So now we have a file that you need to open in JMeter UI, configure number of threads that you want to execute and you are good to go.

Let’s add a test that will validate that number of results on a page is lower then total number of results.

I'm curious: what is the reason for Yahoo discontinuing the "@ymail.com" domain?I'm aware that there's now a 2nd domain option available, "@myyahoo.com", and I recently took advantage of that to create a new address. But "@ymail.com" honestly looks more appealing to me than either of the "yahoo" iterations.

First, to clarify - what is "code", what is "data"? In this article, when I say "code", I mean something a human has written, that will be read by a machine (another program or hardware). When I say "data", I mean something a machine has written, that may be read by a machine, a human, or both. Therefore, a configuration file where you set logging.level = DEBUG is code, while virtual machine instructions emitted by a compiler are data. Of course, code is data, but I think this over-simplified view (humans write code, machines write data) will serve us best for now...

Well I would like to express my huge concern regarding the withdrawal of support for the SMB 1.0 network protocol in Windows 11, and future versions of the Microsoft OS, as there are many, many users who need to make use of this communication protocol, especially users households, since there are hundreds of thousands of products that use the embedded Linux operating system on devices that still use the SMB 1.0 protocol, and many devices, such as media players and NAS, that have been discontinued and companies no longer update their firmware.

here was that elasticity of mind, that disposition to be comforted, that power of turning readily from evil to good, and of finding employment which carried her out of herself, which was from nature alone

glad to be thought of some use

This just happened to me and it was because I was signed in to my work account at the same time.  I went to "sign out all" and signed in again and they reappeared

GitLab self-monitoring gives administrators of self-hosted GitLab instances the tools to monitor the health of their instances. This feature is deprecated in GitLab 14.9, and is scheduled for removal in 15.0.

efficient (and thus time-saving) interfaces

Raskin coined the term and founded the field of cognetics, the ergonomics of the mind

For example, suppose your API returns a 401 Unauthorized status code with an error description like The access token is expired. In this case, it gives information about the token itself to a potential attacker. The same happens when your API responds with a 403 Forbidden status code and reports the missing scope or privilege.

Caution: This is NOT the current local time in most locations in that time zone North America: Only some locations are currently on MST because most places in this time zone are currently on summer time / daylight saving time and are observing MDT.

Mountain Standard Time (MST) is 1 hour ahead of Pacific Standard Time (PST). To convert MST to PST, you have to subtract one hour.

I deliver PDFs daily as an art director; not ideal, but they work in most cases. There's certainly nothing rebellious or non-commercial about them

I'm happy to hear this is still useful 4 years later. The Internet is great!

Linking directly to someone’s blog comment is very useful. Even if a blog doesn’t have an active link for each comment, it’s pretty easy to use developer tools to find the comment’s id and link to it. I’ve done this many times on Smashing Magazine (they don’t have live links on each comment). If there was no way to link to an individual blog comment, this would be a great hindrance to linking on the web. It would not be enough to link to the “#comments” section and then hope for the best. So CMSs like WordPress do the right thing by dynamically adding a unique identifier to each comment.

I don't know why but they just removed some featuresAt first, you can't play this with your friend online except waiting for random matchingYou can't invite your friends to your closed room and play togheter

Today, many users rely upon graphical user interfaces and menu-driven interactions. However, some programming and maintenance tasks may not have a graphical user interface and may still use a command line.

But floats are still useful and relevant! In fact, we have to use them for the shape-outside property to work.

However, if the distinctions between the two concepts appear to be superficial, intentional conflation may be desirable for the sake of conciseness and recall

A product’s onceability is, to a certain extent, linked to its usefulness. If it is really useful, we will certainly go to considerable lengths to repair it.

For branching out a separate path in an activity, use the Path() macro. It’s a convenient, simple way to declare alternative routes

step :decide_type, Output(Activity::Left, :credit_card) => Track(:with_credit_card)

# Create the track, which would automatically create an implicit End with the same id.
Track(:with_credit_card) do
    step :authorize
    step :charge
end

class Example::ValidationErrorTrack < Trailblazer::Activity::Railway
  step :validate_model, Output(:failure) => Track(:validation_error)
  step :save,           Output(:failure) => Track(:validation_error)

  # Can't use fail here or the magnetic_to won't work and  Track(:validation_error) won't work
  step :log_validation_error, magnetic_to: :validation_error,
    Output(:success) => End(:validation_error), 
    Output(:failure) => End(:validation_error) 
end

puts Trailblazer::Developer.render o
Reloading...

#<Start/:default>
 {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
 {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
 {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<End/:success>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Left} => #<End/:validation_error>
 {Trailblazer::Activity::Right} => #<End/:validation_error>
#<End/:success>

#<End/:validation_error>

#<End/:failure>

class Example::ValidationErrorTrack::VPathHelper1 < Trailblazer::Activity::Railway
   validation_error_path = Path(end_id: "End.validation_error", end_task: End(:validation_error)) do
    step :log_validation_error
  end
  step :validate_model, Output(:failure) => validation_error_path
  step :save,           Output(:failure) => validation_error_path
end

o=Example::ValidationErrorTrack::VPathHelper1; puts Trailblazer::Developer.render o
Reloading...

#<Start/:default>
 {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=validate_model>
 {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<End/:validation_error>
#<Trailblazer::Activity::TaskBuilder::Task user_proc=save>
 {Trailblazer::Activity::Left} => #<Trailblazer::Activity::TaskBuilder::Task user_proc=log_validation_error>
 {Trailblazer::Activity::Right} => #<End/:success>
#<End/:success>

#<End/:validation_error>

#<End/:failure>

Record filters allow you to require an instance of a particular class (or one of its subclasses) or a value that can be used to locate an instance of the object. If the value does not match, it will call find on the class of the record. This is particularly useful when working with ActiveRecord objects.

It is impossible to rebuild the base from the Dockerfile as the 3rd party dependencies have changed significantly since 8 months ago when the base was last built. The tags for my base image have been overwritten and I can only restore them from a descendant image. With Docker 1.8 I simply pulled the descendant image, tagged the base layer and I was done. With Docker 1.10+ I'd need to save, then manually construct the base image descriptor and reload it. Doable but sad that it's far more complex.

Allowing parent layer metadata to be saved for a layer, regardless if the parent layer is in the save command, would be a huge win for those of us working on CI/remote systems. Reusing parent layers used to be ridiculously easy. It would be good if we could get some comparably easy way to do it now.

It used to be great that I was able to select a layer from any image and use it as a starting point. Currently, I am given an image that has 4 layers to be stripped off to get to the original base image. The original image is not reconstructable in any other way.

In Angular CLI 6 this command has been removed, and it will not come back. Instead there is a new concept called Builders.With the new Angular CLI you can customize the build process by defining your own builders as well as using one of the builders provided by the community.

In particular, graphical representations of learning designs have been found to stimulate design ideas for teachers who are engaged in designing a course

It is important to note here that the flow does not need to begin with a user interaction. With the rise of asynchronous middleware like redux-saga and redux-observable, the ability to trigger any code on a component anywhere is very useful.

However, as a developer that uses JSX, I find it too useful/concise to give up in the name of syntax purity, especially when I know that what it translates to is still very isolated and computationally pure.

A map is not the territory it represents, but, if correct, it has a similar structure to the territory, which accounts for its usefulness.

A new option --proximate=N groups together lines of output that are within N lines of each other in the file. This is useful when looking for matches that are related to each other.

new style RFC

Secure-by-default is a great approach, but this is not that. It's not even, we know what's best. It's clean up your act or you're out. You really should provide an opt-in to running with scissors. Maybe like config.opt_in_to_dynamic_routes_you_dumbass = true. 1 Pick your reaction

I too would like to know more about the security concerns that are the motivation to remove these useful dynamic routing components. The only thing I can think off is someone who accidentally exposes a private method public, is there more? The dynamic routes are a great way to keep the routing.rb DRY and avoid unneeded dependencies between the routing and the controller files, it has been quintessential Rails magic since version 1.0, surely there must be more serious security concerns to give up such important benefits? What are they? Do we really need to completely remove this from the code base, when removing it from the default routes.rb already would get you most of the security benefit?

I'm sure the security overlords have our best interest in mind and I'd be happy to change my opinion if someone can explain this tradeoff better. I know I can recreate the functionality for myself but I also like to keep in mind what's best for Rails. Just a hand wavy "we've had this for almost 10 years, but it might become an issue in the future so let's preventively eliminate it" does not seem a good enough reason to cut a feature that can make code much more DRY and elegant.

Sounds like Mixins are on their way out

As a later iteration, it might be cool to see a link between the quoted content and my comment

Matz, alas, I cannot offer one. You see, Ruby--coding generally--is just a hobby for me. I spend a fair bit of time answering Ruby questions on SO and would have reached for this method on many occasions had it been available. Perhaps readers with development experience (everybody but me?) could reflect on whether this method would have been useful in projects they've worked on.

which might or might not be useful depending on what is the content of the commit.

In the early 1990s, the creators of Netscape apparently built a function that enabled each web page to be annotated by those visiting it, as a way for viewers to discuss the page’s content. But according to a [1] produced in 2013 by a nonprofit called [Hypothesis][2], the feature was turned off.

but if you have any questions or need additional assistance, please let us know via our Help system or visit: http://impermium.com/typepad-antispam

First, they chose to find a new home for Tumblr instead of shutting it down. Second, they considered not just how much cash they would get on day one, but also — and especially — what would happen to the team afterward, and how the product and the team would be invested in going forward. Third, they thought about the sort of steward of the community the new owner would be. They didn’t have to do any of that, and I commend them for making all three points a priority.

We no longer provide new access to Google Translate's Website Translator. This change does not affect existing use of the Website Translator. We encourage users looking to translate webpages to use browsers that support translation natively.

Google Translate Widget

Another “decision” to make GoogleYoutube crappier and crappier with every passing day. The corporation seems stridently dedicated to deprecating its own products and abusing its customers.Search is now suckier than DuckDuckGo. Fuzzy and/or cherry-picked results.YouTube flooded with reposts/stolen vids and the “recommended” videos have literally nothing to do with your viewing behavior.Politicization and one-way censorship.Translator used to be nearly limitless (no text limit, websites translatable, etc) — now it’s basically a severely nerfed mini-tool to translate short phrases.

Instant previews saw very low usage by our users, and we’ve decided to focus on streamlining the page to benefit more users.

the feature was dropped to “lack of use.”

Yes, it’s been deprecated. Why? Because too few people were using it to make it worth the time, money, and energy to maintain. In truth, although I sometimes disagree with the operator changes, I happen to agree with this one. Maintaining ALL of the synonyms takes real time and costs us real money. Supporting this operator also increases the complexity of the code base. By dropping support for it we can free up a bunch of resources that can be used for other, more globally powerful changes.

Moving forward with v7, we've decided it's best to stop publishing the Stage presets in Babel (e.g. @babel/preset-stage-0). We didn't make this decision lightly and wanted to show the context behind the interplay between TC39, Babel, and the community.

Try doing the equivalent of #indexes without it. Not that it's especially hard, but you have to stop and work out a solutuon. When you need it, that's when you wish there were already a method for it.

AdNauseam is a work in progress, with new features continually being added, tuned, and, sometimes, deprecated. If a setting no longer appears in the settings page, we have likely found a better means of implementing the design goal.

Implementation is a new and frequently advancing field, and realistically, it’s beyond what a lot of us are going to be able to evaluate in our agencies at this point. But even taking pieces of it – especially the pieces about the importance of context for our programs and evaluations – is useful. Even if you don’t use it as an evaluative framework, the questions outlined above are good ones to ask when you’re planning your program in the first place.

you’ve got a good enough idea for a little exercise below.

Imagine you are working for a nonprofit focused on children’s health and wellness in school

Dr. Tiffany Gallicano has a helpful blog post

Vaismoradi, Turunen, and Bondas (2013).[3]

A few exemplars of studies employing Thematic Analysis:

Let’s say that you are studying empowerment of older adults in assisted living facilities by interviewing residents in a number of these facilities.

We have an ethical responsibility to treat what is shared with us by participants with a sense of respect during this process of deconstruction and reconstruction. This means that we make conscientious efforts not to twist, change, or subvert the meaning of bits of data as we break them down or as we string them back together. 

Just a brief disclaimer, this chapter is not intended to be a comprehensive resource on qualitative data analysis. It does offer you an overview of some of the diverse approaches that can be used for qualitative data analysis, but as you will read, even within each one of these approaches there is variation in how they might be implemented in a given project. If you are passionate (or at least curious 😊) about conducting qualitative research, use this as a beginning point to help you to dive deeper into some of these strategies. Before we begin reviewing some of these strategies, here a few considerations regarding ethics, cultural responsibility, and power and control that should influence your thinking and planning as you map out your data analysis plan.

When taking field notes, it is a good practice to make a quick seating chart at the beginning so you can make quick references for yourself of who is saying what.

Some common norms to include are:

We are usually relatively unfamiliar with our participants, at least on a personal level. This can make sitting down for an interview where we might be asking some deep questions a bit awkward and uncomfortable, at least at first. Because of this, we want to craft our questions in such a way that they are not off-putting, inadvertently accusatory or judgmental, or culturally insensitive.  To accomplish this we want to make sure we phrase questions in a neutral tone (e.g. “Tell me what that was like”, as opposed to, “That sounds horrible, what was that like”). To accomplish this we can shift perspectives and think about what it would be like for us to be asked these questions (especially by a stranger), and we can pilot test our questions to see how they ‘feel’ to others. Also, if we are conducting interviews on topics that may be particularly hard for people to talk about, we likely will want to start out with some questions that are easier to address prior to getting into the heavier topics. Make them relatable Unlike surveys, where researchers may not be able to explain the meaning of question, when conducting interviews, we are present to help further explain questions if there is some confusion. However, ideally our questions are as clear as possible from the beginning. This means that we avoid jargon or technical terms, we anticipate areas that might be hard to explain and try to provide some examples or a metaphor that might help to get the point across, and we do our homework to relay our questions in a cultural context that is appropriate. Like the discussion above, pilot testing our questions can be very helpful for ensuring the relatability of our questions, especially with community representatives. What sounds good in our heads as a question, might make little sense to our intended audience. Make them individually distinct, but collectively comprehensive Just like when we are developing survey questions, you don’t want to ask more than one question at the same time. This is confusing and hard to respond to for the participant, so make sure you are only asking about one idea in each question.  However, when you are thinking about your list of questions, or your whole interview guide collectively, ensure that you have comprehensively included all the ideas related to your topic. It’s extremely disheartening as a qualitative researcher that has concluded their interviews and realized there was a really important area that you failed to include in your guide. To avoid this, make sure to know the literature in your area well and talk to other people who study this area to get there perspective on what topics need to be included.

If we are using a highly structured interview guide, this suggests we are learning towards deductive science – we have a pretty good idea based on existing evidence what we are looking for and what questions we want to ask to help us test our existing understanding.  If we are using an unstructured guide, this suggests we are learning towards an inductive science approach – we start by trying to get people to elaborate extensively on open-ended questions to provide us with data that we will use to develop our understanding of this topic.

Data Gathering Strategy  Strengths  Challenges 

As a reminder, saturation is the point at which no new ideas or concepts are being presented as you continue to collect new pieces of data

Remember, qualitative research is a labor-intensive venture. While it may not require lots of fancy equipment, it requires a significant investment of people’s time and potentially other resources (e.g. space, incentives for participants, transportation). Each source of data (interviews, focus groups, observations, other artifacts), will require separate planning as you approach data gathering.

It is a resource that participants own that they choose to share with us.

As we are thinking about going out in the world to gather data, I think it can be helpful to think about the data that is shared with us a resource.

Public recruitment is most likely to be associated with convenience or quota sampling and is unlikely to be used with purposive or snowball sampling, where we need some knowledge of people and the characteristics they possess in advance.

Sampling Type Brief Description Convenience/ Availability You gather data from whatever cases/people/documents happen to be convenient Purposive You seek out elements that meet specific criteria, representing different perspectives Snowball You rely on participant referrals to recruit new participants Quota You select a designated number of cases from specified subgroups Sampling Type Strengths Challenges Convenience/ Availability Allows us to draw sample from participants who are most readily available/accessible Sample may be biased and may represent limited or skewed diversity in characteristics of participants Purposive Ensures that specific expertise, positions, or experiences are represented in sample participants It may be challenging to define purposive criteria or to locate cases that represent these criteria; restricts our potential sampling pool Snowball Accesses participant social network and community knowledge Can be helpful in gaining access to difficult to reach populations May be hard to locate initial small group of participants, concerns over privacy  – people might not want to share contacts, process may be slow or drawn-out Quota Helps to ensure specific characteristics are represented and defines quantity of each Can be challenging to fill quotas, especially for subgroups that might be more difficult to locate or reluctant to participate

Convenience or availability

Qualitative research generally exists on the idiographic end of this continuum. We are most often seeking to obtain a rich, deep, detailed understanding from a relatively small group of people.

In what ways might you be biased about this topic?

As qualitative researchers, we are often not looking to uncover one truth or hard facts about something.  We are generally seeking to expand our understanding of the breadth and depth of human experience.

Qualitative research is situated most often (though not exclusively) in an interpretivist paradigm, meaning we appreciate and try to study the unique experiences of individuals to better understand how they subjectively experience the world.

Quantitative studies are great when we want to summarize data and examine or test relationships between ideas using numbers and the power of statistics.

([pred coll] (reduce (fn [_ x] (if (pred x) (reduced x))) nil coll))

reconocer que producir alimentos y alimentar poblaciones, construir refugio y vivienda, enseñar e investigar, cuidar de los niños, los enfermos y los ancianos requiere de la movilización de la invención y la cooperación sociales.

Students critically evaluate online information by considering the credibility (truthfulness) and validity (usefulness) of the information obtained.

Stanley Milgram’s original study on obedience to authority

Appendix. Technical demonstration of the SOMprocedure

it is clear, also, that it is useful.