-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I'm a student who is starting to work with ahmia.fi search engine as a part of Google Summer of Code. :)
The proposal is online here https://ahmia.fi/gsoc/
In practise, I have now time and funding to develop my search engine. George is my primary mentor and Moritz the backup mentor.
Today, I will submit all the required documents (the tax forms etc.) to Google.
After that, I think I will speed up with code base in the GitHub :)
Cheers, Juha
Juha Nurmi juha.nurmi@ahmia.fi writes:
Hi,
I'm a student who is starting to work with ahmia.fi search engine as a part of Google Summer of Code. :)
The proposal is online here https://ahmia.fi/gsoc/
In practise, I have now time and funding to develop my search engine. George is my primary mentor and Moritz the backup mentor.
Today, I will submit all the required documents (the tax forms etc.) to Google.
After that, I think I will speed up with code base in the GitHub :)
Enjoy GSoC :)
BTW, looking again at your proposal, I see that you are going to do both popularity tracking and backlinks.
How are these two technologies going to interact with each other? That is, how will the indexer consider the output of those two features?
Also, with your newly acquired knowledge about backlinks, how long is it going to take your incorporate them in ahmia? Are you actually going to do it during the "Use an another crawler to search .onion pages from the public Internet" phase?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 22.04.2014 17:35, George Kadianakis wrote:
Enjoy GSoC :)
I will :)
BTW, looking again at your proposal, I see that you are going to do both popularity tracking and backlinks.
Yes, another crawler gathers backlinks from the public WWW and I will start gathering the URL clicks from the users.
How are these two technologies going to interact with each other? That is, how will the indexer consider the output of those two features?
Django front-end re-sorts the answers from YaCy back-end.
See https://ahmia.fi/static/gsoc/re_sort.jpg
I have this idea in mind: https://ahmia.fi/static/gsoc/sorter.py
The result is sorted according to YaCy result index, number of backlinks and clicks which are scaled.
Note the scaling: p_info.backlinks = 1 / (float(index) + 1) etc.
sum_function = 3.0*self.yacy + 2.0*self.backlinks + 1.0*self.clicks
where 3, 2 and 1 are test coefficients. I will optimize these and made a better model if necessary. However, clicks are easily spoofed and there have to be small coefficient for them.
Also, with your newly acquired knowledge about backlinks, how long is it going to take your incorporate them in ahmia? Are you actually going to do it during the "Use an another crawler to search .onion pages from the public Internet" phase?
We can test it when popularity tracking and backlinks crawler are working.
- -Juha
Juha Nurmi juha.nurmi@ahmia.fi writes:
On 22.04.2014 17:35, George Kadianakis wrote:
Enjoy GSoC :)
I will :)
BTW, looking again at your proposal, I see that you are going to do both popularity tracking and backlinks.
Yes, another crawler gathers backlinks from the public WWW and I will start gathering the URL clicks from the users.
How are these two technologies going to interact with each other? That is, how will the indexer consider the output of those two features?
Django front-end re-sorts the answers from YaCy back-end.
See https://ahmia.fi/static/gsoc/re_sort.jpg
I have this idea in mind: https://ahmia.fi/static/gsoc/sorter.py
The result is sorted according to YaCy result index, number of backlinks and clicks which are scaled.
Note the scaling: p_info.backlinks = 1 / (float(index) + 1) etc.
sum_function = 3.0*self.yacy + 2.0*self.backlinks + 1.0*self.clicks
where 3, 2 and 1 are test coefficients. I will optimize these and made a better model if necessary. However, clicks are easily spoofed and there have to be small coefficient for them.
That makes sense.
BTW, what is the 'yacy' score? Is it just the order that YaCy's indexer chose for each result? Or does YaCy actually expose a score for each result? How is the score derived? Or do you treat it as a blackbox and assume it's the most accurate of backlinks and popularity.
Thanks!
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 25.04.2014 17:27, George Kadianakis wrote:
Juha Nurmi juha.nurmi@ahmia.fi writes:
On 22.04.2014 17:35, George Kadianakis wrote:
Enjoy GSoC :)
I will :)
BTW, looking again at your proposal, I see that you are going to do both popularity tracking and backlinks.
Yes, another crawler gathers backlinks from the public WWW and I will start gathering the URL clicks from the users.
How are these two technologies going to interact with each other? That is, how will the indexer consider the output of those two features?
Django front-end re-sorts the answers from YaCy back-end.
See https://ahmia.fi/static/gsoc/re_sort.jpg
I have this idea in mind: https://ahmia.fi/static/gsoc/sorter.py
The result is sorted according to YaCy result index, number of backlinks and clicks which are scaled.
Note the scaling: p_info.backlinks = 1 / (float(index) + 1) etc.
sum_function = 3.0*self.yacy + 2.0*self.backlinks + 1.0*self.clicks
where 3, 2 and 1 are test coefficients. I will optimize these and made a better model if necessary. However, clicks are easily spoofed and there have to be small coefficient for them.
That makes sense.
BTW, what is the 'yacy' score? Is it just the order that YaCy's indexer chose for each result? Or does YaCy actually expose a score for each result? How is the score derived? Or do you treat it as a blackbox and assume it's the most accurate of backlinks and popularity.
I am using only the order information.
BTW, we (Mikko installed new servers) are migrating YaCy servers and took down the old one system. There should be a working crawler + fresh full text search results soon :)
- -Juha
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
Some updates. Ahmia have now fresh new YaCy back-end installed. Unfortunately, I messed up with Solr and eventually we might have to destroy and re-crawl everything again. At the moment, it at least works.
Then some good news. I created a milestone to github. There are all the main features and I try to develop them as fast as I can :)
https://github.com/juhanurmi/ahmia/issues?milestone=1&page=1&state=o...
Currently, I have worked some code to gather popularity stats and new domains from tor2web nodes and saving them to ahmia.fi. Furthermore, I have built a tool that checks backlinks from the public WWW! This data is useful for the popularity measurements.
I am already pushing code to github :)
Cheers, Juha