When a system demonstrates instability, it invites people in to participate in its interpretation and direction. In fact, boyd’s critique is based on her observation that people and organizations who have upheld positive values in some aspects of their work have disregarded those values elsewhere. Schwartz’ theory of basic human values situates conformity values as oppositional to self-direction values such as autonomy (S. As I summarized in Chapter 2, much of the research about values and design emphasizes designers’ decision-making. Conversations classified here are characterized by the use of highly specific terminology, much of which originates within the IndieWeb, such as names of standards and applications. This is commensurate with my experiences building Yarns as reported in Chapter 4, VigorIgnite CBD where I performed much of the work of building on my own (albeit with influence from and collaboration with a small number of other IndieWeb developers), VigorIgnite Gummies Reviews but my overall approach was structured by the Microsub specification and norms about modularity and interoperability.
From the latter perspective, the generations model has generally predicted an accurate timeline of IndieWeb adoption. Figure 5.7 presents the distribution of terms related to IndieWeb’s technical standards across the topic model. Inclusion was identified as particularly challenging in Chapter 6. While this was discussed primarily in terms of RQ3 (i.e. identifying sources of exclusion), inclusion was evident as a value in several features of IndieWeb’s community, VigorIgnite CBD such as its code of conduct and diversity initiatives. Additionally, VigorIgnite CBD the method of identifying IndieWeb-related repositories on GitHub excludes projects that are not open-source as well as projects that are open source but hosted somewhere besides GitHub. Topic 12: Microformats. This topic concerns Microformats, the primary method for marking up machine-readable content among IndieWeb’s community. Topic 14 was labelled as “Online community management.” This topic consists mostly of discussions related to IndieWeb’s chat channels, wiki, and other aspects of online community. However, this strategy of focusing on problems that have been observed and documented within the community can lend momentum to biases. RSS is all about errantly focusing on plumbing instead of user experience.
’ve temporarily bumped bridgy user pages to show up to 100 responses. Another IndieWeb developer who created a commercial service with similar syndication features as Bridgy has written that reliance on platform APIs had been an obstacle, VigorIgnite Review especially from a business perspective, “Back when I was working on Known, investors would ask about the supplier risk of being so heavily dependent on third party APIs to provide a lot of the core value. Further, as will be further discussed in Sections 6.2.2 and 6.2.3, there is a divide between the possibilities for decision-making among developers and other IndieWeb users. The higher median for issue and network events suggests that many projects had multiple users who contributed by testing or offering feedback. Several IndieWeb contributors were developing reader software as early as 201227. Although many of these individual projects resulted in functional software that was at least useful to their creators, none achieved widespread use and readers remained a gap in IndieWeb’s collection of tools until Microsub heralded “the year of the IndieWeb reader” in 2018 (Çelik 2018). Conformity is a property of all standards, but notable here because Microsub conflicts with IndieWeb’s convention of generating standards from observed behaviour. For example, multiple topics concerned different IndieWeb technologies.
Some topics were linguistically distinct but overlapped in meaning. People in this centre are likely to have pronounced influence over the kind of discussions that take place in IndieWeb’s chat, including shifts in the prevalence of topics over time, such as increasing attention toward the topics I have labelled Events and IndieWeb building blocks, and slightly less attention toward the topic I have labelled Defining IndieWeb. This supports the observation in Chapter 4 that IndieWeb projects are largely built by individuals or small groups, and that collaboration occurs through relationships of interoperability and dependence among these projects. This indicates that actual development activities tend to focus on personal projects and small collaborations. This indicates that there is not a widespread tendency for individuals to blend the same combinations of topics in a given month. However, closer inspection identified non-event conversations concerning IndieWeb’s wiki and other topics. By contrast, the number of months in which a users’ chat messages focused on other topics was not predictive of GitHub activity. Firstly, it is important to acknowledge that this is not likely to be a measurement of all participation in GitHub repositories related to IndieWeb, but rather a measurement of participation that could be linked using the methods described in Section 3.3.4. The 3.6% of chat users who were linked to activity on GitHub are those who (a) interacted with a GitHub repository that was captured in this study, (b) registered a personal URL on IndieWeb’s list of chat-names4, and (c) linked to their personal URL from their GitHub account, or to their GitHub account from their personal URL.