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

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.  You can get the latest version from GitHub or PyPI. - **GitHub:** [https://github.com/TheCrazyGM/hive-nectar](https://github.com/TheCrazyGM/hive-nectar) - **PyPI:** `pip install hive-nectar --upgrade` 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