Search on onename.com not finding my ID

Apps Identity
#1

I registered my ID and I wanted to check if it had been registered.

If I put in http://www.onename.com/eroche I am there but there is a search box on the top left which doesnt seem to find my name. I also tried searching for timblee and I cant find it either but I do see it if I put in http://www.onename.com/timblee.

Is it possible there is an issue with search indexing on the site. larry posted this in the slack forum in response to my question

(blockstack-venv)Vanquish:~ larry$ blockstack lookup eroche.id
{
“profile”: {
"@type": “Person”,
“account”: [
{
"@type": “Account”,
“identifier”: “ed_roche”,
“proofType”: “http”,
“proofUrl”: “https://twitter.com/ed_roche/status/778674385569902593”,
“service”: “twitter”
},
{
"@type": “Account”,
“identifier”: “53c349c47bb004df637f91f7b01af3a7886c72a2”,
“proofType”: “http”,
“proofUrl”: “https://twitter.com/andrew23baldwin/status/778955481175957504”,
“service”: “openbazaar”
}
],
“address”: {
"@type": “PostalAddress”,
“addressLocality”: “Ireland”
},
“description”: “Exploring the Blockchain one block at a time. I write about Crypto, Technology and Travel on Steemit.”,
“image”: [
{
"@type": “ImageObject”,
“contentUrl”: “https://s3.amazonaws.com/97p/rv1.jpeg”,
“name”: “cover”
},
{
"@type": “ImageObject”,
“contentUrl”: “https://s3.amazonaws.com/kd4/eroche”,
“name”: “avatar”
}
],
“name”: “Edward Roche”,
“website”: [
{
"@type": “WebSite”,
“url”: “https://steemit.com/@eroche”
}
]
},
“zonefile”: "$ORIGIN eroche.id\n$TTL 3600\n_http._tcp IN URI 10 1 "https://blockstack.s3.amazonaws.com/eroche.id"\n"
}
(blockstack-venv)Vanquish:~ larry$

#2

It doesn’t work with the onename api either: https://api.onename.com/v1/search?query=eroche

Screen Shot 2017-01-21 at 1.29.30 AM.png1126×294 46 KB

It looks like a problem with onename’s search index.

Your name show up fine in the explorer: https://explorer.blockstack.org/name/eroche.id

#3

Thanks for reporting! Looking into it and will report back here.

1 Like
#4

I can confirm that one the earlier index refresh got stuck and the data is a bit stale. I could fix this on the current server (it’s faster) but we’re moving our servers to a different account/provider for cost reasons. So I’m switching the server (booting/deploying a new one). It’d take a bit longer but is a better fix. I’ll update on progress over the weekend.

1 Like
#5

I looked more into and debugged the issue. Reporting my finding.

The main issue is that the search service is fetching data correctly from the (now old) DHT deployment but it’s not setup properly with the new Atlas network. Re-implementing and/or fixing the current code is redundant work because search (which was a separate daemon and repository earlier) has been merged with Blockstack Core.

Blockstack Core already has a mechanism for syncing with the Atlas network and fetching zonefile data locally. So with this merge, the search service can get this data locally (it’s already on disk). I plan to work on it this week.

In summary, my debugging pointed to issues that are better solved in the new release of Blockstack Core that includes search. I’ll keep the old search service up and push some manual fixes to get more recent profiles indexed in search. I plan to work on finishing the patch on the new release soon and then we’ll replace out the old search service. This forum post and Github issues are a good place to follow progress.

2 Likes
#6

We’re doing a planned upgrade of search. You can follow progress here

When this goes live, we’ll switch from the old search deployment (search.onename.com) to a new deployment (search.blockstack.org) and will also give users easy to install instructions if they want to deploy your own search server.

#7

Great Thanks Ill test it out when the upgrade has gone through.

1 Like