Revert "Remove review comments from the code."

This reverts commit 472ae11.

Author: Mariha Kozinska

README.md

@@ -2,9 +2,12 @@
 
 In a series of articles we document how we build a distributed hospitality exchange over [Solid](https://solidproject.org).
 
+[comment]: <> (Who are we? Would be nice to write that it was you together with OHN project/team or you as part of it)
+
 [Start here](intro.md)...
 
 ---
+[comment]: <> (I enjoyed the mystery of unknowing "what happened next" but I believe many people may prefer to know what to expect before starting to read, so you may consider to add an overview here)
 ... or jump over directly to one of the chapters:
 
 1. [Developing a distributed app with Solid](intro.md) \

group-community.md

@@ -59,6 +59,14 @@ Improvement #2.1: Make the group members searchable by location, creating a geo
   - a group could be replicated, and an index could be distributed over a few nodes, with some redundancy.
 - If we don't make _Improvement #2.1_, we have to fetch all members' offers in order to find hosts in the area we travel to
 
+
+[comment]: <> (### 3. Make a distributed way to discover each other &#40;Distributed Hash Tables&#41;)
+
+[comment]: <> (I don't think it would work actually. 
+It is possible to have an index distributed over a few nodes, that could be queried by location. 
+It is also possible to have a key-value store distributed over a few nodes, implemented as a distributed hash table, it would be queried by keys, not sure what they might be.
+I suggest removing this point alltogether. )
+
 ### (both solutions can coexist next to each other)
 
 ---
@@ -136,6 +144,10 @@ Basically, at this point, the options are two:
 1. Everybody in the internet can see the list of hospitality exchange members
 2. Group is private, but the people's hospex data are public. ([this doesn't work if the group is hosted on CSS](https://github.com/CommunitySolidServer/CommunitySolidServer/issues/1442))
 
+[comment]: <> (What if we had a functional webId for each hospex community, and we created a public Solid Group that included them and authorized only members of this group to see people's hospex data? Each community would have a separate app/webpage, with their own webId. Only app would be authorized to access hospex data of members of the community it serves. The members directly or other apps/communities would not be authorized to read that data.
+Trust between communities could be established by granting or revoking access to resources of one community for the webId corresponding to the other community
+Only the apps could write to hospex.ttl files and they could enforce and validate expected file format for the offers that belong to them, a format that would be specific to them and they would have freedom to change and maintain it)
+
 We chose the second option to start. But it's a difficult choice, two suboptimal options...
 
 ### Finally, making it

intro.md

@@ -26,6 +26,9 @@ I think [Solid](https://solidproject.org/) is an interesting idea. But it suffer
 
 I don't care for the inception ideas. I don't care for authority in Solid. I don't care for your new Specification. I want it to work.
 
+[comment]: <> (I don't care for your new Specification)
+[comment]: <> (it's unclear to me who is "your" here. Maybe adding a link under "Specialization" will help, or changing "your" to somthing more specific?)
+
 For me, Solid is:
 
 1. an identity provider
@@ -35,6 +38,11 @@ As I said, i want to develop great real-social applications. Applications that c
 
 One well explored, and popular use case is Hospitality Exchange. It's pretty clear what the system should do.
 
+[comment]: <> (would be great if you mentioned somewhere here, here-here or elswhere on this page, how your collaboration with me or/and OHN started, what OHN is about and how it fits together with Your agenda. Maybe also a few words about sleepy.bike, who is it for and where it comes from? I'll be happy to discuss or draft parts of this if it was helpful.)
+
+[comment]: <> (I would describe OHN as an effort to design and build next generation hospitality exchange platform. One that would be federated (decentralized and interconnected\) in order to address issues and the long-term consequances many hospex communities have faced over the years of existance and which we believe are related to centralized infrastructure they've been built on.
+Or something along these lines.)
+
 So, let's focus on Hospitality Exchange for now.
 
 ## What is it supposed to do?
@@ -46,7 +54,12 @@ In the simplest case:
 0. Sign in
 0. Write a little bit about yourself
 0. See a map of people who would like to host fellow travellers
+
+[comment]: <> (I like also a phrasing "people who invite fellow travellers to stay at theirs home/place". For me "people who offer to host sb" seems somehow very transactional, like the verb "to offer" implided that ones gets something in return. And I know usually they do, but I feel like it's better not to expect that.
+Maybe it's that the word "offer" has sales connection to me, where things are exchanged for money in a trasactional way)
 0. Open a profile of, and read about a few potential hosts, what they write about themselves and what other travellers wrote about staying with them, ..., get impression that you'll have good time together and maybe that you'd be reasonably safe with them
+
+[comment]: <> (personally I don't consider safety as something to think actively about, I follow my intuition and unless something awakens my inner sense of danger-detection I just go for it. My default is to trust people I'd say. I am writing it because I wouldn't mention safety-verification here, but I don't know how others have. Just to consider removing it.)
 0. Contact the potential hosts
 0. Wait for their reply
 0. When they reply, get a notification
@@ -68,6 +81,9 @@ Now, you have a home, you want to host travellers in your home:
 0. Enjoy the new real world connection, enjoy their stay
 0. After their stay, write a reference for them, and establish a friendship connection
 
+[comment]: <> (just as a side note: referrences are not a mandotory component, in WarmShowers they were hardly used, other platform may have different trust systems for example based on existing connections or profiles in other social networks. 
+In Trustroots 'references' are called 'experiences' which I also personally prefer as 'references' seem to me a bit formal and like it was Linked-in or similar network. I belive the phrase 'references' comes from CouchSurfing but I never used it so idk)
+
 ---
 
 In a more complex feature:

next-steps.md

@@ -5,6 +5,9 @@
 - send messages to other members
 - post travel plans...
   - ...and members of various communities (even those you can't see) from the area will be notified, and can invite you
+
+[comment]: <> (the above seems hard... I'd limit it to others from your communities only?)
+
 - connect to others
   - _create connectios_ with people you know `:me foaf:knows myFriend` (or a special hospex connection)
   - _write a reference_, to tell others about your experience with a particular member (social proof of safety)