Opened 8 years ago

Closed 8 years ago

#2992 closed defect (fixed)

bridge-by-default bundle links on blog are transient

Reported by: cypherpunks Owned by: erinn
Priority: Medium Milestone:
Component: Webpages/Website Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

The links to the files in https://blog.torproject.org/blog/windows-bridge-default-bundle result in a 404.  

Are these bundles going to be kept up to date?  I notice they are for 0.2.2.23-alpha, whereas 0.2.2.24-alpha is current.  

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by erinn

Resolution: invalid
Status: newclosed

https://www.torproject.org/dist/vidalia-bundles/vidalia-bridge-bundle-0.2.2.24-alpha-0.2.12.exe
https://www.torproject.org/dist/vidalia-bundles/vidalia-bridge-bundle-0.2.2.24-alpha-0.2.12.exe.asc

I'm closing as invalid, but I should think about the smart way to link to files in blog posts since we eventually move all files to archive.torproject.org in order to save mirror space.

comment:2 Changed 8 years ago by arma

Resolution: invalid
Status: closedreopened
Summary: bridge-by-default bundles are 404bridge-by-default bundle links on blog are transient

[Reopening so people notice]

One approach is to link to the download page that has links to the individual bundles.

Then all your blog posts link to the same URL, but it's always the right URL.

You could add an anchor to the appropriate place in the download page.

(These particular bundles aren't linked to from anywhere except your most recent blog post, right? They should probably get a home on one of the download pages.)

comment:3 Changed 8 years ago by nickm

Component: Tor bundles/installationWebsite

comment:4 Changed 8 years ago by erinn

Yes, they deserve a home on the download pages, along with the new TBBs. I'll spend some of today updating those. And yes, you are right about how to link. I will do that from now on. Thanks!

comment:5 Changed 8 years ago by erinn

Okay, I added the bridge bundle link and a little information:

https://torproject.org/download/download

So.

  1. Is it confusing? I want to make it clear why using a bridge-by-default bundle might be preferable, but the wording could be clearer/more succinct/more informative somehow. I don't know that anyone will read the bridge page, so a better description would help.
  1. There's no stable bridge-by-default bundle and that is making the formatting wonky. I'll fix that by making a stable bundle, unless there's some reason stable is not a useful bridge-by-default version to have.

Separately, the more I look at this page, the less clear it is how I should go about offering the Firefox 4 TBBs. "There are FIVE ways to use Tor!" seems like it could be the maximum level of confusing, so since it's not the easy download page, do I just assume people can say "hey yeah I want the Firefox 4 TBBs" or do I leave those on the TBB page itself, to be discovered by people who manage to find their way there?

More on topic for this bug title: should I link to non-TBB bundles with the download page, and link to TBB with the TBB page?

comment:6 in reply to:  5 Changed 8 years ago by arma

Replying to erinn:

Okay, I added the bridge bundle link and a little information:

https://torproject.org/download/download

So.

  1. Is it confusing? I want to make it clear why using a bridge-by-default bundle might be preferable, but the wording could be clearer/more succinct/more informative somehow. I don't know that anyone will read the bridge page, so a better description would help.

I think it's ok.

  1. There's no stable bridge-by-default bundle and that is making the formatting wonky. I'll fix that by making a stable bundle, unless there's some reason stable is not a useful bridge-by-default version to have.

I'd say you'll have more fun fixing the formatting than you will making a whole separate set of bridge-by-default bundles and then maintaining them forevermore. I expect most bridge-by-default users will be people who download and run the thing because somebody tells them to, and don't even use the client part of Tor -- not otherwise ordinary Tor users who didn't want to figure out what to click in Vidalia. One version at a time should be plenty.

Separately, the more I look at this page, the less clear it is how I should go about offering the Firefox 4 TBBs. "There are FIVE ways to use Tor!" seems like it could be the maximum level of confusing, so since it's not the easy download page, do I just assume people can say "hey yeah I want the Firefox 4 TBBs" or do I leave those on the TBB page itself, to be discovered by people who manage to find their way there?

Depends how much testing you want them to get. Sticking them on the download page if you think they might not work is probably premature. But that said, you have to get from here to there somehow. I'd suggest just replacing the main TBB with the new TBB once you think everybody 'should work'.

More on topic for this bug title: should I link to non-TBB bundles with the download page, and link to TBB with the TBB page?

If you do that, few people will use TBB, which is the opposite of what phobos seems to want.

I'd say one way to get out of this situation (you're right, the download page Windows section sure has a lot of choices) is to get us closer to the day when download-easy is the default page people get when they click on 'download'.

comment:7 Changed 8 years ago by arma

Resolution: fixed
Status: reopenedclosed

Looks like bridge-by-default bundles are now happily linked from the download page. Closing.

Note: See TracTickets for help on using tickets.