An image (or any other type of file) with a "filesystem:" URL is already stored on disk (using the filesystem API) and the "https://web.telegram.org/temporary/xxxxx.jpg" part of the URL doesn’t represent an actual valid URL, just a unique identifier that the filesystem API uses to retrieve the file in its cache.
Not sure how to address this issue in oxide/webbrowser-app.
It appears the 'filesystem' URI scheme is deprecated and should probably not be used: http:// www.iana. org/assignments /uri-schemes/ historic/ filesystem.
An image (or any other type of file) with a "filesystem:" URL is already stored on disk (using the filesystem API) and the "https:/ /web.telegram. org/temporary/ xxxxx.jpg" part of the URL doesn’t represent an actual valid URL, just a unique identifier that the filesystem API uses to retrieve the file in its cache.
Not sure how to address this issue in oxide/webbrowse r-app.