Update

update_culture.md

@@ -20,4 +20,6 @@ Software updates are usually justified by "muh [security](security.md)" and "muh
 - **It is painful for the user** while at the same time being unnecessary, i.e. it's plainly artificial discomfort forced on users. The user has to keep caring about his software like some kind of [tamagotchi](tamagotchi.md), becoming a slave to it.
 - **It creates a mindset of not aiming to [finish](finished.md) anything** and [normalizes](normalization.md) this -- developers accept they release unfinished software, users accept they use unfinished software, society depends on technology that's not been finished, is buggy, unstable, randomly changing from one day to another etcetc. Update culture has a similar effect to the cancerous economic effect of [inflation](inflation.md) that prevents you from saving up money: it destroys anything that becomes static, not allowing to establish any stability.
 - **It is actually a huge security risk** (yes, we don't really buy intro security but this still holds). The developer, whoever it is, has the power to remotely push and execute any code at any time to the devices of many users. In fact this can be seen as the definition of [backdoor](backdoor.md). This is not just an issue of [proprietary](proprietary.md) software, there have been many [FOSS](foss.md) projects pushing [malware](malware.md) this way (look up e.g. the projects that targeted malware at Russians during the Russia-Ukraine war).
-- ...
+- ...
+
+Inb4 IPv7.