I’m working on a script for my local mesh community that uses the MeshView API to feed content into a Discord bot/script.
I need access to each node’s public key. I know the public key is pushed to MQTT and can be seen in NODEINFO_APP packets, but it is currently not stored in the MeshView database as part of the node, nor is it exposed via the API in node or packet information.
Including public keys in the API would be really useful, it would allow us to detect key changes or identify nodes that might be spoofing on the network, improving overall security and transparency. It would also let our Discord bot provide more detailed, node-level information and features to our users and community, enhancing engagement and awareness.
Would it be possible to include node public keys in a future release of the API?
Thanks for considering this!
Hi,
I’m working on a script for my local mesh community that uses the MeshView API to feed content into a Discord bot/script.
I need access to each node’s public key. I know the public key is pushed to MQTT and can be seen in NODEINFO_APP packets, but it is currently not stored in the MeshView database as part of the node, nor is it exposed via the API in node or packet information.
Including public keys in the API would be really useful, it would allow us to detect key changes or identify nodes that might be spoofing on the network, improving overall security and transparency. It would also let our Discord bot provide more detailed, node-level information and features to our users and community, enhancing engagement and awareness.
Would it be possible to include node public keys in a future release of the API?
Thanks for considering this!
<!-- github-sync-id:3856730843 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Hi,
I’m working on a script for my local mesh community that uses the MeshView API to feed content into a Discord bot/script.
I need access to each node’s public key. I know the public key is pushed to MQTT and can be seen in NODEINFO_APP packets, but it is currently not stored in the MeshView database as part of the node, nor is it exposed via the API in node or packet information.
Including public keys in the API would be really useful, it would allow us to detect key changes or identify nodes that might be spoofing on the network, improving overall security and transparency. It would also let our Discord bot provide more detailed, node-level information and features to our users and community, enhancing engagement and awareness.
Would it be possible to include node public keys in a future release of the API?
Thanks for considering this!
This will be added to version 3.0.5! is already on that branch, check it out.
awesome good to hear! thank you!