Update

how_to.md

@@ -23,7 +23,7 @@ An important issue of many ideologies/philosophies/religions/etc. has shown to b
 
 Examples from LRS point of view:
 
-- Is it OK to ever use violence? Here LRS takes the extremist way of strongly saying no -- according to us violence is always bad and we definte this as an [axiom](axiom.md), something without a need of proof, it is the very foundation of our movement and not acknowledging it would simply mean it's not LRS anymore. However a bit of moderacy may also appear here; if for example someone uses violence in a desperate attempt to protect one's child, though we won't embrace the action we won't condemn the man either -- he committed a "sin", did something wrong, but in his situation there was really no right thing to do, so what should we blame him for, for being a subject of unfortunate situation?
+- Is it OK to ever use violence? Here LRS takes the extremist way of strongly saying no -- according to us violence is always bad and we define this as an [axiom](axiom.md), something without a need of proof, it is the very foundation of our movement and not acknowledging it would simply mean it's not LRS anymore. However a bit of moderacy may also appear here; if for example someone uses violence in a desperate attempt to protect one's child, though we won't embrace the action we won't condemn the man either -- he committed a "sin", did something wrong, but in his situation there was really no right thing to do, so what should we blame him for, for being a subject of unfortunate situation?
 - Is it OK to sometimes use proprietary software? Here for example [Richard Stallman](rms.md)/FSF/[GNU](gnu.md) take the extremist stance and say no, proprietary software is the literal [devil](devil.md) and though shalt evade it for all cost (in fact GNU will put effort in purposefully breaking compatibility with proprietary software, which is borderline capitalist behavior similar to artificial obsolescence etc.). While we agree it is a good general rule to avoid software whose purpose is almost exclusively the abuse of its user, we may be more tolerant and allow breaking the rule sometimes, because to us proprietary software is nothing set in any axiom, it is just a symptom resulting from bad society. As a non-axiom it should be a subject to constant reevaluation against the main goal. A simple commandment of "NO TOUCH NOTHING PROPRIETARY" is a good tool for a newcomer, it is a simple to follow rule of thumb that teaches him to find free replacements and alternatives, however once one becomes advanced and eventually a master of the freedom philosophy, he sees things aren't as simple to be solved by one simple rule, just as a master of music knows when to break basic rules of thumb, when to leave the scale, break the rhythm to make excellent music. Here we see it similarly: When touching proprietary software doesn't result in significant harm (such as supporting its developer, becoming addicted to it, getting abused by it, ...) and when it does significant good (e.g. inspires creation of its free clone, reveals the mechanisms by which it abuses its users, ...), it may in fact be good to do so.
 - Should you oppose your boss at work, deny to serve him in unethical practice because he is a filthy capitalist and so make trouble for yourself, possibly even get fired for it? Well, this is not so easy again; a strict extremist anticapitalist here would just stay without a job because he couldn't work as any work supports capitalism. On the other hand such a guy would just be homeless, rid of any practical opportunity to create and do good, and would probably die soon anyway. Here it's more or less a question of personal tuning, finding the "least harmful" job, minimizing time spent at it so as to be able to do good in spare time, opposing your boss sometimes but not every single time, not really building a career so that you may quit at any moment etc. Until we have [basic income](ubi.md) or something, you are more or less [doomed](doom.md) to suffer dealing with this on your own sadly.
 
@@ -58,7 +58,7 @@ Firstly **do NOT follow mainstream tutorials on making website** -- these are ab
 - **Static site hosting** to store your site on, which will server the site to clients. You have several options here:
   - There exist free static site hosting services, e.g. those on many [git](git.md) hosting platforms like [GitLab](gitlab.md) or [Codeberg](codeberg.md) (even [GitHub](github.md), but avoid that one if possible), on [pubnix](pubnix.md) servers such as [tildetown](tildetown.md) or sites like [neocities](neocities.md). Here you may still encounter some censorship, but it can be a good start. Just search their site for details on how to host a site there.
   - You may host your site at home, typically using [Raspberry Pi](rpi.md). This doesn't really cost anything as the weaker Raspberrys (e.g. 3B) consume negligible amount of electricity, and for non-extreme traffic you won't even need a super high speed connection (especially considering you will make a very tiny, efficient website). This is a very good option as practically no one will be able to censor you (only police and ISP), but it's also a tiny bit more difficult to set up because firstly you need to set up a webserver ([Apache](apache.md) is usually installed on any GNU/Linux distro though, it's really easy to do) and secondly you NEED A PUBLIC [IP ADDRESS](ip_address.md) (as typically you will be behind a [NAT](nat.md) so that computers from outside can't reach your server): you will probably have to ask your [internet provider](isp.md) for it (maybe you already have it, maybe they will give it to you for free, maybe you'll have to pay some small fee; just ask). Then you will also need to set up port forwarding on your [router](router.md) so that the requests from the outside are redirected to your web server computer (Raspberry Pi) -- this is just done in router settings by entering the IP address of the webserver computer somewhere.
-  - You may also pay for a [VPS](vps.md) (i.e. a server computer a company runs for you and which you access remotely) which has the same advantages as having your own home server (i.e. being able to host game servers, dynamic websites, [gopher](gopher.md) sites etc.), but we won't cover this here. Renting a VPS in some obscure country may be a good option to host a very controversial site.
+  - You may also pay for a [VPS](vps.md) (i.e. a server computer a company runs for you and which you access remotely) which has the same advantages as having your own home server (i.e. being able to host game servers, dynamic websites, [gopher](gopher.md) sites etc.), but we won't cover this here. Renting a VPS in some obscure country may be a good option to host a very controversial site. Also VPS may be expensive compared to mere static site hosting. { NOTE: **Check out this cool host**, it looks pretty based: https://www.nearlyfreespeech.net/. They try to be as cheap as possible, you only pay for resources you use, so with a tiny site it may be almost free, and they don't censor content as a rule. Also their site is pretty suckless. An issue may perhaps be when someone DDOSes you and wastes your resources, draining your money pool. ~drummyfish }
 - Optionally buy a domain name (search web for domain registrars), for example *mycoolsite.party*. If you are using a free hosting service, you will get a subdomain for free and don't have to care about this (but can still also use your own domain if you have it and want to). If you have your own home server, you probably want to buy a domain because otherwise people would have to connect to your site by literally typing an IP address to the browser. Once you have the domain, you want to edit the [DNS](dns.md) records of your domain to point to the IP address of your server (i.e. you want to add an "A record"): how exactly to do this depends on the registrar (they will have some kinda online system to edit the records).
 
 For starters try to go the easiest way: use some free static site hosting without a domain name. Later, once you get comfortable, you may transition to self-hosting with your custom domain.