--- /dev/null
+# Domains man in the middle
+
+>qorg: Why is the ICANN a thing?
+>dvtate: Because there is bureaucracy for everything
+
+Those guys can create and destroy any domain they want, they say that
+we have to pay for internet domains, they are a fucking MITM.
--- /dev/null
+# markdown sucks!
+
+(which is ironic since im writing this in markdown)
+
+The markdown syntax sucks and it's unreadable, for example:
+
+The \*quick\* \*\*brown\*\* fox jumps over the \*\*lazy\*\* dog
+
+Translates to:
+
+The *quick* **brown** fox jumps over the **lazy** dog
+
+It's pretty unreadable to put both bolds and itallics with * because
+it leads to confussion. because a normal person reads \*text between
+asterisks\* as bold. not as /cursive/
+
+In saner alternatives (org-mode for example) \*something\* goes to
+**something** and /something/ goes to *something*
+
+Not to mention that when markdown lacks something (because it's not
+bloated!) you have to fallback to HTML.
+
+## Alternatives
+
+* org-mode
+* Jumping in the eye of a hurricane
+>I hosted a matrix server and explored Riot. You can tell they've
+>invested a lot into the UI. There's some 'dark pattern design' going
+>on too, like their "data collection dialog." They want you to
+>consent. Encryption isn't on by default, and when you do turn it on
+>the program prompts you to 'backup' your keys where "we'll store an
+>encrypted copy of your keys on our server." There is so much push to
+>harvet data from you in some way or another. For an apparently "open
+>source," "private," and "federated" program there seems to be an
+>insidious push to be the polar opposite. The project wants to
+>eventually move away from matrix usernames to phone numbers or e-mail
+>addresses to identify users.
+
+--- [lainon](https://lainchan.org/sec/res/10513.html#q10557)
+
# Matrix, Riot, Element, Synapse, Vector... I don't know how it is called anymore
Hey that's first problem! nobody knows how to find your service!
~~~
countries:
- - ES
- - DE
- - FR
- - GB
- - US
- - NO <- This isn't Norway, This is false
+ - ES
+ - DE
+ - FR
+ - GB
+ - US
+ - NO <- This isn't Norway, This is false
~~~
If you use YAML instead of literally anything else, is because you
~~~
countries:
- - ES
- - DE
- - FR
- - GB
- - US
- - "NO" <- Alright, not false anymore.
+ - ES
+ - DE
+ - FR
+ - GB
+ - US
+ - "NO" <- Alright, not false anymore.
~~~
+YAML can understand both tabs and spaces as indentation methods. It depends
+on the implementation if they are supported and many don't support it. So
+you're usually stuck working with spaces in YAML files instead of tabs.
+
+~~~
+editors:
+ - vi
+ - emacs
+ - ed
+
+functions:
+ - read <- Here's where the parsers will get confused
+ - write
+~~~
+
+If you thought indentation is a problem, you will have a bigger problem
+with complex structures. Here's array colors that contains two elements.
+
+~~~
+colors:
+ -
+ red: valid
+ hex: "FF000000"
+ - cow:
+ hex: none
+~~~
+
+This roughly translates to:
+
+~~~
+colors = {
+ { red: "valid", hex: "FF000000"},
+ cow = { hex: "none" }
+}
+~~~
+
+YAML also decided to be special and add includes. How they work depends on
+the implementation. Here's a good example on how to abuse it:
+
+~~~
+users:
+ - name: Chris
+ repositories: &chrisrepos
+ - emacsconf
+ - dotfiles
+ - name: Marie
+ repositories: *chrisrepos
+ - emacsconf-improved
+ - name: John
+ repositories: *chrisrepos
+~~~
+
+One would guess that John has access to Chris' repositories and Marie
+too with the added -improved repository but this is invalid. You need to
+use <<: \*chrisrepos on the next line to append/override values. Wasted
+reserved keynames for things that already exist.
+
+YAML doesn't require you to quote your strings which should result in
+simpler writing for humans. But here's some weird cases where this results
+in parsing problems. Try to guess how many of these are strings and how
+many are integers.
+
+~~~
+value1: 42423
+value2: +0x_324_bad
+value3: -9_90_99_0:39:1
+value4: -0_
+value5: 0_0_0_0_0
+~~~
+
+If you guessed all, you are right. YAML allows all kinds of things in
+integers to make it more readable to humans and to make implementations
+more complicated.
I am **NOT** going to dig into terms of service. Only privacy.
+## What to check in a XMPP server?
+
+Well, first thing you should check is for *how long* they keep IP
+addresses. (Or if they don't collect IP addresses, like some services
+do). You shold also check if they provide a **v3** onion address (so
+you can connect anonymously to it). And you should check **what kind
+of data** they ask for in the registration.
+
Trashserver.net
===============
Wait what? You're telling me that Riseup accepts non-trusted
connections? WHAT? ABORT EVERYTHING. NEVER USE THIS
+Disroot
+=======
+
+[privacy policy](https://disroot.org/es/privacy_policy)
+
+They require a email address for signing up (altough they provide
+e-mail services). But i'm only caring for XMPP in this article,
+in XMPP they collect:
+
+* **IP address** (deleted after 24 hours)
+
+Apparently that's it. But they log IP addresses and they require Email
+address for signing, and i didn't see any .onion hostname for their XMPP server, so mid tier
+
jabber.lqdn.fr
==============
projects / kill9.git / commitdiff