Added an article on why telegram sucks and a tutorial on creating eepsites

guides/eepsite.md

@@ -0,0 +1,88 @@
+# How to setup an Eepsite in most linux distros
+
+An eepsite is a website in I2P, there are 2 main I2P clients (Java I2P
+and i2pd). So i'll cover both programs here
+
+# nginx configuration
+
+Implying you use nginx, you should use a configuration like this:
+
+~~~
+server {
+	listen 127.0.0.1:8080;
+	root /home/eepsite/www_data;
+	# any of your custom configuration goes here
+}
+~~~
+Now, explaining the not-so-normal things on the configuration:
+
+* We listen to 127.0.0.1 because we want only that computer to access
+  that server (if it was just `listen 8080;` it will bind the port to
+  every available IP address. Allowing external access and we don't
+  want that.)
+* We listen to port 8080 so we can have less errors later. The i2p
+  client will pick the port 8080 in 127.0.0.1 and then use it as port
+  80 in the I2P address. As there's only one HTTP server in
+  port 8080. You don't have to do any of these weird `server_name`
+  hacks. So you should bind to another port each eepiste you want.
+  
+# i2pd configuration
+
+1. Create the ~/.i2pd/tunnels.conf file
+2. put these contents
+
+~~~
+[website]
+type = http
+host = 127.0.0.1
+port = 8080
+keys = website.dat
+enableuniquelocal = false
+~~~
+
+## Explanation
+
+* `type = http` so it forwards the given port to 80 automatically
+* `host = 127.0.0.1` the host to make the request (can be anything)
+* `port = 8080` where it will get the port (change this for further eepsites)
+* `keys = website.dat` the file which will hold the eepiste private
+  key
+* `enaleuniquelocal = false` gives the 127.0.0.1 IP address to each
+  visitor. (by default i2pd will give addresses like 127.32.23.12)
+
+Now start i2pd, you can get the b32 address of the site you just
+created with this command:
+
+`printf "%s.b32.i2p\n" $(head -c 391 website.dat|sha256sum|xxd -r -p | base32 |sed  s/=//g | tr A-Z a-z)`
+
+(Or you can go to http://127.0.0.1:7070/?page=i2p_tunnels)
+
+That's it!
+
+# Java I2P
+
+Java I2P is better in my opinion because it is faster and it's easier
+to create an eepiste then. By default Java ships with Jetty (A simple
+HTTP server that does it job very well). So you can just drop the
+files you want to serve in ~/.i2p/eepsite/docroot and they'll be
+served once you start the first thing in
+<http://127.0.0.1:7657/i2ptunnelmgr> (the one that points to
+127.0.0.1:7658, which is the jetty instance)
+
+Jetty does it work pretty well, but you can obviously use nginx (or
+any other HTTP server, obviously). To do this just scroll to the
+bottom in <http://127.0.0.1:7657/i2ptunnelmgr> and create an HTTP
+hidden service.
+
+Enter whatever you want in the name. And in the description. You can
+set a website hostname if you want (foobar.i2p) and edit the private
+key file if you want. 
+
+Just enter whatever you need in the target section:
+
+![The target section mentioned above](/i2p.png)
+
+Then click save. click start and it should give you the b32
+address. And if you gave it a host. a addresshelper.
+
+That's it!

harmful/index.md

@@ -2,6 +2,8 @@
 
 Here I complain about things that I think they suck
 
+Taking something here seriously, depends on you.
+
 ## For software
 
 Be aware that in the section about software I'm not saying "STOP USING

harmful/software/signal.md

@@ -80,7 +80,7 @@ automatically.
 
 # Signal desktop
 
-<img src="/1610908987.png" width=700/>
+![Plus it is made in electron](/signal_desktop)
 
 # Centralization
 
@@ -136,4 +136,4 @@ Did I mention it needs phone number to work?
 
 
 [^1]: Signal services died in 2021-01-15. How could have this have
-happened is it is P2P?
+happened is it is P2P?

harmful/software/telegram.md

@@ -0,0 +1,38 @@
+# Telegram sucks
+
+Telegram sucks, I don't know why people think it is more secure than
+other applications. Like [whatsapp](whatsapp) at least bothers on
+encrypthing the messages (we don't konw if it is backdoored or
+not. but  well at least it is)
+
+# The client
+
+In telegram, messages are not end-to-end encrypted so the russians who
+operate it can read them.
+
+>\>inb4 you can use secret chats in telegram which are encrypted.
+
+Yes. Those secrets chats are enabled by default and supported fnord in
+telegram-desktop.
+
+For some reason I don't understand, telegram-desktop depends in a
+wayland library (even though i'm using X) 
+
+Then, you can use `telegram-cli` which is the most confusing thing
+i've seen in a lot of time but it supports the secret chat thing
+
+# The server
+
+I don't know man. It is proprietary.
+
+# The data it asks for
+
+* Phone Number
+
+Like, why? XMPP (for example), minimally, asks for a JID and that's
+it. That's how other users will find you
+
+
+# Further readings
+
+[Signal sucks](signal)

index.md

@@ -10,17 +10,25 @@ license. Images might or might not be under that license.
 
 Any article in this website is WIP. And they will always be WIP.
 
-## Contributing to this website
+# Contributing to this website
 
-Go to the [Codeberg repository](https://codeberg.org/qorg11/kill9), fork
-it, change whatever, make a pull request, ill merge, and your change
-will appear here. If you don't want to use Git,
-[email](mailto:qorg\[@\)vxempire.xyz) me a diff and I'll patch the
-file. Atribution will be given if wanted.
+You can contribute to kill-9 either writting things or donating
 
-If you want to request an article, just submit an issue or email me.
+## Writing
 
-## RSS feed
+Clone the thing from the [git
+repo](https://git.qorg11.net/kill9.git). Make whatever changes and
+send them to me. If possible using `git-send-email(1)` but sending a
+.diff (made with `git-diff(1)`, obviously) is also acceptable.
+
+## Donating
+
+You can donate to kill-9 using
+[Bitcoin](bitcoin:bc1qghl6f27dpgktynpvkrxte2s3gm9pcv8vlwuzum) or
+[Monero](monero:47QTumjtqJabbo1s9pLDdXeJarLVLfs1AaEcbi1xrEiV852mqcbe5AHLNXTk7tH9MscxcxQDfJQnvH5LpxvfgwSJQZ3zbS6)
+
+
+# RSS feed
 
 Since we use a fucking wiki software and this is not a blog we don't have a RSS feed.