fixing errors, adding new team members

Makefile

@@ -1,5 +1,6 @@
-VOLUMES=--volume="${PWD}/cache/bundle:/usr/local/bundle"  --volume="${PWD}/cache/gem:/usr/gem" --volume="${PWD}:/srv/jekyll"
+VOLUMES=--volume="${PWD}/cache/bundle:/usr/local/bundle:Z"  --volume="${PWD}/cache/gem:/usr/gem:Z" --volume="${PWD}:/srv/jekyll:z"
+
 
 watch :
 	-[ ! -e "${PWD}/cache" ] && docker run ${VOLUMES} jekyll/jekyll jekyll build 
-	docker run -p 4000:4000 ${VOLUMES} jekyll/jekyll jekyll serve
+	docker run -p 4000:4000 ${VOLUMES} jekyll/jekyll:3.8.6 jekyll serve

_config.yml

@@ -31,7 +31,7 @@ url: "https://graphsense.github.io" # the base hostname & protocol for your site
 
 repository: "graphsense/graphsense.github.io"
 repo: "https://github.com/graphsense"
-discord: "https://discord.gg/udweqn3aSd"
+# discord: "https://discord.gg/udweqn3aSd"
 
 # Build settings
 plugins:

_includes/navbar.html

@@ -18,7 +18,7 @@
           {%- endif -%}
         {% endfor -%}
         {% include navitem.html title="On Github" url=site.repo icon="fab fa-github" %}
-        {% include navitem.html title="On Discord" url=site.discord icon="fab fa-discord" %}
+        <!-- {% include navitem.html title="On Discord" url=site.discord icon="fab fa-discord" %} -->
       </ul>
     </div>
   </div>

documentation.md

@@ -45,17 +45,17 @@ Because we use GraphSense for advanced (research) analysis tasks and move a lot
 
 **Q: How can I get access to the GraphSense demo?**
 
-Just drop an email to [contact@iknaio.com](mailto:contact@iknaio.com) and briefly explain **who** you are and **why** you want access to our demo. You will receive access credentials, and we will also sign you up for our public GraphSense users mailing list.
+Just drop an email to [contact@ikna.io](mailto:contact@ikna.io) and briefly explain **who** you are and **why** you want access to our demo. You will receive access credentials, and we will also sign you up for our public GraphSense users mailing list.
 
 <h4>Operation</h4>
 
 **Q: How often is the data updated?**
 
-That depends on how often you parse and ingest relevant raw data (blockchains, exchange rates, etc.) and subsequently run the transformation procedure (see [GraphSense Setup](https://github.com/graphsense/graphsense-setup)). We currently trigger this manually for demo purposes, but it could be automated using a cron job.
+That depends on how often you parse and ingest relevant raw data (blockchains, exchange rates, etc.) and subsequently run the transformation procedure. The [GraphSense Lib](https://github.com/graphsense/graphsense-lib) repository allows to do contentious updates without running the full transformation (see delta-updates). We currently trigger this manually for demo purposes, but it could be automated using a cron job.
 
 **Q: Does GraphSense support real-time updates?**
 
-Not yet, mainly because we never needed it in our investigations. However, this feature is on our future feature lists.
+Using the ingest and delta-update features of [GraphSense Lib](https://github.com/graphsense/graphsense-lib) a near real-time system can be built.
 
 **Q: How are entity and abuse types assigned to addresses?**
 
@@ -81,7 +81,7 @@ GraphSense development is very much driven by the needs of our project partners
 
 **Q: I need a specific new feature, can you provide it?**
 
-First of all, let us know what you need, ideally by filing a *feature request* issue in the relevant repository, probably the [GraphSense Dashboard](https://github.com/graphsense/graphsense-dashboard) or the [GraphSense API](https://github.com/graphsense/graphsense-openapi). Alternatively, you can write an email to [contact@iknaio.com](mailto:contact@iknaio.com).
+First of all, let us know what you need, ideally by filing a *feature request* issue in the relevant repository, probably the [GraphSense Dashboard](https://github.com/graphsense/graphsense-dashboard) or the [GraphSense API](https://github.com/graphsense/graphsense-openapi). Alternatively, you can write an email to [contact@ikna.io](mailto:contact@ikna.io).
 
 Whether we can implement a feature request depends on whether it fits into our plan or not. That, in turn, depends on the research funding model we are currently working on.
 

index.md

@@ -99,7 +99,8 @@ title: Home
     <li>Rainer Stütz, <a href="https://www.csh.ac.at/" target="_blank">Complexity Science Hub Vienna</a></li>
     <li>Matthias Rella, <a href="https://www.ikna.io/" target="_blank">Iknaio Cryptoasset Analytics GmbH</a></li>
     <li>Michael Fröwis, <a href="https://www.ikna.io/" target="_blank">Iknaio Cryptoasset Analytics GmbH</a></li>
-    <li>Artemiy Malyshau, <a href="https://www.ikna.io/" target="_blank">Iknaio Cryptoasset Analytics GmbH</a></li>
+    <li>Thomas Niedermayer, <a href="https://www.ikna.io/" target="_blank">Iknaio Cryptoasset Analytics GmbH</a></li>
     <li>Melitta Dragaschnig, <a href="https://www.ait.ac.at/" target="_blank">AIT - Austrian Insitute of Technology GmbH</a></li>
+    <li>Michael Seidl, <a href="https://www.ait.ac.at/" target="_blank">AIT - Austrian Insitute of Technology GmbH</a></li>
   </ul>
 </div>

news.md

@@ -116,7 +116,7 @@ This release provides
 
 * a central repository ([graphsense-setup](https://github.com/graphsense/graphsense-setup)) for installing all required components using Docker Compose
 
-As a response to the increasing number of requests for our semi-public demo, we also changed the access model. Before it was simple HTTP authentication, which was shared among all users. Now everyone who wants to work with the demo or use the API needs an API key, which can be requested per email (<a href="mailto:contact@iknaio.com">contact@iknaio.com</a>).
+As a response to the increasing number of requests for our semi-public demo, we also changed the access model. Before it was simple HTTP authentication, which was shared among all users. Now everyone who wants to work with the demo or use the API needs an API key, which can be requested per email (<a href="mailto:contact@ikna.io">contact@ikna.io</a>).
 
 
 <h2>