better workaround for Code OSS remotes

README.md

@@ -714,7 +714,8 @@ In host, create new FF profile (`about:profiles`) for that purpose, and configur
 
 Note that VS Code (and all related products) has a protection intended to prevent OSS variants from connecting to proprietary versions of VS code.
 However, apparently, it is implemented in such a way that it prevents even different OSS products from connecting to each other.
-Only "Code OSS" is packaged for Alpine; and only VSCodium has server-side builds, so you'll need to patch Code OSS to make it pretend to be VSCodium.
+Only "Code OSS" is packaged for Alpine (until https://gitlab.alpinelinux.org/alpine/aports/-/issues/14860 is implemented);
+and only VSCodium has official server-side builds, so you'll need to use custom server-side builds with Code OSS.
 
 Steps to get it running, assuming that you already have keyring and key-based SSH auth (with non-RSA key) configured:
 
@@ -745,7 +746,11 @@ In my experience, changing `nameShort`, `nameLong`, `applicationName`, `dataFold
 and adding `updateUrl`, `quality` and `commit` fields was enough.
 But most of these fields are probably irrelevant and can be left as is.
 
-Run `code-oss`, add "Open Remote - SSH" extension by jeanp413, exit.
+Run `code-oss`, add "Open Remote - SSH" extension by jeanp413.
+Go to its settings, and set "Server Download Url Template" to
+`https://github.com/gitpod-io/openvscode-server/releases/download/openvscode-server-v${version}/openvscode-server-v${version}-${os}-${arch}.tar.gz`
+(otherwise it will download VSCodium server-side builds by default).
+Exit `code-oss`.
 
 Add `"enable-proposed-api": ["jeanp413.open-remote-ssh"]` at the root level of `~/.vscode-oss/argv.json`.