Hi,
> Arisbe:>> I looked up my relays and bridges on Atlas using their nickname,
> IP>>
address or fingerprint. I bookmarked these look-ups so that I could>>
easily access the Atlas data for my nodes going forward.
No URLs have changed (planning to change them in the near future but
nothing
Hi,
On 16/11/17 02:36, teor wrote:
> No, I can't, because iOS ad blockers do not provide this information.
> Did you add many resources in the transition?
Short of buying me an iPad I have no idea how to debug this.
The following resources are loaded by Relay Search, and the new ones are
those
Hi,
On 15/11/17 07:13, Arisbe wrote:
> I use to review my bridges as well as my relays on Atlas. Now I don't
> find my bridges on nyx. Is this something I'm doing wrong?
Atlas and Nyx are different things. I've updated the subject and
hopefully someone familiar with Nyx can chime in.
Thanks,
Hi,
On 14/11/17 21:49, I wrote:
> Can anyone explain how changing things to The New such as Arm to Nyx
> and Atlas to Relay Search advances anything apart from boredom?
In the case of Atlas/Relay Search, we are consolidating codebases into
something more maintainable, with less code duplication
Hi,
On 14/11/17 18:26, teor wrote:
> No, it isn't: one of the new resources appears to be blocked by AdBlock
> Plus for iOS. So it only works with content blockers turned off. You probably
> want to fix this eventually, because these blocklists are popular. And the
> issue likely affects multiple
Hi,
On 14/11/17 20:33, tor wrote:
> A 200px purple banner with a Schneier quote at the top of every page?
> Seriously? What a hideous waste of space. Can anyone explain how this UI
> element is helpful to users? It's awful.
This is the Tor Metrics style used in preparation for merging into the
Hi,
On 14/11/17 17:03, Ralph Seichter wrote:
> I see no more graphs outside their boxes in Chrome, Firefox and Safari.
Yay! (:
> One thing that -- for me -- only works in Chrome and Firefox, but not
> Safari, is the timestamp info shown when moving the mouse pointer over
> the little circle
Hi,
> On 14/11/17 16:16, Ralph Seichter wrote:
>> https://imgur.com/a/VMJhE -- I see these "graph outside the container
>> box" issues in Chrome, Firefox and Safari. I sure hope it does not just
>> happen to me?
Graphs should now be scaling properly, although I'm not sure what I've
done will
Hi,
On 14/11/17 16:28, Guinness wrote:
> Is it just me or is the font way bigger than it used to be with Atlas?
> I personnaly find it too big, but it is just some cosmetics :)
The style has been merged from the Tor Metrics website. For the most
part this is fixed as all the style decisions have
Hi,
On 14/11/17 16:16, Ralph Seichter wrote:
> https://imgur.com/a/VMJhE -- I see these "graph outside the container
> box" issues in Chrome, Firefox and Safari. I sure hope it does not just
> happen to me?
This looks to be an issue with the responsiveness of those boxes. I'm
getting that too.
Hi,
On 14/11/17 16:04, Ralph Seichter wrote:
> I have since removed all cookies and data tied to the torproject.org
> domain from my Safari 11 cache, and now Relay Search seems to work as
> designed. I'm glad, of course, but it still seems weird. At least I have
> screenshots to prove that I did
On 14/11/17 15:35, Ralph Seichter wrote:
> On 14.11.17 13:52, Iain R. Learmonth wrote:
> I also notice that the "new look" does not work in Safari 11 on macOS
> 10.13.1 (High Sierra). For shame! Has nobody tested this?
>
> Problem detail: When accessing https://atlas.to
Hi David,
On 14/11/17 13:01, David Goulet wrote:
> Quick question for you. Atlas used to have the search box at all time in the
> corner which for me was very useful because I could do many search without an
> extra click to go back one level down like the new site has.
>
> How crazy would it be
Hi All,
You may notice that Atlas has a new look, and is no longer called Atlas.
For now no URLs have changed but this is part of work to merge this tool
into the Tor Metrics website.
The style is determined by the Tor Metrics Style, and modifications have
been made to fit this.
The decision
Hi,
On 14/11/17 05:03, Roman Mamedov wrote:
> Dear Tor project: this is very bad style to keep that in /var/lib, content
> with properties like this must go into /var/cache/ [1], where it would be
> automatically excluded from backups by default policies in most backup
> systems.
It does seem
Hi,
On 21/10/17 09:06, Roger Dingledine wrote:
> That said, the folks handling tshirt requests are the real arbiters
> of how they are interpreting my sentences, so I will defer to them. :)
I was sure we had a bug for this, but I can't find it. Here's a bug I
just filed to include eligibility
Hi,
On 15/10/17 09:07, nusenu wrote:
>> See proposal 234 [0] for adding bitcoin/zcash/etc addresses.
>
> Thank you for the pointer. This proposal is from 2014 and I havn't found
> any trac ticket for it, so I guess no one is working on implementing it.
> Once this is implemented I'll remove
Hi,
On 14/10/17 23:01, nusenu wrote a proposal.
The ContactInfo field doesn't need to be overloaded again. ):
See proposal 234 [0] for adding bitcoin/zcash/etc addresses.
Maybe we can work out new fields for extrainfo documents [1] that could
contain some of this information.
I do think this
Hi,
On Fri, Sep 22, 2017 at 04:52:02PM +0100, Pascal Terjan wrote:
> There may be some timing difference, a faster response if the
> connection fails/is rejected vs if nothing is listening
Ah, I hadn't thought of that. Although I guess this would also be the case
if there is congestion or a
Hi teor,
On Fri, Sep 22, 2017 at 11:14:07PM +1000, teor wrote:
>
> > On 22 Sep 2017, at 23:03, relay 000 wrote:
> >
> >> Someone is using the hidden service rendezvous protocol to ask non-exit
> >> relays to scan non-tor IP addresses.
> >
> > wow, people can misuse my
Hi,
On 17/09/17 04:56, Iain R. Learmonth wrote:
> I'll have a think about this.
I had a little think about this. While the search strategy is something
to consider, I've hacked up a simple tool for building circuits and
detecting, at a very high level, when it fails. I don't yet have the
rea
Hi,
On 17/09/17 00:56, Roger Dingledine wrote:
> Actually, no, we want it to be the case that all relays can reach all
> relays. The less true that becomes -- that is, the less clique-like
> the network topology becomes -- the more complicated the anonymity
> measurements become, and that is
Hi All,
This is clearly something that operators want.
> https://nos-oignons.net/Services/index.en.html
This looks like a great idea. I can't promise immediate progress on
this, but I'll file a trac ticket shortly and hopefully progress can be
made soon.
Thanks,
Iain.
Hi,
On Sat, Mar 04, 2017 at 08:23:00PM +, nusenu wrote:
> > [10:55] Why does Atlas shows the "not recommended software"
> > icon under "Flags" ? B/c this python snippet sjhows, that it is not a
> > flag in the (old) meaning: flags =
> > controller.get_network_status(relay=srv.nickname).flags
Hi,
On Thu, Jan 26, 2017 at 11:07:10PM +, Iain R. Learmonth wrote:
> Following the Metrics Team meeting today, it was decided to remove these
> graphs, at least until we can come up with something better.
Those graphs for which data will never be present (3 days and 1 week
traffic) no
Hi,
On Sun, Jan 22, 2017 at 09:55:43AM +0100, mistral.re...@posteo.net wrote:
> Many thanks for the reply including the link to the open ticket! I really
> hope that this gets sorted out at some point. I spent quite some time to
> sort out what might be wrong with my setup but good to know the
Hi,
On 06/07/16 18:25, tor relay wrote:
>> I've been running an exit node for over a year on OVH now, no problems
>> so far. Highly recommended (especially since they give me 10TB of
>> traffic for about 10$USD/month; considering I use about 7-8TB of that
>> per month, it's well worth it).
>
>
Hi All,
On 29/06/16 09:56, Karsten Loesing wrote:
> tl;dr: Globe is now retired in favor of an improved Atlas.
Atlas is improved, but I'd like to improve it further. I've been
tackling #6787 looking to improve the homepage and make Atlas easier to
use for someone that isn't already a Tor expert.
28 matches
Mail list logo