Just not sure if they'd want to force everyone into the "/usr/share/homepage" directory?
Dunno. At some point we have to talk to them about such things. Might be acceptable. I mean, if anyone disagrees and later provides a patch that lifts that hardcoded folder, by all means.
This "/usr/share/homepage" directory is a convention we made up, not an pre-existing standard, right?
Right.
(This is the context: https://github.com/micahflee/torbrowser-launcher/issues/152)
Then each distribution could use their own sub-directory:
Sounds good.
[hr]
Discussing this on irc.oftc.net#tor-dev could help. They might be able to answer such detail questions.
Dunno. At some point we have to talk to them about such things. Might be acceptable. I mean, if anyone disagrees and later provides a patch that lifts that hardcoded folder, by all means.[/quote]
Sounds good.
[quote=“Patrick, post:76, topic:347”]Discussing this on irc.oftc.net#tor-dev could help. They might be able to answer such detail questions.
If successful, we will have a solution for proposing dynamic custom about: URLs for the browser startpage. Where the distro can set their own about: URL and local webpage path in environment variables.
One thing to keep in mind: the more generic and [sometimes contradicting goals] smaller and simpler the proposed change, the more likely it is to have upstream review and merge the patch.
One thing to keep in mind: the more generic and [sometimes contradicting goals] smaller and simpler the proposed change, the more likely it is to have upstream review and merge the patch.[/quote]
Totally agree!
Trying to make it as lean of a modification as I can.
And trying to also play to the interests of Tails community and the general distro concept as well.
As much as I would appreciate having such a test, the problem with this one seems to be that it only works when JS is active, thus making what it “puts out” rather useless in terms of the average user.
Any false positive would lead to high FUD rate in the forums and cause a lot time being spend with researching and explaining stuff while losing time working on actual issues. For that reason the Browser Tests - Whonix page as created.
Sorry, I should have been clearer. I meant the ASCII Whonix logo that appears as the Whonix landing page whenever Tor Browser is started. @iry did it some time ago (I believe because some Tor Browser change at that time broke the previous version that did have a high-def Whonix logo if I remember correctly).
Actually I like the 2020 version of the Whonix logo. It seems a waste not to use it in the landing page, particularly since people like it.
Would be good if that could be fixed. Sure I agree, no question, ASCII Whonix logo is bad. Better replaced with real image. But I somehow doubt that the underlying Tor Browser bugs which made this required were fixed in meanwhile. Passage of time doesn’t equal progress on lowest priority / wishlist bugs. From Tor Browser development perspective this is super low priority. Not easy to even find that discussion / bug report now.
Tor Browser only render HTML for local pages via file://, no images/CSS
In Tor Browser 7.0.10 (and earlier too, see below), if I open a local page via file:// only the HTML is rendered, but images are broken and CSS isn’t applied at all.
So I presume this broke in Whonix at that time, devs reacted, and the community has had the unpretty ASCII every since.
Doesn’t look like anybody complained about it breaking since then over on trac.torproject.org, so it would probably be a low-risk change if Whonix reverted to using a nice hi-def image (2020 logo version).
