fixed infinite scroll for ipfs

Author: amaynez

_posts/2021-03-24-starting-the-adventure.md

@@ -108,7 +108,7 @@ You can use the modified template yourself by [forking my repository](https://gi
 Since I decided on Jekyll to generate my site, the choice for hosting was quite obvious, **[Github Pages](https://pages.github.com)** is very nicely integrated with it, it is free, and it has no ads! Plus the domain name isn't too terrible ([the-mvm.github.io](https://the-mvm.github.io)).
 
 ##### Interplanetary File System
-To contribute to and test [IPFS](https://github.com/ipfs/ipfs#quick-summary) I also set up a [mirror](https://weathered-bread-8229.on.fleek.co/) in IPFS by using [fleek.co](https://fleek.co). I must confess that it was more troublesome than I imagined, it was definetively not plug and play because of the paths used to fetch resources. The nature of IPFS makes short absolute paths for website resources (like images, css and javascript files) innoperative; the easiest fix for this is to use relative paths, however the same relative path that works for the root directory (i.e. /index.html) does not work for links inside directories (i.e. /tags/), and since the site is static, while generating it, one must make the distintion between the different directory levels for the page to be rendered correctly.
+To contribute to and test [IPFS](https://github.com/ipfs/ipfs#quick-summary) I also set up a [mirror](https://weathered-bread-8229.on.fleek.co/) in IPFS by using [fleek.co](https://fleek.co). I must confess that it was more troublesome than I imagined, it was definetively not plug and play because of the paths used to fetch resources. The nature of IPFS makes short absolute paths for website resources (like images, css and javascript files) inoperative; the easiest fix for this is to use relative paths, however the same relative path that works for the root directory (i.e. /index.html) does not work for links inside directories (i.e. /tags/), and since the site is static, while generating it, one must make the distinction between the different directory levels for the page to be rendered correctly.
 
 At first I tried a simple (but brute force solution):
 ```jekyll
@@ -120,12 +120,12 @@ At first I tried a simple (but brute force solution):
 	{% assign relativebase = './' %}
 {% endif %}
 ...
-# Eliminate unnecesary double backslashes
+# Eliminate unecesary double backslashes
 {% capture post_url %}{{ relativebase }}{{ post.url }}{% endcapture %}
 {% assign post_url = post_url | replace: "//", "/" %}
 ```
 This `jekyll/liquid` code was executed in every page (or include) that needed to reference a resource hosted in the same server.
 
-But this fix did not work for the search function, because it relies on a `search.json` file (also generated programatically to be served as a static file), therefore when generating this file one either use the relative path for the `root` directory or for a nested directory, thus the search results will only link correctly the corresponding pages if the page where the user searched for something is in the corresponding scope.
+But this fix did not work for the search function, because it relies on a `search.json` file (also generated programmatically to be served as a static file), therefore when generating this file one either use the relative path for the `root` directory or for a nested directory, thus the search results will only link correctly the corresponding pages if the page where the user searched for something is in the corresponding scope.
 
 So the final solution was to make the whole site flat, meaning to live in a single directory. All pages and posts will live under the root directory, and by doing so, I can control how to address the relative paths for resources.

all-posts.json

@@ -4,7 +4,7 @@ layout: null
 {
   "posts" : [
     {% for post in site.posts %}
-    "{{ post.url }}"{% unless forloop.last %},{% endunless %}
+    ".{{ post.url }}"{% unless forloop.last %},{% endunless %}
     {% endfor %}
   ]
 }

posts-by-tag.json

@@ -8,7 +8,7 @@ layout: null
   "tag" : "{{ this_word }}",
   "posts" : [
       {% for post in site.tags[this_word] %}
-      "{{ post.url }}"{% unless forloop.last %},{% endunless %}
+      ".{{ post.url }}"{% unless forloop.last %},{% endunless %}
       {% endfor %}
     ]
   } {% unless forloop.rindex == 2 %},{% endunless %}