Re: [tor-bugs] #28065 [Internal Services/Services Admin Team]: Tor web docs

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#28065: Tor web docs
-------------------------------------------------+-------------------------
 Reporter:  hiro                                 |          Owner:  (none)
     Type:  defect                               |         Status:  new
 Priority:  Medium                               |      Milestone:
Component:  Internal Services/Services Admin     |        Version:
  Team                                           |
 Severity:  Normal                               |     Resolution:
 Keywords:                                       |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------
Description changed by hiro:

Old description:

> During the meeting in CDMX some of us chatted about the possibility to
> build and maintain a sort of Tor web docs (like the mozilla web docs
> [1]).
>
> The idea is to collect all the techniques we use to make websites
> tor-browser and privacy friendly in a single place. We could also
> include the reasoning behind doing certain things in pure css vs js. Or
> why we decide to do things in a certain way.
>
> Some topic that I have been thinking about are:
>
> - Why tor browser is slightly different from Firefox (or another browser)
>
> - Why does my app work differently in tor browser?
>
> - How can I make my app compatible for people that do not use JS?
>
> - Code examples for css and js
>
> - Server side website programming, what to keep in mind...
>
> While all these topics are documented in various articles around the
> interwebs, I kinda think we (tor community) should own something like
> this, since it would also help to push forward the idea that the web as
> we know it needs to change.
>
> Up to now I have always thought this sort of content belonged to the
> styleguide. Recently I have been thinking that while the individual
> implementation details of what use in our websites can be included in
> the styleguide, the reasoning behind those and the general
> implementations should be put somewhere else.
>
> Also I do not think these topics belong directly to the dev portal, as I
> tend to think that should be about developing on tor rather than
> considering how the web works a bit differently when using tor browser.
> Unless we would rather do a specific section regarding all this in the
> web portal.
>
> Further things to consider:
> - Kevin (on cc) is working on a Tor friendliness scanner tool for
> websites.
> - We see often threads like the following on our mailing lists:
> https://lists.torproject.org/pipermail/tor-onions/2018-August/000295.html
> This one is about how to avoid privacy leaks for onion services.

New description:

 During the meeting in CDMX some of us chatted about the possibility to
 build and maintain a sort of Tor web docs (like the mozilla web docs [1]).

 The idea is to collect all the techniques we use to make websites
 tor-browser and privacy friendly in a single place. We could also
 include the reasoning behind doing certain things in pure css vs js. Or
 why we decide to do things in a certain way.

 Some topic that I have been thinking about are:

 - Why tor browser is slightly different from Firefox (or another browser)

 - Why does my app work differently in tor browser?

 - How can I make my app compatible for people that do not use JS?

 - Code examples for css and js

 - Server side website programming, what to keep in mind...

 While all these topics are documented in various articles around the
 interwebs, I kinda think we (tor community) should own something like
 this, since it would also help to push forward the idea that the web as
 we know it needs to change.

 Up to now I have always thought this sort of content belonged to the
 styleguide. Recently I have been thinking that while the individual
 implementation details of what use in our websites can be included in
 the styleguide, the reasoning behind those and the general
 implementations should be put somewhere else.

 Also I do not think these topics belong directly to the dev portal, as I
 tend to think that should be about developing on tor rather than
 considering how the web works a bit differently when using tor browser.
 Unless we would rather do a specific section regarding all this in the
 web portal.

 Further things to consider:
 - Kevin (on cc) is working on a Tor friendliness scanner tool for
 websites.
 - We see often threads like this [2] on our mailing lists. This one is
 about how to avoid privacy leaks for onion services, but we might identify
 more similar best practice tips being discussed.

 [1] https://developer.mozilla.org/en-US/
 [2] https://lists.torproject.org/pipermail/tor-
 onions/2018-August/000295.html

--

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28065#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

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