Just letting it slide. Deleted the A record and should be fine now.

Our platform is open source so we keep everything open. And what are your devs doing?

I had a good laugh.

I'm wondering if this site is for scamming people. Should I scam the scammer? Add more DNS records to point their way?

So, I checked their website. The landing page talks about decentralized revolution and network security. Yet, they couldn't implement a simple domain name check.

I pointed this out to him and the reply was EPIC.

Guy didn't know how to ask for help.

You guys pointing your ip to our server

Please tell your devs to fix this they have ruined our whole website structure

Mildly irritating.

Someone from blazenode.io messaged me today.

One of my domains' old DNS records point to an IP address (206.189.132.211) that's currently assigned to their active web server.

So, its messing up their traffic/analytics.

Recommended default values for the metrics

Search Time Breadth ef_search: The size of the dynamic candidates list during search (How many nodes are explored to find the nearest neighbours).

This metric affects the query time, not the indexing time.

Construction Time Search Width ef_construction: The number of candidates considered while inserting a node into the graph.

Higher ef_construction means better selection of neighbours resulting in higher at indexing time cost.

Maximum Connections m: The maximum number of bi-directional edges permitted for each node in the graph.

Higher m means denser graph and hence better recall accuracy. However, more memory usage and slower indexing.

Next, choosing a value for,

1. Maximum connections m
2. Construction Time Search Width ef_construction and
3. Search Time Breadth ef_search