for - urban planetary boundaries - barriers to transition - downscaled planetary boundaries - barriers to transition - cross-scale translation of earth system boundaries - barriers to transition - question - retrofitting cities to stay within the doughnut - what are the challenges?

Noise is anything interfering with clear communication; distractions that occur during communication that resolves in misinterpretation.

Internal noise: psychological or physical problem someone is dealing with during communication

External noise : Environmental components that cause distraction

Semantic noise: a disturbance in the transmission of a message; interferes with interpretation of the message due to words having more than one meaning.

A connotation: positive or negative emotional connection to a definition. connotative semantic noise is more of an emotional issue with the intended use of words.

Denotation: the literal meaning of a word; denotative semantic noise: when we hear or see language we cannot define therefore we cannot interpret.

[[Devon Price]] in Laziness Does Not Exist - Human Parts

Archive copy without paywall: https://web.archive.org/web/20191231131144/https://humanparts.medium.com/laziness-does-not-exist-3af27e312d01?gi=e119027675fe

• key finding
  • some systems of power have absolutely no barriers
• comment
  • when there are no barriers, then power seekers will have opportunity to actualize power

For this to all work, it requires a broad ecosystem to buy in to its ubiquity. However many of the key constituencies are operating in their own silos, functioning independent of other stakeholders who's co-dependence is essential.

https://mxb.dev/blog/the-indieweb-for-everyone/

Being willing to capture an idea by spending the time writing it out in full is an incredibly strong indicator that it is actually worth capturing. Often those who use cut and paste or other digital means for their note capture will over-collect because the barrier is low and simple.

More often than not, if one doesn't have some sort of barrier for capturing notes, they will become a burden and ultimately a scrap heap of generally useless ideas.

In the end, experience will eventually dictate one's practice as, over time, one will develop an internal gut feeling of what is really worth collecting and what isn't. Don't let your not having this at the beginning deter you. Collect and process and over time, you'll balance out what is useful.

3.1 Recognize your two barriers

https://thejollyteapot.com/2022/01/5/ben-smith-s-new-media-venture-could-be-the-one-i-ve-been-looking-for

Time in the US, Immigration status, Lost opportunities

Jean-Jacques, M., & Bauchner, H. (2021). Vaccine Distribution—Equity Left Behind? JAMA. https://doi.org/10.1001/jama.2021.1205

Services like [[InkBlot]], your works [[Health Care Spending Account]] - in the past I had good luck with the Aspiria - they got me setup with a good therapist from Shift Collab Therapy

Even trying to figure out what my starting point was too much - but being able to use a service like that to help connect me was really important.

there are also some concerns around the safety and privacy of some of the online health providers.

If they require a video call - high speed internet access can be a limiting factor.

Some people may not be able to get the privacy that they need to take a call without a spouse or family member around.

I'm not even really sure what this entails. Are we saying "don't even bother thinking about creating an open textbook until you're a master of UDL." Seems like a bit of a barrier to entry/participation.

Might be a more effective carrot than a stick. Something like, "hey, there are people here who speak UDL, so if you're a subject matter expert or a pedagogy person maybe it makes sense to team up." So far I'm not hearing so much of that at Rebus. I'm hearing more "these are our priorities and they should be yours too."

This reminds me of Siegert's notion of creating barriers and categories ("cuts").

This was an excellent article Chen (2007) in defining and laying out how a blended learning approach of objectivist and constructivist instructional strategies work well in online instruction and the use of an actual online course as a study example.

RATING: 4/5 (rating based upon a score system 1 to 5, 1= lowest 5=highest in terms of content, veracity, easiness of use etc.)

This article explores the interaction of student based learner-centered used of technology tools such as wikis, blogs and podcasts as new and emerging technology tools. With distance learning programs becoming more and more popular, software applications such as Writeboard, InstaCol and Imeem may become less of the software of choice. The article looks closely at the influence of technology and outcomes.

RATING: 4/5 (rating based upon a score system 1 to 5, 1= lowest 5=highest in terms of content, veracity, easiness of use etc.)

This is certainly true. It reminds me of the early historical growth of the Catholic church. Paul of Tarses came in and relaxed the dietary restrictions and the need for circumcision which effectively lowered the barrier for entry into the church. One needn't be a Jew to be a follower of Jesus; this helped early growth tremendously.

Simple awareness still huge issue

The most important take-away I see in this whole section on reasons for not making data electronically available is not mentioned here directly!

