Updating the Tor binary included with Ricochet #618

jonah · 2018-11-25T14:02:13Z

ghost commented

2018-11-25 14:02:13 +00:00

(Migrated from github.com)

Description

Screenshot:

Resolves: #474

## Description Screenshot: ![ricochet-symlinks](https://user-images.githubusercontent.com/42108382/48980065-30520680-f0bc-11e8-9546-cbcb93dd5398.png) Resolves: #474

ghost commented

2018-11-25 15:06:34 +00:00

(Migrated from github.com)

Preview: http://62.102.148.154:19472/#im

ghost commented

2018-11-25 15:06:57 +00:00

(Migrated from github.com)

@beardog108 Thoughts?

jonah approved these changes 2018-11-25 15:07:05 +00:00

ghost commented

2018-11-25 17:32:55 +00:00

(Migrated from github.com)

@tya99 I think it would be better if the ricochet warning was collapsible or linked to a github comment (like how we do the ipfs warning), because it takes up too much screen real estate just for people who want to use ricochet

👍 1

Vincevrp (Migrated from github.com) reviewed 2018-11-25 18:57:49 +00:00

Vincevrp (Migrated from github.com) left a comment

@tya99 I think it would be better if the ricochet warning was collapsible or linked to a github comment (like how we do the ipfs warning), because it takes up too much screen real estate just for people who want to use ricochet

I agree. Did you write this yourself @tya99? If not, please link to the original content instead.

> @tya99 I think it would be better if the ricochet warning was collapsible or linked to a github comment (like how we do the ipfs warning), because it takes up too much screen real estate just for people who want to use ricochet I agree. Did you write this yourself @tya99? If not, please link to the original content instead.

ghost commented

2018-11-26 02:23:06 +00:00

(Migrated from github.com)

I think it would be better if the ricochet warning was collapsible or linked to a github comment (like how we do the ipfs warning)

Could do that however I think that might detract from how important it is. Perhaps we could put it at the end after "Related Information".

Ideally it would be great if we had foldable headings on the privacytools.io page like this for example.

I agree. Did you write this yourself @tya99?

Yes I did. See Issue #474 part of the reason I am reluctant to just leave it as a github comment. Should something happen to github or the repository or even the privacytoolsIO account it would be lost and not tracked within source control.

> I think it would be better if the ricochet warning was collapsible or linked to a github comment (like how we do the ipfs warning) Could do that however I think that might detract from how important it is. Perhaps we could put it at the end after "Related Information". Ideally it would be great if we had foldable headings on the privacytools.io page [like this for example](https://en.wikipedia.org/wiki/Code_folding). > I agree. Did you write this yourself @tya99? Yes I did. See Issue #474 part of the reason I am reluctant to just leave it as a github comment. Should something happen to github or the repository or even the privacytoolsIO account it would be lost and not tracked within source control.

ghost commented

2018-11-26 07:13:11 +00:00

(Migrated from github.com)

Books often have sections with info like this at the end. Maybe we could create a separate page for these things?

ghost commented

2018-11-26 19:41:24 +00:00

(Migrated from github.com)

@Shifterovich If we still have a link that would jump/go to the section, that would be acceptable.

ghost commented

2018-11-26 20:07:59 +00:00

(Migrated from github.com)

If we move this section to the bottom of the page, the links will work.