permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit b4fda132cd5ea6e09166e3a893f34ec1a1e355bd
parent 94914403e2df94f0b72cc9261fe67f62b7593238
Author: kattrali <kattrali@web>
Date:   Thu, 29 Aug 2024 15:11:20 +0200

add time constraint / self-obviation as experimentation prompts

Diffstat:
Mgetting_started.mdwn | 5+++--
1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/getting_started.mdwn b/getting_started.mdwn @@ -55,7 +55,7 @@ Investigate the places in your life or work involving computer use. How much energy does it use, including accessed network resources? Can it be reduced, replaced, or removed? What impact does it have on your wellbeing and your community? Is there a common task you perform online which could be moved -locally? +locally? How can computer use for a particular task be phased out? Approach computer use and acquisition with longevity in mind, considering things like whether you need to buy new hardware, or could you repurpose an old @@ -64,7 +64,8 @@ computer or device instead? Does it need to use a computer at all? When developing something new, what are you gonna use to ensure you make something that does not end up being harmful or wasteful? How will you measure the impacts of your project, like the resources used to create and run it -including energy, fresh water, and waste heat? +including energy, fresh water, and waste heat? Can your new system be +[[self-obviating|self-obviating system]]? With computation and computer tech consumerism taking such a big space in so many activities, it is very likely that a domain, a common/everyday tool, or a