Here are the raw numbers for I am satisfied with my ability to integrate data from disparate sources to address research questions:

• 156 (12.2%) Agree Strongly
• 419 (32.7%) Agree Somewhat
• 363 (28.3%) Neither Agree nor Disagree
• 275 (21.5%) Disagree Somewhat
• 069 (05.4%) Disagree Strongly

Of the people who are not satisfied in some way, how many of those think current data sharing mechanisms are sufficient for their needs?

Of the ~5% of people who are strongly dissatisfied, how many of those are willing to spend time, energy, and money on new sharing mechanisms, especially ones that are not yet proven? If they are willing to do so, then what measurable result or impact will the new mechanism have over the status quo?

Who feel that current sharing mechanisms stand in the way of publications, tenure, promotion, or being cited?

Of those who are dissatisfied, how many have existing investment in infrastructure versus those who are new and will be investing versus those who cannot invest in old or new?

10 years ago how would you have convinced someone they need an iPad or Android smartphone?

Policies and procedures are barriers, but there are many more barriers beyond that which get in the way first.

What is the sharing standard? What are the consequences of not sharing? What is the enforcement mechanism?

There are three primary sharing mechanisms I can think of today: email, usb stick, and dropbox (née ftp).

The dropbox option is supplanting ftp which comes from another era, but still satisfies an important niche for larger data sets and/or higher-volume or anonymous traffic.

Dropbox, email and usb are all easily accessible parts of the day-to-day consumer workflow; they are all trivial to set up without institutional support or, importantly, permission.

An email account is already provisioned by default for everyone or, if the institutional email offerings are not sufficient, a person may easily set up a 3rd-party email account with no permission or hassle.

Data management alternatives to these three options will have slow or no adoption until the barriers to access and use are as low as email; the cost of entry needs to be no more than *a web browser, an email address, and no special permission required".

If thriving is a metric (is it measurable? too subjective?) of success then the 3 characteristics it must have are:

• modularity: divisible into components
• granularity: fine-grained modularity
• integrability: low-cost integration of contributions

I don't dispute that these characteristics are needed, but they are too general to be helpful, so I propose that we look at these three characteristics through the lens of the type of contributor we are seeking to motivate.

How do these characteristics inform what we should focus on to remove barriers to collaboration for each of these contributor-types?

Below I've made up a rough list of lenses. Maybe you have links or references that have already made these classifications better than I have... if so, share them!

Roughly here are the classifications of the types of relationships to open source projects that I commonly see:

• core developers: either hired by a company, foundation, or some entity to work on the project. These people care most about integrability.

• ecosystem contributors: someone either self-motivated or who receives a reward via some mechanism outside the institution that funds the core developers (e.g. reputation, portfolio for future job prospects, tools and platforms that support a consulting business, etc). These people care most about modularity.

• feature-driven contributors: The project is useful out-of-the-box for these people and rather than build their own tool from scratch they see that it is possible for the tool to work they way they want by merely contributing code or at least a feature-request based on their idea. These people care most about granularity.

The above lenses fit the characteristics outlined in the article, but below are other contributor-types that don't directly care about these characteristics.

• the funder: a company, foundation, crowd, or some other funding body that directly funds the core developers to work on the project for hire.

• consumer contributors: This class of people might not even be aware that they are contributors, but simply using the project returns direct benefits through logs and other instrumented uses of the tool to generate data that can be used to improve the project.

• knowledge-driven contributors: These contributors are most likely closest to the ecosystem contributors, maybe even a sub-species of those, that contribute to documentation and learning the system; they may be less-skilled at coding, but still serve a valuable part of the community even if they are not committing to the core code base.

• failure-driven contributors: A primary source of bug reports and may also be any one of the other lenses.

What other lenses might be useful to look through? What characteristics are we missing? How can we reduce barriers to contribution for each of these contributor types?

I feel that there are plenty of motivations... but what barriers exist and what motivations are sufficient for enough people to be willing to surmount those barriers? I think it may be easier to focus on the barriers to make contributing less painful for the already-convinced, than to think about the motivators for those needing to be convinced-- I think the consumer contributors are some of the very best suited to convince the unconvinced; our job should be to remove the barriers for people at each stage of community we are trying to build.

A note to the awesome folks at Hypothes.is who are reading our consumer contributions... given the current state of the hypothes.is project, what class of contributors are you most in need of?