I don't know off the top of my head, that algorithm was written a long time ago, before I was involved with the development of the hivemind codebase, so somebody would need to dive into the hivemind code

We'll be migrating hivemind itself to the HAF architecture, so yes, API nodes in the future will consist of a hived node plus one or more HAF apps. And we will likely see the emergence of API nodes that

Where's the HAF database stored? You can store it wherever you want, you just point your HAF code at the postgres database server of your choice.

Yes, that's correct, that is one of the key "ease-of-use" benefits that HAF offers to programmers.

A HAF server is very similar to an existing API node in the way it works, and in terms of it's trustworthiness. In other words, if you are using someone else's HAF server, then you're trusting it's data,

Can you remind me what HAF stands for? Hive Application Framework Are you still looking at or working on a change/new user reputation system? Yes, I'm hoping to get started on a completely new type of

testing speed to comment

The operation is also available in Hive's command-line interface (CLI) wallet.

I don't understand your question, could you add some detail?

Maybe @quochuy can investigate this on hive.blog?

I'm hopeful it will be ready before the end of the month.

Also, @howo has previously expressed plans to continue work on communities, as I recall from discussions with you and others in mattermost and gitlab.

In my opinion, it would be a mistake to start this work before we complete HAF work. The next step in hivemind's evolution is to port it to HAF. After that, it should be no big deal for someone to enhance

Show was just slightly shorter than I remembered :-) Nice editing job, barely noticeable.

Information communication has always been the fundamental building block of human civilization. Computers and networking technology have already radically changed how we communicate and process information,

That is people buying Hive from our cryptocurrency exchange site:

Actually, that name is appropriate, because that route on jussi is for older, slower pre-appbase traffic that jussi has to translate from the old format before a hived node can process it.

Some interesting ideas there, but I haven't given it much thought yet. First thing I need to do is review current implementation in depth; I haven't looked at the resource credit code much.

It might have, but I always recommend checking such things :-)

hive-js was updated a couple of days ago. So you just need to make sure you are using the very latest version.