permacomputing

commit 25205642e7fbb425987f3f3dd72cce9d9f91800d
parent 6213431da2fde6c6c20683ce685688ab6f6a5a6f
Author: viznut_web <viznut_web@web>
Date:   Wed,  8 Jun 2022 12:31:10 +0200

empty web commit

Diffstat:
M
WWW.mdwn
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/WWW.mdwn b/WWW.mdwn
@@ -65,7 +65,7 @@ Some questions to ask when building something on the web:
   * How easy is it to use the resources offline? (If the site consists of multiple static files, think about giving the option of downloading the content as a single file)
   * Are you fine with the idea of people sharing your content on their own sites? (If yes, put it available under a free content licence and encourage people to spread it)
   * Are there ways to use the site with a non-web protocol/client? ([[Permacomputing wiki]] can be edited via [[Git]], for example)
-  * What are you planning to use as a server? Purchasing of dedicated hardware should be avoided, but using something your community already has is a good idea. Using a time-sharing account to a small, local webhotel is a better idea than buying "cloud computing" from a multinational corporation (even if you'll only get 99.9% uptime instead of 99.999%).
+  * What are you planning to use as a server? Purchasing of dedicated hardware should be avoided, but using something your community already has is a good idea. Using a time-sharing account to a small, local webhotel is always a better idea than buying "cloud computing" from a multinational corporation (even if you'll only get 99.9% uptime instead of 99.999%).
 
 ## Software