Should Hive Developers Maintain Backward Compatibility?

in dPoll2 months ago (edited)

Should Hive Developers Maintain Backward Compatibility?


Apparently, the Hive devs made changes, because some applications are broken (mine). My voting service doesn't work with Hive anymore. My script for transferring money neither. A such disruption already occurred with HF24.

Yet vote and transfer are not depreciated operations.

The Hive internal market doesn't work. Hiveblocks shows nothing.

A Hive proposal is too expensive, so I ask the question here:
Should Hive developers maintain backward compatibility in order to keep existing applications working?


  • Yes

  • No

Answer the question at dpoll.xyz.

Edit

Let's Encrypt root certificate expiration is the cause of the issue. Hive developers changed nothing this time.

Sort:  

Voted for

  • Yes

It is the constant API level changes that has kept Hive down. Suppose they break Splinterlands. Where would Hive be in terms of price be after that?

It would be a disaster. Spinterlands is driving Hive up.

Let's Encrypt root certificate expiration is the cause of the issue. Hive developers have changed nothing this time.

Voted for

  • Yes

Voted for

  • Yes

Voted for

  • Yes

Voted for

  • Yes

Voted for

  • Yes

Voted for

  • Yes

At least better communication will help a lot to make transitions smoother. This will become more important as the ecosystem grow with more DAPP developers.
!PIZZA

Hive services uptime ratio is very important.

Let's Encrypt root certificate expiration is the cause of the issue. Hive developers changed nothing this time.

Voted for

  • Yes

Voted for

  • Yes

Voted for

  • Yes

PIZZA!
PIZZA Holders sent $PIZZA tips in this post's comments:
@vimukthi(8/10) tipped @droida (x1)
Learn more at https://hive.pizza.

Voted for

  • Yes

Voted for

  • Yes
 2 months ago Reveal Comment
 2 months ago Reveal Comment