Skip to main content



Difficulties in creating APIs for third parties

We have been thinking about creating APIs so that people can easily create and integrate their applications with HexHoot. We were also thinking about hosting a page where we link to these applications as well. In our brainstorming sessions, we have been encountering a serious concern. Any design that we have so far been able to come up with have a vulnerability that an application could simply access the user information from the IndexedDB, and could potentially send it across to unauthorised party. Image generated by OpenAI's DALL-E 2. Currently, we are thinking in three different directions to come up with something that could eliminate this vulnerability: We should come up with a design wherein apps can not access such information. This may have been an easier task if we did not want to keep HexHoot's codebase opensource. We could think of different techniques with which we could achieve this, if at least a part of the codebase was closed. We could require the developers to

Latest Posts

The ability to communicate without the Internet is important

Released HexHoot v1.0.3; Featuring Intranet Communication!

Key exchange and Zero-Knowledge-Proof

How a couple of courses in Physics lead to the creation of HexHoot

Explaining Zero-Knowledge-Proof strategies in an abstract manner through a hypothetical story

Why HexHoot?