SearcharxivSearch

arXiv subjects

Carmel Schare

Publications and source records attributed to Carmel Schare.

2 recordsLinked to original sources

Social.Wiki: A Web Held in Common

Many of the websites people depend on have owners whose interests are not fully aligned with their users. We address the root of this problem by presenting a reimagining of the web where sites are not owned at all but are instead collaboratively produced like Wikipedia articles. We call the system Social$.$Wiki because it supports the co-creation of interactive social sites, such as those for microblogging, messaging, dating, gaming, ride sharing, and so on. With off-the-shelf AI tools, people with little or no programming experience can edit these sites to better reflect the needs and preferences of their communities. Social$.$Wiki builds on ideas from collaborative malleable software systems such as Webstrates, but is designed for public participation rather than use only within small, trusted groups. To this end, Social$.$Wiki includes governance to mitigate conflict. To accommodate diverse governance preferences, our model of "plural governance" lets people independently choose the policies that determine which edits to a site they see. Social$.$Wiki also implements a granular security model to protect personal data in a malleable environment. Complementing the decentralized design and governance of Social$.$Wiki sites, both site edits and within-site data are stored on Graffiti, a decentralized infrastructure, decoupling the ownership of underlying servers from the ownership of sites. We evaluate Social$.$Wiki through case studies that demonstrate the range of sociotechnical structures it supports, as well as through deployments at a hackathon and in the wild.

cs.SI

Making Software Meaningful

Adopting a single measure can improve the usability, modularity and accountability of software: a commitment to explicit meaning. This entails constructing and agreeing upon a representation of the behavior of the software, as observed in the domain of application. The phenomena comprising this behavior become a vocabulary that grounds all discourse about the software, among all stakeholders, and for all artifacts and activities. These phenomena are individuals; actions they participate in; and facts that result from actions. They can be organized, by partitioning the set of actions, into concepts, offering larger units of meaning. Examples of exploiting meaning are given in three areas: designing for usability (by aligning user and designer on a single shared meaning); generating modular code with LLMs (by mapping units of meaning to units of code, achieving not only modularity but also legibility); and making agents accountable (by having them adhere to a code of conduct that defines their intended behavior).

cs.SE