@Patrick @mig5 it appears to be working great. thank you and sorry for the late reply.

Does this work for you? @tempest

@Patrick I have set it to a temporary redirect now (302). In my tests in Firefox, the request is not being cached (server sends back the 302 each time according to Nginx logs)

Works great! Thanks @mig5!

I suggest not permanent redirection, otherwise browsers may cache old version.

Edited above comment a few times to fix syntax

Added this to /etc/nginx/sites-enabled/download.whonix.org.conf:

In T895#18241, @mig5 wrote:

It doesn't strike me as too hard to just add a 'current' symlink pointing to the latest release?

Another approach might be to use Nginx redirects (and a shell script or something, to maintain changes as new versions come out), so that URLs like https://download.whonix.org/ova/current/Whonix-XFCE-current.ova redirect to https://download.whonix.org/ova/14.0.1.4.4/Whonix-XFCE-14.0.1.4.4.ova . Useful?

It doesn't strike me as too hard to just add a 'current' symlink pointing to the latest release?

Hi Tom!

Tracker updated at https://github.com/jthingelstad/foreground/issues/182

No, not action buttons. But it's cool that this works now. Didn't know that's possible.

Darn, I see the top nav does click to drop but no links are usable in the drops.

mediawiki foreground skin: make items in navigation clickable without drop-down and without javascript

Awesome! All done except: mediawiki foreground skin: make items in navigation clickable without drop-down and without javascript

I went ahead and toned down font-size on h tags a bit. Looks better although <h3> might need to drop a touch more, 1.5 instead of 1.6.

New code select looks nice. However it does not work yet when javascript is disabled.

• style="width:800px'" fixed using https://www.whonix.org/wiki/Special:ReplaceText (long time user, awesome extension) Pages such as the https://www.whonix.org/wiki/Bridges no longer needlessly let mobile users to scroll empty content on the right which is good.
• New code select looks nice. However it does not work yet when javascript is disabled.

Just a note, I change the mouseover pointer to cursor: text; just as the current textareas.

I see. No idea what's doing that. Could you try please to figure out

what's doing this?

Hutchy68 (Tom Hutchison):

Hutchy68 added a comment.

> Not fixed:
> 
> There is too much white space on the left and the right side of any wiki page. (I always have to zoom in to 130% - 150% to use all the space of the screen.) (That is in a maximized desktop browser window.)
Sorry, I was misunderstanding your request. I set the `max-width` to 100%. Most website use a container with a max-width hard set to a number of pixels which is what Foreground does out of the box. You might find the 100% great on lots of pages, maybe not so on others. That would be your call. Anyway, the 100% is now set.

Not fixed:
There is too much white space on the left and the right side of any wiki page. (I always have to zoom in to 130% - 150% to use all the space of the screen.) (That is in a maximized desktop browser window.)

For CodeSelect multi line test:

In T809#17271, @Hutchy68 wrote:

CodeSelect has a hard set row="1" in the widget powering it. I cannot find any examples of multiple lines used except as the demo on the template page.

Most of the items have been solved. Exceptions:

https://www.whonix.org/blog/ already redirects to https://forums.whonix.org/c/news

@Patrick if you want to share with me out-of-band, the admin password for the mailman lists, I can look at this. I think the 'goodbye' setting is quick and easy to set.

merged into T809

merged into T809

https://forums.whonix.org/t/content-security-policy-now-deployed-on-whonix-websites

We have now a DNS Certification Authority Authorization (CAA) Policy.

In T84#14765, @marmarek wrote:

Well, google is going to deprecate HPKP in chrome/chromium.

Same as T84#14765.

https://forums.whonix.org/t/replacing-whonix-wordpress-blog-https-www-whonix-org-blog

Well, google is going to deprecate HPKP in chrome/chromium.

Great!

From the console log:
Blocked http://kkkkkkkkkk63ava6.onion/blog/ in page http://kkkkkkkkkk63ava6.onion/blog/ from extracting canvas data. http://kkkkkkkkkk63ava6.onion/blog/:51.
Line 51 is related to Wordpress' emoji-rendering code, which is done with the HTML5 canvas.

Can someone update me on the workflow for changing the website?