Hive-Nectar v0.0.11: A Small But Necessary Patch

avatar
(Edited)

Hey everyone,

Short post today for a small but important update to hive-nectar. This one isn't a fancy new feature, but rather a necessary patch that came directly from community feedback.

A user who was migrating their projects from beem to hive-nectar pointed out that their scripts were failing to load a few posts. After digging into it, we realized that some older communities, particularly waivio, are still setting their community tag via the post's json_metadata instead of using the built-in community field that is standard now.

The Comment() function was causing a key error because the community field was not present, but the community tag was in the json_metadata of the post.

To ensure backward compatibility and support for these older communities, I've pushed an emergency patch. The function will now check for the community in the json_metadata if the primary community field is not present.

hive-nectar now sits at version v0.0.11 with this simple fix. It's not a spectacular change, but it was a needed one to ensure the library works as expected across the entire Hive ecosystem, old and new.

Version v0.0.11 is up and live!

You can get the latest version from GitHub or PyPI.

As always, a huge thank you to the community members who provide feedback and help find these edge cases!

Michael Garcia a.k.a. TheCrazyGM

dev nectar python archon tribes pimp proofofbrain
0
0
0.000
10 comments
avatar

Congratulations @thecrazygm! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)

You published more than 450 posts.
Your next target is to reach 500 posts.

You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word STOP

Check out our last posts:

Hive Power Up Day - August 1st 2025
0
0
0.000
Reply
avatar

I had no idea that there was a difference between older and newer communities. That's so curious and interesting. Can the older communities be updated in some way, or is it just a thing that can't be changed, and must be accepted as is? Congratulations on the fix, by the way! 😁 🙏 💚 ✨ 🤙

0
0
0.000
Reply
avatar

They could, they would just need to change the frontend. Right now they just append {"community": "old_community"} the json_metadata field of the post. Whereas the newer communities, e.g. all the ones with hive-XXXXXX in the name, set the community by using that community as the parent_author but leaving parent_permlink blank (or else it's a comment). Which to be honest doesn't seem as intuitive, but makes sense as the newer communities are accounts that have membership fields and roles etc.

0
0
0.000
Reply
avatar

Oh, OK, I'm glad that they can be updated. That's fascinating, and it helps me understand new aspects of Hive, so thank you for that explanation. 😁 🙏 💚 ✨ 🤙

0
0
0.000
Reply
avatar

Hello thecrazygm!

It's nice to let you know that your article won 🥈 place.
Your post is among the best articles voted 7 days ago by the @hive-lu | King Lucoin Curator by keithtaylor

You and your curator receive 0.0070 Lu (Lucoin) investment token and a 6.93% share of the reward from Daily Report 740. Additionally, you can also receive a unique LUSILVER token for taking 2nd place. All you need to do is reblog this report of the day with your winnings.

2.png

Invest in the Lu token (Lucoin) and get paid. With 50 Lu in your wallet, you also become the curator of the @hive-lu which follows your upvote.
Buy Lu on the Hive-Engine exchange | World of Lu created by @szejq

If you no longer want to receive notifications, reply to this comment with the word STOP or to resume write a word START

0
0
0.000
Reply