What's the status of TeleHash? #188
Comments
|
All of the main activity this past year has been here: https://github.com/telehash/telehash-c/graphs/contributors As various early deployments of v3 progressed in different use cases, one has become predominately powerful above all others as a core networking platform for IoT with Filament. The dust hasn't settled there yet either, hence why there isn't much activity on the main telehash.org/etc areas. There's been a regular stream of new learnings as the IoT use case expands, and I'm expecting a v4 draft with that focus yet this year, as well as the telehash-c codebase being the primary implementation as it's become even easier to bind it into other languages now that it's embedded friendly and standalone. If your projects are IoT related then you're on the right track and join the telehash slack team as well as take a look at telehash-c and file issues there if it's close to what you need :) |
|
@quartzjer Thank you for your thorough answer. Indeed, my use-case is IoT related, I want to connect some measurement devices to securely connect and share, regardless of their network location. Are there any examples available? I imagine something like building a minimalistic client-server or p2p application that sends some sample data etc. Ideally I'd like to use TeleHash from a higher-level language (Haskell), but binding to C API is perfectly fine. |
|
@quartzjer any update on this yet? wondering if there is already a way i can start testing telehash |
|
yes actually, it's my holiday project to get things all reset towards a v4 revamp of the protocol and c code, so stay tuned :) |
|
@quartzjer will any gui be available for v4? |
|
v4 will emerge just as a protocol update and C reference library that is focused on IoT/embedded use cases. |
|
Ok thats good too, i want to use telehash on chips and pocketchips for
affordable meshnets
…On Dec 26, 2016 11:27 AM, "Jeremie Miller" ***@***.***> wrote:
v4 will emerge just as a protocol update and C reference library that is
focused on IoT/embedded use cases.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#188 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AMFmFsaVxil8cqwfqP00HsK7C6UeG0IBks5rL-r7gaJpZM4J_mIR>
.
|
|
Hi @quartzjer, there hasn't been any updates for almost a year regarding the v4 spec and the new IoT focused C library. Is there any ETA? This project is very interesting, and I'm always wondering about its production readiness. |
|
It's definitely still the plan, unfortunately slow to make it happen but there's many forces wanting this to exist before the end of the year :) |
|
Great news! is there any draft or something so we can take an earlier look? or even a list of the proposed changes? |
|
Only informally, but the goal is to move the entire protocol to use the IETF JOSE standards. Handshakes will be a JWE wrapped by a JWS, and individual messages will be a JWE with a streaming cipher derived from the handshake. All of it will support using JSCN also such that everything remains IoT friendly. |
|
Is the slack channel still available? I can't access the auto invitation |
|
How do I join the slack channel? |
|
Sadly there's still no activity I guess :( |
I apologize that this is probably not the best place to ask questions. But the web page says
and neither channels seem to be appropriate/give any response.
Furthermore the website says
but there seems to be no activity on the GitHub page in the past year.
I'd be quite interested in the protocol, as it seems to solve some interesting use-cases for my projects, so it's a pity it seems to be losing interest of its developers.
Another question, are there some examples how to use the library, and/or API documentation? The specification is very thorough, but it's aimed at implementers, not actual users, and it's difficult to figure out how to correctly use the library.
The text was updated successfully, but these errors were encountered: