Yeah of course, At first, it was a learning project, also to get more familiar with Golang. I believe that for any information that is public anyway (e.g. Amboss), you should consider making it available on Nostr. Otherwise, you are always dependent on a central provider which can close its business. In addition, as soon as there is a relevant network effect, you can also expand the project. For example - Automatic push notifications when a peer announces maintenance. - Or the exchange of further information, e.g., about currently poorly maintained nodes in the network (with high latencies), which are then automatically excluded from pathfinding at other nodes. The fundamental problem is always how to trust the information on Nostr if you cannot verify that it has actually created a lightning node.
