{"action":"created","issue":{"url":"https://api.github.com/repos/dreamwidth/dw-free/issues/1800","repository_url":"https://api.github.com/repos/dreamwidth/dw-free","labels_url":"https://api.github.com/repos/dreamwidth/dw-free/issues/1800/labels{/name}","comments_url":"https://api.github.com/repos/dreamwidth/dw-free/issues/1800/comments","events_url":"https://api.github.com/repos/dreamwidth/dw-free/issues/1800/events","html_url":"https://github.com/dreamwidth/dw-free/issues/1800","id":157792624,"number":1800,"title":"Elimate all non-free javascript","user":{"login":"srukle","id":9255609,"avatar_url":"https://avatars.githubusercontent.com/u/9255609?v=3","gravatar_id":"","url":"https://api.github.com/users/srukle","html_url":"https://github.com/srukle","followers_url":"https://api.github.com/users/srukle/followers","following_url":"https://api.github.com/users/srukle/following{/other_user}","gists_url":"https://api.github.com/users/srukle/gists{/gist_id}","starred_url":"https://api.github.com/users/srukle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/srukle/subscriptions","organizations_url":"https://api.github.com/users/srukle/orgs","repos_url":"https://api.github.com/users/srukle/repos","events_url":"https://api.github.com/users/srukle/events{/privacy}","received_events_url":"https://api.github.com/users/srukle/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/dreamwidth/dw-free/labels/status:%20untriaged","name":"status: untriaged","color":"ededed"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-05-31T23:27:17Z","updated_at":"2016-05-31T23:47:38Z","closed_at":"2016-05-31T23:47:38Z","body":"I attempted to use the sluggish Firefox app GNU LibreJS [1]. I don't use it any longer. But what I found was interesting, and I encourage DW administrators to give it a spin.\r\n\r\nAfter using it, I decided to eliminate all non-free JavaScript code from sites I have made personally. For an example, I learned about the non-free JavaScript my site uses and eliminated it [2]. The site runs just as well as it did prior to running the non-free code.\r\n\r\nWhen I used Dreamwidth, I noted that non-free JavaScript was detected. So I am asking a very broad and complicated question. Is there anyway Dreamwidth would support getting rid of its propriety code?\r\n\r\nOne thing I feel like I can be only critical about is the Google Analytics of the entire site. Could it be configured to be toggled by users who need it and disabled by default -- or at least toggled off for paid users?\r\n\r\n[1] https://addons.mozilla.org/en-US/firefox/addon/librejs/?src=ss\r\n[2] https://github.com/srukle/srukle.github.io/issues/1"},"comment":{"url":"https://api.github.com/repos/dreamwidth/dw-free/issues/comments/222854417","html_url":"https://github.com/dreamwidth/dw-free/issues/1800#issuecomment-222854417","issue_url":"https://api.github.com/repos/dreamwidth/dw-free/issues/1800","id":222854417,"user":{"login":"rahaeli","id":1716035,"avatar_url":"https://avatars.githubusercontent.com/u/1716035?v=3","gravatar_id":"","url":"https://api.github.com/users/rahaeli","html_url":"https://github.com/rahaeli","followers_url":"https://api.github.com/users/rahaeli/followers","following_url":"https://api.github.com/users/rahaeli/following{/other_user}","gists_url":"https://api.github.com/users/rahaeli/gists{/gist_id}","starred_url":"https://api.github.com/users/rahaeli/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rahaeli/subscriptions","organizations_url":"https://api.github.com/users/rahaeli/orgs","repos_url":"https://api.github.com/users/rahaeli/repos","events_url":"https://api.github.com/users/rahaeli/events{/privacy}","received_events_url":"https://api.github.com/users/rahaeli/received_events","type":"User","site_admin":false},"created_at":"2016-05-31T23:47:38Z","updated_at":"2016-05-31T23:47:38Z","body":"Ha, jinx, @zorkian -- I was already typing a response with much the same answer.\r\n\r\nI'm going to agree with Mark, and in fact go a step further and close this issue, not because the answer is 'no' but because the answer is 'it's complicated' and any project to reduce or eliminate nonfree JS would be large, messy, and need careful specs and regression testing -- we've found that those kinds of bugs are really a bad fit for Github Issues, because they never end and it's impossible to keep track of and really hard to figure out what to do with them if the person who's working on the issue loses interest partway through.\r\n\r\ndw-dev would be a better fit for the discussion, really -- if there are specific nonfree JS libraries you think can be replaced by an equivalent free JS library, you can post there and we can do the analysis to see if the replacement does do what we need it to do. (Then, once everybody agrees it's a good 1:1 equivalence, you can open individual issues for replacing each specific library.) Like Mark, I'm all for replacing nonfree stuff with free stuff! But generally speaking, in our dev history, we've only used nonfree alternatives when the person working on the project couldn't find an appropriate free library. Things certainly could have changed since then, and it's always worth a good thorough analysis, but one of our big priorities is not reinventing the wheel: if it's a choice between a nonfree library and rolling our own, we'll go with the nonfree library. (Rolling your own is how you get into messy situations where you're stuck maintaining a mass of nonstandard JS libraries that need constant bugfixes, browser fixes, and accessibility fixes.)\r\n\r\nAbout Analytics: we use it to get information about how people are accessing the site (with what browsers, on what platforms, etc) in order to determine what our browser support policy should be, what browser bugs we need to target, what browser bugs we can safely ignore, etc. (For instance, \"this bug only affects Browser X\" is more important to fix when Browser X is 40% of our traffic vs 1% of our traffic.) We check it regularly, and it provides important information -- not having that information would be detrimental to the site. \r\n\r\nWe already only add the Analytics code on site pages that don't have the potential to contain really personal stuff -- not on journals, not on locked/private entries, etc, etc. (People can individually enable it in their journals, but if they do, it's their own Analytics account, not DW's.) People who don't trust Analytics to only be doing what it says it's doing or don't want to contribute to those stats even anonymously can block the JS file (and we do recommend that in the Privacy Policy), with the caveat that it means their browser stats won't be counted in the aggregate anonymized data that we use to make decisions about the site."}}
{"actor":{"display_login":"rahaeli"}}