Akash founder and io.net CTO in a confrontation

Orijinal yazar: TechFlow

One of the most noteworthy events in recent days is the launch of IO.NET tokens.

From the price changes at the Binance opening to the review of the experience of providing graphics cards to mine IO tokens…it seems that all attention is focused on the asset level of IO.

However, there are also people who disagree.

For example, Greg Osuri, the founder of Akash Network, another decentralized cloud computing project, was a bit restless. While his attention was focused on changes in IO prices, he went to experience the IO.NET product.

As a result, the experience was a bit unsatisfactory.

Greg then began to point out various product experience issues of IO.NET on Twitter, and he turned from the founder of another şirket into the quality inspector of IO.NET.

IO.NETs CTO Gaurav Tdhinait responded one after another, patiently explyapay zekaning each of Gregs questions.

The two sides had a back-and-forth discussion. On the surface, it was an objective question and answer session on product experience, but behind the scenes it was a competition between two similar business projects and the maintenance of brand image.

The founder of Akash tried out the products of rival companies and offered suggestions. At this juncture, it is difficult to say whether this was just just for fun or deliberately nitpicking.

We have compiled the entire conversation between Akash founder Greg and IO.NET CTO Gaurav Tdhinait to restore the event.

Buying an Apple product but getting a Nokia instead, are you feeling cheated?

The cause of the incident originated from an initial failure feedback from Greg, the founder of Akash, when using IO.NET.

Greg purchased a cluster of 4 A100 GPU graphics cards on IO.NET and paid the corresponding fees.

After deploying the cluster and paying the fees, Greg discovered that the goods were not what he ordered. After checking various data, he found that he did not get 4 A100 GPUs, but only one RTX a4000.

On paper, there was a huge performance gap between what he wanted and what he actually got. Greg said it was a bit like paying for an Apple phone but only getting an old Nokia phone.

To prove its authenticity, Greg not only asked @IO.NET on Twitter for an explanation, but also posted a video recording he had recorded that included all the purchase and operation steps.

This post quickly went viral, and even others tended to believe that this was a fraud and demanded an explanation from IO.NET.

This move quickly attracted a personal response from IO.NETs CTO Gaurav ( @GauravTdhinait ), who gave a relatively reasonable explanation.

The so-called wrong goods in Gregs video recording is actually because one of the servers (nodes) in the cluster he created is unhealthy, so the cluster cannot operate normally.

As for why the A 100 got the RTX a 4000, specifically, the RTX a 4000 that Greg showed is actually the master node of the cluster (the server responsible for management and coordination), rather than the working node (the server responsible for actual calculations) used to perform high-performance computing tasks.

And the problematic cluster IO.NET will not charge any money and will be automatically destroyed afterwards.

In simple terms, the video you record is not the same as what you actually see.

When you buy an Apple phone, you still get an Apple phone. It鈥檚 just because there is a problem with this Apple phone that the misunderstanding you think has occurred.

More importantly, CTO Gaurav also provided some other evidence: Greg actually created a total of 7 clusters on IO.NET, 6 of which ran successfully.

Greg only posted about this individual failure and asked for an explanation. Although IO.NET did not directly comment on this behavior, it is hard not to think that Greg might be picking on an individual case.

The 6 successful ones did not record or say anything, and the 1 failed one recorded the screen and asked for a reply. Some netizens in the comment area also said:

You dont look like youre really here to use the product properly…

Quality inspector

After questioning the product quality, Greg did not stop acting as a quality inspector for IO.NET. He continued to complain about other problems with the IO.NET product and kept harping on various experience issues.

For example, Greg said that he recharged 100 U to his IO.NET account, but did not get an upgrade to unlock the qualification to purchase more clusters. He questioned whether IO.NET was deliberately censoring him and restricting the permissions of his account.

For example, the CTO of IO.NET thought that Gregs behavior in using the product was abnormal. He quickly created a cluster service and deleted it immediately after 2 minutes. Greg refuted it very seriously, saying that he did not delete it immediately, but deleted it after a long time, because the IO.NET system could not display the GPU correctly, and it looked like the program was not responding, so he deleted it reasonably…

As of the time of writing this article, Greg is still constantly opening new posts on Twitter, even putting various issues together to complain, and telling everyone not to believe the one-sided words of IO.NET CTO, and by the way praising the smooth operation of his own Akash Network.

Whether IO.NET has any user experience problems or how many user experience problems there are seems unimportant in such online discussions and exposure posts.

Instead, the impression is that as the founder of another project, he spends a lot of energy to experience other peoples products, relentlessly pointing out various problems and seriously refutating every one-sided statement.

Is this their own CEO or someone else鈥檚 free quality inspector?

In this way, dwelling on details makes people feel that you are not being too serious, but rather lowering your level.

Gregs behavior also attracted criticism from the community. Some people bluntly said, Brother, you should spend time improving your own products instead of complaining about your competitors. Other AKT holders felt that Gregs vision was not good and made them want to sell their coins.

Peers look down on each other

In ancient Chinese, the phrase literati look down on each other often refers to the fact that literati look down on each other.

In fact, you can easily feel the pleasure and motivation of finding faults like Greg does – I am also engaged in the same business as you, and of course I cannot tolerate your small mistakes; I even often have the urge to say, If you cant even handle this, then I really want to say something to you.

Therefore, when the founder of Akash complained about IO.NET, it can be said that it was a kind of DePIN contempt.

Everyone has two skills, but everyone hopes that the other person only has one.

DePIN or decentralized cloud computing projects are emerging one after another. There are not many technical barriers, but more resource-intensive businesses. The level of experience, the degree of smoothness and the amount of brand resources are often the important chips for winning or losing.

However, if one personally acts as a quality inspector and is not absolutely sure that he can point out the problems, in the end it will only damage his own brand image.

After all, if you are too critical of your competitors and something unexpected happens with your own product, the community will bring up old issues.

Leaving room for yourself and others may be the prevailing philosophy in a world dominated by makeshift troupes.

This article is sourced from the internet: Akash founder and io.net CTO in a confrontation

Related: SignalPlus Volatility Column (20240611): Key 36 Hours

The United States will hold a new round of FOMC meetings on Thursday morning, and before that, there will be heavy CPI inflation data released on Wednesday night, which has made the global market sit on pins and needles. According to Jinshi, Federal Reserve mouthpiece Nick Timiraos said that most buy-side economists and other professional Fed observers now expect the Fed to cut interest rates once or twice in September or December. There are two risks at this stage. One is that the Fed will regard the sound economic activity as a signal that the policy is not tight enough and the high interest rate will not be maintained for long enough; the other risk is that the Feds attempt to preemptively strike may ignite the market. Source: SignalPlus, Economic…