Showing 73–84 of 110 articles
A rumour travels quickly when it tries to care, before sharing with the whole community: Citizenship and networks
A rumour can begin with a legitimate concern and cause harm when shared unchecked. A community needs context, verification channels, and repair in order to care without amplifying suspicion.
Read article
Conflict is not resolved by adding another screen, before sharing with the whole community: Citizenship and networks
A network conflict is not fixed by another screen. A community needs understandable rules, mediation, repair, and reviewable decisions to participate without undue exposure.
Read article
The exception reveals the quality of the system, before sharing with the whole community: Citizenship and networks
Exceptions show whether a network and community offer real alternatives or rules only for the usual case. A fair system retains context, repair, and routes to participation.
Read article
A useful figure can also lead us to the wrong place, before sharing with the whole community: Citizenship and networks
A metric can signal a problem, but it cannot explain a life by itself or authorise surveillance. In networks and communities, measurement needs context, limits, and alternatives.
Read article
Accepting does not always mean being able to choose, before sharing with the whole community: Citizenship and networks
Consent is meaningful only when a clear, workable alternative exists. In networks and community spaces, accepting must not be the price of belonging.
Read article
The first question must come before the tool, before sharing with the whole community: Citizenship and networks
A community tool becomes meaningful when the public question comes before the platform: it defines what is shared, who decides, and how harm is repaired.
Read article
After launch, the important work begins when an app asks for information: Privacy and data
Launch does not close data decisions. An app must observe failures without turning every use into a profile, explain changes, and correct permissions when real service reveals different needs.
Read article
A useful number can still lead us to the wrong place when an app asks for information: Privacy and data
Metrics help detect failures, but they do not justify collecting every available datum. A responsible app measures what is necessary, explains its limits, and retains human alternatives.
Read article
Accepting does not always mean being able to choose when an app asks for information: Privacy and data
Acceptance is meaningful only when an app explains which data it needs, why it will use them, and provides real alternatives. Privacy needs understandable decisions, not default permissions.
Read article
The first question must come before the tool when an app asks for information: Privacy and data
Before asking for data, an app should explain its purpose, offer an alternative, and limit collection to what is essential. The first question protects privacy and improves the service.
Read article
Participation changes the question and improves the answer around an automatic response: Everyday artificial intelligence
Participation turns an automatic response into a service that can be corrected: it makes room to identify errors, add context, and decide what improves without shifting every burden to the recipient.
Read article
Care also means not monitoring everything around an automatic response: Everyday artificial intelligence
Care around an automatic response does not mean recording every action: it means limiting data, providing a human route, and reviewing only what is needed to correct harm.
Read article