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

You are viewing a single comment's thread:

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
2 comments
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
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