Charles Choi <kickingve...@gmail.com> writes: >> On Jun 26, 2025, at 5:16 AM, Max Nikulin <maniku...@gmail.com> wrote: >> >> I would keep contents of this section either in the current article or in >> archive (but accessible from web). Certainly it should be marked as a >> historical artifact. >> > > Honestly, I’m not seeing there being much value to having the Opera > section kept intact either as an archive (which is problematic as > there is no archive file for org-protocol.org) or in a history section > as the guidance it provides isn’t really actionable. This text is > under source control, so if it needs to be resuscitated it can be.
Let's drop it, then. Make sure to note it in the commit message. I guess Max was right (upthread) that my feedback wasn't clear. To be clearer, I'm fine with deleting outdated guidance as long as there's a stated reason for it and a reasonable time for people to object on the mailing list. Max wrote: > I have not played "git blame" game, but I suspect, this section is > from epoch when Opera had its own rendering and JS engines. Currently > it is based on Chromium and the text is likely outdated. I was missing that background (I last used Opera sometime around ~2002, I think). Sounds like a convincing reason to delete it. Max wrote: > I would keep contents of this section either in the current article or > in archive (but accessible from web). Certainly it should be marked as a > historical artifact. [...] I have seen various > recipes in blog posts and other web pages, but I was not sure if that > info was still useful. I think, we may save some time for new users by > clearly saying that specific instructions were applicable several years > ago, but there is no point to try them now even if org-protocol does not > work. I understand the point, but retaining instructions for the purpose of explaining that there's probably no point in trying them -- that sounds like something that should be done sparingly, if at all. We are doing something like that on this page for org-remember and the old slash-separated URIs, but I'm not sure it's a standard we should set ourselves for third-party apps. Yours, Christian
