Re: [tor-dev] atlas.torproject.org question

[Karsten Loesing <karsten@xxxxxxxxxxxxxx>]

On 7/6/13 1:36 PM, me@xxxxxxx wrote:
> Am 2013-07-06 06:33, schrieb Sebastian G. <bastik.tor>:
>> 06.07.2013 12:05, Karsten Loesing:
>>> On 7/6/13 9:01 AM, Lunar wrote:
>>>> Karsten Loesing:
>>>>> On 7/3/13 5:16 PM, me@xxxxxxx wrote:
>>>>>> I updated it to display bridge detail and enable bridge search. Works
>>>>>> fine so far.
>>>>>> You can now toggle between relays or bridges in the search results.
>>>>>
>>>>> This is awesome!  Repeating the link here, so that others can follow:
>>>>>
>>>>> http://makepanic.github.io/emberjs-tor-onionoo/#/
>>>>
>>>> Small issues I spoted while playing with it:
>>>>
>>>>  * If a search, then select 'Bridges' view, visit a bridge page, and
>>>>    then use the back button of my browser it switches back to the
>>>>    'Relays' view. Not ideal.
>>>>
>>>>  * IMHO, the y-axis of the bandwidth graphs should always start at 0
>>>>    so multiple relays can be compared by layout graphs side by side.
>>>
>>> Can you add these to GitHub's issue tracker?
>>>
>>> https://github.com/makepanic/emberjs-tor-onionoo/issues
>>
>> @Lunar
>> If you don't have access to Github, I'll can add them as well.
>>
> 
> Added them both and fixed the bug where it defaults the search to
> 'relays'. The last version should also hash all the 40char hex strings
> for search requests.

Neat!

>>>> How close is this piece of code to have feature parity with Atlas?
>>>
>>> I think there are no features in Atlas that this new tool doesn't have.
>>>  To the contrary, this tool has features that we wanted to have in Atlas
>>> for a long time (list 10 fastest relays on start page, show bridge
>>> details).
>>
>> @makepanic
>> Could you please add this features to Atlas?
>>
> 
> Ok. Is there anything i need to contribute to the project?

Clone the repo, make changes, push your branch somewhere, and create a
Trac ticket or comment on an existing ticket that you want someone to
review your changes.  Arturo or I will then review your branch, merge
them, and deploy them on atlas.torproject.org.

Best,
Karsten


>>> However, I don't have plans to retire Atlas just yet.  I think it's fine
>>> to have more than one website providing access to Onionoo data.  Yay,
>>> diversity.
>>>
>>
>> @Karsten
>> Hooray, diversity. Yes, please don't retire Atlas.
>>
>> Best,
>> bastik
>>
>> _______________________________________________
>> tor-dev mailing list
>> tor-dev@xxxxxxxxxxxxxxxxxxxx
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> _______________________________________________
> tor-dev mailing list
> tor-dev@xxxxxxxxxxxxxxxxxxxx
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> 

_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev