commit 119fa566bc62869a18c459eee4d807b280c08b0b
parent a8c511ab94b14427406802b6798b5fcce2127f8b
Author: viznut_web <viznut_web@web>
Date: Mon, 20 Jun 2022 09:52:44 +0200
empty web commit
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/BBS.mdwn b/BBS.mdwn
@@ -13,4 +13,4 @@ Some notable features of the BBS culture from the permacomputing perspective, es
* Intensity. When online time is limited (and possible even charged per minute), it needs to be used actively instead of "just idling around". Non-multitasking operating systems amplify this. Offline is the default state of mind, and online is an exception.
* Scarcity and sharing. When connection time is a limited resource, users are generally expected to contribute to the systems by message-based discussions and/or uploads instead of just passively "leeching" files. Most BBSes implemented an upload/download ratio system where files were used as "currency".
* [[File collection]]. BBSes typically host all kinds of software and other files useful for computer users. Also, before the broadband Internet, it was not feasible to redownload the same files every time they were needed, so it was also important to curate local, personal file collections.
-* [[Decentralization]]. Because of the file collection culture, nothing that is published in one place stays in that place. For message forums, there are networking systems (particularly [[Fidonet]]) for creating shared forums between several BBSes, although system-specific ("local") messaging culture is also considered important.
+* [[Decentralization]]. Because of the file collection culture, nothing that is published in one place stays in that place. For message forums, there are networking systems (particularly [[Fidonet]]) for creating shared forums between several BBSes, although system-specific ("local") messaging cultures are also considered important.
