A place for developers to talk about building on Farcaster.

/dev

Farcaster

code @ spindl.xyz. Interested in technology, history, and music // farcaster.network

Yeah, this. The hubs log the public ip of every peer they know about. It's possible to geolocate the IPs and build a map. But I haven't tried it personally.

Opportunity for a side project:

- Take all Hub IPs
- Plot on map

grep for "New Peer ContactInfo" in the logs. Happy to answer any questions.

do you think it would be worth it to add a rest/grpc endpoint to hubs that return a list of all connected peers?

Due to the libp2p config, this will be a small subset of all peers that are on the mesh. So for this particular use case, logs are better. But I've wanted the connected peers myself for other reasons. Will add it when I get a chance.

oh yeah that's right. so there's no function directly inside libp2p to get all peers on the mesh?

I don't think so? We manually remove entries from the peerStore when we hangup. I'd have to investigate. It's not hard to add this if we wanted it, but don't think it's worth it just for this usecase.