Opened 6 years ago

Closed 3 years ago

#10407 closed defect (wontfix)

check tells people about javascript but points them to atlas

Reported by: arma Owned by: arlolra
Priority: Medium Milestone:
Component: Applications/Tor Check Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

At the bottom of check.tp.o we tell them whether they're running javascript, and point them at the faq that tells them they're welcome to turn javascript off if they feel safer.

And then if check thinks they're using Tor, it invites them to go to atlas to learn more about their exit relay.

And atlas basically doesn't work with javascript off. Neither does globe.

I wonder if there's a fix? Seems like a messy tradeoff all around.

Child Tickets

Change History (8)

comment:1 Changed 6 years ago by arlolra

Ah yes, I noticed this in https://lists.torproject.org/pipermail/tor-talk/2013-December/031363.html (Is that user confused that since noscript is present, JavaScript is disabled?)

Well, the answer might be asking Atlas/Globe developers for better progressive enhancement on their sites. But JavaScripts is part of the web and the FAQ clearly states that the ultimate goal is a combination of firewalls and sandboxing that allow users to browse with JS enabled. So, maybe this is more just an example of the tradeoff you're making by disabling JavaScript.

I can always remove the link to Atlas altogether.

comment:2 Changed 6 years ago by arlolra

I wrote a patch to render Globe on the server side, https://github.com/makepanic/globe/pull/42

Not sure yet if that's the approach Christian wants to use because they seem to working on a rewrite in node.

In any case, a solution here is imminent.

comment:3 Changed 5 years ago by arma

Is the solution here still imminent? :)

comment:4 in reply to:  3 ; Changed 5 years ago by arlolra

Replying to arma:

Is the solution here still imminent? :)

Wow, 7 months ... Christian was making progress on globe-node but considering they've gone and disappeared, imminent now seems a bit strong.

If no one steps up soon to develop an Atlas/Globe fork, I'll volunteer there and a timeline will be clearer.

comment:5 in reply to:  4 Changed 5 years ago by ultrasandwich

Replying to arlolra:

Replying to arma:

Is the solution here still imminent? :)

Wow, 7 months ... Christian was making progress on globe-node but considering they've gone and disappeared, imminent now seems a bit strong.

If no one steps up soon to develop an Atlas/Globe fork, I'll volunteer there and a timeline will be clearer.

I am interested in helping out night/weekend style on that fork as well.

comment:6 Changed 5 years ago by RahulRRixe

Is this issue is still open. I am interested in contributing it. I have installed the package on the local system and I needed to know whether I have to contribute to atlas code or in the Tor Check.

comment:7 Changed 5 years ago by arlolra

Is this issue is still open. I am interested in contributing it.

Yes.

I have installed the package on the local system and I needed to know whether I have to contribute to atlas code or in the Tor Check.

I think globe is the preferable relay explorer, but it's searching for a maintainer. The idea being to finish the port from ember to node.

comment:8 Changed 3 years ago by arlolra

Resolution: wontfix
Severity: Normal
Status: newclosed

This is more of an Atlas issue, which anyways seems to work at the medium-high security slider setting.

Note: See TracTickets for help on using tickets.