Max Nikulin <[email protected]> writes: > I do not think it is a good idea to use alternative front-ends as href > attribute in HTML as it is fetched from web server. E.g. > <https://github.com/alphapapa/org-ql> identify specific resource. It is > up to users to install a browser extension that redirects some requests > to alternative sites they prefer and they trust. Alternative instances > are transient, used as bookmarks they may become invalid. Unknown domain > may confuse users. Rewriting address from one alternative front-end to > another instance is more difficult than redirecting from canonical > address since all alternatives must be known in the former case. > Transforming link at the moment, when it is accessed, should be more > reliable from my point of view.
Do you have ideas how to implement what you propose? > FSF may try to develop a JS library that informs users and perhaps even > redirects to an alternative front-end (as opt-in) when users click on > links. It may be a challenge to implement this reliably and in a way not > disturbing users too much, to avoid complications with regulations like > GDPR. Maybe, but that's a tangent. FSF policy is very specific about linking to websites that require non-free JS: https://www.gnu.org/prep/standards/standards.html#References-to-Nonfree-Software-and-Documentation If the purpose for which you would refer to the page cannot be carried out without running nonfree JavaScript code, then you should not refer to it. Thus, if the purpose of referring to the page is for people to view a video, or subscribing to a mailing list, and the viewing or subscribing fail to work if the user’s browser blocks the nonfree JavaScript code, then don’t refer to that page. The extreme case is that of web sites which depend on nonfree JavaScript code even to see the contents of the pages. Any site hosted on ‘wix.com’ has this problem, and so do some other sites. Referring people to such pages to read their contents is, in effect, urging them to run those nonfree programs—so please don’t refer to those pages. (Such pages also break the Web, so they deserve condemnation for two reasons.) Instead, please quote excerpts from the page to make your point, or find another place to refer to that information. > I would consider moving Worg to another domain to have relaxed policy in > respect to links. The problem is not Worg domain, but the fact that orgmode.org main website links to Worg and then Worg recommends non-free web pages. Changing the domain will not change this problem. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
