ToDo for Kicksecure ™ Wiki Devs

From Kicksecure
< Dev
Jump to navigation Jump to search

Your support makes
all the difference!

We believe security software like Kicksecure needs to remain open source and independent. Would you help sustain and grow the project? Learn more about our 10 year success story and maybe DONATE!

Website Enhancements Planning



new thank you donation message[edit]

1) CORS issues are fixed now? (Patrick attempted to fix these.)

2) explain Patrick how to draft a HTML e-mail with text-only fallback in Thunderbird

3) Possible to have a plaintext fallback if HTML is disabled by the e-mail client?

4) e-mail for

  • Kicksecure
  • Whonix

5) bug?

This page is in Quirks Mode. Page layout may be impacted. For Standards Mode use “<!DOCTYPE html>”.

Valid HTML better / good idea for best e-mail reader compatibility?


  1. How can I check CORS issues?
  2. In thunderbird multipart email can be accomplised by going to "Options > Sending Format" and choose "Both HTML and Plain Text"
    1. This Sending Format however only seems to take effect if the mail is truly sent. So saving it as a draft and then "saving as" .eml does work but does not create a multipart email
    2. So maybe admin should send the email to his own email address and then save the .eml file
    3. However this eml file needs to be modified for each recipient, so there needs to be more work done
    4. May another mail software needs to be involved
  3. The plaintext fallback is exactly what we want to accomplish with multipart
  4. What is meant with task 4?
  5. Maybe live discussion is needed


todo: discuss

What does (15 lines only) do?

Probably would have little effect for our wiki because of our custom skin? Does this functionality seem useful?


  • The development of this extension seems pretty interesting
  • The new extension (from pseudonym dev) is not much different from the original and seems to fix a faulty behavior of the original extension
  • Both versions consist of 2 parts: ext.purge.js and Hooks.php
    • In Hooks.php in every page (without our skin) there is a link added to call the purge page (which is not part of the extension but of mediawiki itself)
    • This is just a convenience shortcut, but useful - even for us. Because if a dev is already on the edit page then our purge via super menu is not available. Removing this extension however would not be a terrible loss but a small convenience downgrade
    • In ext.purge.js the convenience is even more improved for Javascript users only. Because then the link does not open the purge-page but is stopped and instead the purge action is instantly performed without going to the purge page
  • Both versions are not perfect
    • The original version fails to prevent the link to be augmented by Javascript. This might be due to it being loaded to early or other factors
    • The newer version fixes this behavior but also prevents nojs users to use this button at all. It will be there but non-functional
  • Suggestion (in order of preferability from Dev's perspective)
    1. However because it would be mainly for our convenience I suggest use the newer version
    2. If not then use the older version
    3. If not then write our own fork which would be the perfect solution
    4. Another option would be to just add our own purge button via a simple Javascript file on pages that don't have the skin. That would also be a ONLY-JS solution but it would be a bit quicker than the "perfect fork" solution
    5. If not then don't use at all, because we have instant access to purge via our skin


  • Do we even need the purge button still?
    • Only for template changes?
    • Otherwise cache invalidation is stable nowadays?
  • Weird anyhow that non-admins can clear cache.
  • MediaWiki's solution prevents crawlers from accidentally pressing that button.
  • noJS support not required.
    • JS-only solution good enough.
  • Could we make it login-only or admin only?

add querystring to Headscript[edit]

purpose: invalidate browser cache on css changes

  • append querystring to our custom css/js
  • append to fontawesome etc too?
  • read version number from a local file in /srv/shared/cssversion/version-file
  • sanity tests
    • check it is a real number
    • check string length maximum
  • fall back to querystring=error if local file is missing or has invalid contents

how do we update the version number? options:

  • hardcoded in headscript
  • manually on file
  • manually in MediaWiki:cssversion
  • mw-combine can bump the version number but that might run too frequently (by the server, for testing, could be changed but non-ideal)
  • by Patrick writing a script that checks if contents of mw-autogen folder changed (counting all file names and hashing all files)

Alternative considered Cache-Control HTTP header stale-while-revalidate:

  • Would result in lots of If-None-Match requets and 304 responses.

Upgrade mw-multi-wiki - delete deleted files[edit]


  • I suggest upgrading mw-multi-wiki
  • Currently it is the case that files which are deleted are not updated during mw-multi-wiki deploy
  • This means that a dev would have to delete the other files manually and keep track somewhere which files to delete later
  • This is a problem because sometimes files should not be deleted before everything is finished and admin has approved development. And it also cannot be deleted before because then the wiki which is not updated yet would not function anymore
  • So I suggest admin upgrades the mw-multi-wiki script and checks for formerly Category:MultiWiki files that are now deleted and delete them too
  • Or maybe find another solution


  • How mw-multi-wiki could detect deleted files from Category:MwDeleteMe?
  • A) mw-multi-wiki could be stateful and "remember" which pages were ever in mw-multi-wiki but that's ugly because then an idempotent, clean script would be dependent on remembering the state in some state file. The state would be difficult to share among developers.
  • B) A Category:MwDeleteMe could be invented. Delete all contents from the page and add that Category. Then mw-multi-wiki could remove it first from slave and eventually form the master wiki. Also non-ideal because not an intuitive process as it requires the developer to remember this because it's not a simple as using as using the wiki's internal deletion feature.
  • C) Deletion log doesn't contain categories.
    • Parsing the deleted revision for Category:MultiWiki might be error prone (if a wiki page was MultiWiki in the past but then it was only a comment).


Patrick asked on the MediaWiki mailing list.

new idea: diff the categories in the different wikis

report only

Logos Misc TODO[edit]


  • github sponsors credit card
  • Content in Kicksecure wiki and Whonix wiki
  • wiki text inconsistencies
    • Chapter "Definitions" currently shows:
      • Logo - seems to unspecific
      • Landscape logo
      • Text logo
      • Icon logo
    • Chapter "Current Kicksecure logos" uses a different language.
    • Chapter "Current Whonix logos" uses a different language.
  • logo consistent naming
  • projectname-logo-definition


MultiWiki: Think about PHP files[edit]

  • For the workflow it would be good to not only deploy the js and css files to the "slave" wikis, but also the php-scripts for combined and headscript content
  • Pro: if there are more than 2 wikis (which are not at the moment) then it's way easier to manage
  • Con: At the moment it's not necessary. And we would need to be very careful with who gets the rights

Stage Server as Master[edit]

  • MultiWiki feature requests:
    • The idea is the separate MultiWiki files into "code" (js, css files) and "content" (content pages)
    • pull code (CSS, JS, widgets) from Kicksecure stage server
      • How about templates such as Template:Header?
        • These need to be in a special category to be recognized as code?
  • stage server feature request:
    • The stage server becomes the master server for code files. That way new scripts can be developed and tested on the stage server without disrupting the normal production use of the public wikis. Once a new feature is ready it can be multiwiki deployed from the stage server (master) to the slave wikis
  • For content pages the Kicksecure wiki might still be the master however

Newsletter Widget[edit]

  • Widget here means "widget" generally as in a box with a special feature.
    • Not necessarily a MediaWiki widget.
    • Is there a better terminology than widget to avoid confusion?
  • features:
    • subscribe
    • unsubscribe
    • add the newsletter subscribe/unsubscribe to homepage
    • the widget should be re-usable in other places in the wiki
    • Ideally noJS compatible.
    • Just two (subscribe/unsubscribe) POST submit boxes.
    • The backend on the server could be a simple PHP script that just appends the e-mail address to a file subscribe.txt / unsubscribe.txt.
      • The PHP script should reject invalid e-mail address formats (such as with spaces in the middle or missing @ sign)
      • The PHP script would return "Success. Thanks for signing up!" or "Failure to sign-up. Please report this bug in the forums."
  • non-features:
    • double opt-in (this will be done manually at a later stage before sending any e-mails)
  • TODO: discuss


  • Topic was discussed. Script should be simple and at best not using a database
  • Dev did newsletter research. Conclusions
  • Options
    • We could write a completely new scripts
    • We could base a widget on the research by admin: (an old script)
    • We could by a modern script and set it up with mysql
  • Admin said he will do script research again

FlaggedRevisions CacheClear Workaround[edit]


TODO DEV[edit]

video production - Hidden Text Attacks[edit]


todo produce


Please port to using tab controller.

The A, B, C would be nicer if using tab controller.

Whonix homepage - Form elements do not have associated labels[edit] shows some suggestions:

Form elements do not have associated label

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.

Failing Elements

div.section-banner > div.inner-wrapper > div.overview-image-and-video-player > input#hide-overview-image
<input type="checkbox" id="hide-overview-image">

Heading elements are not in a sequentially-descending order[edit]

  • Heading elements are not in a sequentially-descending order
    • Heading elements in order is a very impractical metric which probably very few websites adhere to. Headline levels are very rarely used structurally (exception example MediaWiki and similar), but often rather as style choices. Especially smaller headlines which are very rarely used anyways h4-h6 are often used exclusively as style elements. For our project that would be possible especially if it's limited to few sites. But it would mean changing HTML as well as CSS
    • TODO: discuss


  • I would say this is very difficult because headlines are not only used by us but by mediawiki itself or extension in the "wrong order"


  • write bug report draft for if issue can be reproduced on (or
  • document this was discussed on dev/mediawiki


  • This "bug" is not due to mediawiki
  • As documented here this CAN be solved on our part
  • However this might be time consuming to find ALL pages where the headlines are not in correct order
  • Maybe admin can create a list of pages that he really wants to be fixed in this regard (important pages). Then dev can fix those pages in a reasonable time frame.


  • no local fixes
  • important thing is only that upstream bug report exists or is going to be created


  • I mean that this might be "our fault"
  • So mediawiki might not have "bugs" in this regard, but it was just our practice before to use these headlines in the wrong context
  • So this is not a workaround, but just fixing our own code
  • So a bug report would not be justified


homepage html optimizations[edit]

For Kicksecure and Whonix homepage. To reduce DOM size.

Something doable, useful here?

Instead of using this code;

<div id = ”navigation-main”>


            etc ..



It would be better to use this other one;

<ul id = ”navigation-main”>

    etc ..


Defer Upstream MediaWiki JavaScript[edit]


<script async="" src="/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector"></script>

Patrick could server side easily rewrite that to:

<script defer src="/w/load.php?lang=en&modules=startup&only=scripts&raw=1&skin=vector"></script>

(Nobody uses script async="" (not a syntax error - asked upstream). This is easily string replaced to script async using nginx.)

Progressive Web App PWA[edit]


You can find the site.webmanifest here:

  • mediawiki-customized-dist: public/favicons-kicksecure/site.webmanifest
  • mediawiki-customized-dist: public/favicons-whonix/site.webmanifest


  • do we need the extension or do we create our own
  • read
  • use Lighthouse (integrated in chromium developer console)
    • Content is not sized correctly for the viewport

The viewport size of 396px does not match the window size of 360px.

If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more.

  • Manifest doesn't have a maskable icon

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more.

critical css test[edit]



  • A simplified test if critical CSS inclusion into the head results in faster website speed at all.


  • Making mediawiki use critical CSS. How to integrate this with mediawiki will be considered at a later time in a separate task.



  • 1) Use a browser where you are logged out and have no cookies. This is because cookies and being logged in has an influence on the HTML provided by mediawiki.
  • 2) on /test/ add Kicksecure homepage with the normal HTML document that we have now: kicksecure-hp-normal-not-critical-css.html. This will be needed for speed comparison.
  • 3) create a copy kicksecure-hp-critical-css.html
  • 4) use some tool to extract the critical css. add the critical css to the head. (
  • 5) out-comment all other CSS for a simple test. Search the HTML document for stylesheet. (CSS load with media="print" onload="'all'" can and probably should be ignored and left enabled as it already loads async.)
  • 6) load all other CSS async
  • 7) compare speed of the two different HTML documents

Wiki Content[edit]



  • improve introduction, consider using font awesome using widget:Icon_Bullet_List if sensible
  • How understandable is ? Please suggest improvements.
  • improvements:
  • that page needs to be properly contextualized (Whonix-Host in development, volunteer help welcome, Whonix live available already anyhow)
  • goal of page: illustrate goal, ask for contributions (very much worthwhile. The current progress as of now is for large part based on contributions.)



  • general review
  • content improvement

soft todo:

  • note: Whonix wiki/Features nicely shows a table when googleing for "Whonix features"
    • Therefore keep/improve "Whonix ™ Soft Features" table


  • irritating: The features listed here have other names and other profiles than the features listed on Homepage -> Somehow rename the page or chapter to make that better or other suggestions=
  • Anonymous Browsing and Anonymous Communications, Hosting and Publishing seem to be more like use cases than features -> OK.
  • Platform Flexibility
    • What does "based on" have to do with flexibility? -> See chapter About#Based_on_Debian. In short: anything possible with the things its based on should work with Whonix too. No artificial restrictions or limitations which are often falsely assumed.
    • What does "Free, Open Source, Libre, Freedom Software." have to do with flexibility? -> Customization is possible and relatively simple.
    • What is "Virtual machine images with Type I or 2 hypervisors." ? -> Why is that mentioned? Shows that Whonix is flexible enough to be ported to different hypervisors.
  • Pre-installed software - why are there not all apps mentioned like on the homepage? -> Please update any missing ones. On wiki/Features it can be more use case based and more elaborated.
  • What is "torification" for the uninformed user? -> Torification means the process of routing traffic over Tor.
  • Security and Anonymity Protection: They are not real sentences. And it's highly technical. The reader does not know what is even meant by most of this -> True. Can be elaborated?
  • Tor Network / Torification
    • The text consists of sentences but is a pretty cold start. "Most applications can be" - where in Whonix or elsewhere? What is Tor? -> ""Most applications can be" - applies anywhere. Outside and inside of Whonix. But in that chapter, it's probably best to talk about Whonix. If mentioning the outside Whonix use case, then that there is a much higher risk for leaks. Related to
    • "Both, pre-installed and custom installed applications can be use" - does this have anything to do with tor? -> Related to flexibility of Whonix. Some people assume only pre-installed applications can be used. This is false. Also most custom installed applications can be installed. That should me mentioned somehow.
    • This whole chapter seems like a technical documentation, not like a promotion. -> Good if it's both?
  • Tunnel and Chaining Support: Very little explanation. Unintelligeble for non-technical users -> True. Please add more context.
  • Tunnel Other Anonymizing Networks: like Tunnel and Chaining Support
  • Tunnel Support: Very technical sentence and even more technical table
  • Whonix ™ Soft Features: Explanations are mid-technical and rather "lifeless" -> True.

Mobile_Phone_Security wiki page content enhancements[edit]


  • read
  • keep notes about the most shocking security and privacy issues, these will be needed for the summary chapter that is to be invented
  • summary: on the very top, add a new chapter "Summary", write a summary on top why securing a smartphone and not being spied on is doable in theory but in practice pretty much unfeasible for most users.
  • add a few more bulletpoints on the very top (currently there is only "Massive Data Harvesting by Most Phones." and "There are backdoors in most mobile devices."
  • add introduction chapter on the very top?
  • advice on a better page title as well as
    • SEO description
    • find/create better illustrative image
  • other content suggestions?

Whonix Homepage Image Fixes[edit]

  • any illustrative images looking non-ideal and should be replaced?

Kicksecure illustrative images[edit]

  • any illustrative images looking non-ideal and should be replaced?

illustrative images creation[edit]

Implementation probably needs discussion.

  • Hiding your identity is harder than just hiding your IP.
  • You can't be anonymous without being secure.
  • your Whonix with Tor versus your IP without Whonix
  • route randomization
  • Ask yourself - privacy by design / privacy by policy
  • freedom / freedom security / security
  • why security matters
  • why anonymity matters



Thumbnails improvement[edit]

  • Admin didn't like thumbnails "double border"
  • Maybe more slick design?


  • Minimal design was tried here: Testpage1
  • Maybe already a good solution?

check ticket[edit]


  • Dev read the claims, did research and tested the suggestions
  • Below is the text Dev would suggest replying to the current threat (two answers currently). Copy from source code

In response to matmarex' reply we would agree that this is not technically a bug with Collapsible Elements regarding HTML validity. Also we support the role="none" solution. We tested this already and it worked.

We also agree with Izno that <button class="mw-collapsible-text">Expand</button> might be the better solution altogether. And CSS is already used to add the brackets before and after. So it would just be changing the CSS and not introducing more complexity by adding CSS where there was none before.

An [a] typically represents a link, a download or a jump label (with the name attribute before this solution was generally replaced by ids as jump labels). [a] is not designed to be used as an interactive element. So while syntactically correct and valid the use of [a] could be considered wrong here regarding context and use case.

FlyInNotification mobile small version[edit]

  • On mobile FINotification too big, fills screen
  • Mobile version please


  • Dev chose breakpoint at 550px screen width, because then the large version takes up half the screen
  • Then it breaks to smaller version which fills half the screen on 380px (our lowest supported screen width)
  • Dev could do more breakpoints but one seems enough
  • Dev also suggest not making the notification smaller because its purpose IS to get into the users field of view and be noticed

Total Blocking Time[edit]

Total Blocking Time went up on google pagespeed for mobile. Ideas why? Anything changed? Related to uglifyjs?


  • Research was conducted on possible issues
  • Source maps could not be found in research to cause performance issues
  • Then it was tried to change the use of source map via customized wiki. But "run-git-pull" failed with: Exit code: 128 output: ""
  • Admin please fix wiki pull


  • fixed (github changed SSH fingerprint)
  • use for testing this?


First Contentful Paint 1.6s / 1.7s 1.1s / 1.2s 1.1s / 1.2s 1.1s / 1.1s
Total Blocking Time 50ms / 70ms 370ms / 580ms 110ms / 220ms 370ms / 210ms
Speed Index 1.8s / 1.9s 1.9s / 1.9s 1.6s / 1.4s 1.7s / 1.5s
Largest Contentful Paint 3.3s / 3.4s 3.0s / 3.6s 3.4s / 3.7s 3.4s / 3.0s
    • Analysis
      • It seems the only metric truly affected IS total blocking time, the rest is pretty much the same
      • It seems also obvious that the new scripts - prism and instant page - have a significant impact on TBT, but are NOT the only reason because without scripts (meaning also without combined.min.js) it's still not as fast as before
      • Dev did a diff of OLD and NEW and saw some differences and found that in flyinnotification the image should be decoding="async" loading="lazy" which was already fixed too but didn't change much for pagespeed
      • Dev also thinks it's possible that deferring Javascript leads to a worse TBT, because [Total blocking time] = [Time to interactive] minus [First contentful paint] → so the longer JS is deferred the longer it might take to reach time to interact. That is however just a speculation. This page here is a great overview over the topic - not that this page states "It is important to specify that Time To Interactive is not a standardized indicator. It may therefore evolve. Note also that, although Google has included this metric in the calculation of the Lighthouse and PageSpeed Insights score, its weight has decreased during recent changes in the calculation of the score, to the point that it seems to be bound to disappear eventually."
      • Here is some more explanation for total blocking time and suggestions to improve and possible reasons why it might have increased in our development
    • How to proceed
      • Dev suggests admin to define a course: Invest more time into improving this metric or waiting for this metric to phase out?
      • Because - this was not mentioned before - there were also tests done with gtmetrics which gave very good results and slightly worse results when the "connection" was heavily throttled, indicating that maybe only server speed or dome size could be improved


  • check with chromium 112 with built in lighthouse in chromium developer toolbar
  • Lighthouse 10 will be available in Chrome 112, currently scheduled for release on March 29, 2023.
  • also happens with mediawiki therefore probably a pagespeed bug or less likely a mediawiki issue

DONE / Log of DevSprint since 2021-12[edit]

  • 2023-03-31
    • FlyInNotification mobile small version
    • Bug report answer Collapsible Elements
    • Video Hidden Text Attacks production + title image
    • Thumbs double border improvements
  • 2023-03-29
    • Video Hidden Text Attacks production
  • 2023-03-28
    • Whonix wiki/Linux content fix
    • Pagespeed improvements
      • Headline research
      • Research “Links are not crawlable”
      • Total blocking time research and testing
  • 2023-03-25
    • Donate pages improvements text image design
    • Content fix Whonix Linux installer page
    • Discussion ToDo
    • PayviaPaypal change amount on interval change
    • "Time to Interactive" performance research
    • Software pitch
  • 2023-03-24
    • PayViaPaypal upgrades usability, simple design
    • FlyinNotification upgrades functionality, design, smallery file size
    • Strategy discussion
  • 2023-03-22
    • mwcombine source maps + uglify syntax + documentation
    • Discussion ToDo
    • PayViaPaypal redesign (guardian) + cleanup
  • 2023-03-21
    • Video Kicksecure 001 script
    • Cookie warning bug analysis
    • Pagespeed optimizations
    • mwcombine error output + add source map for custom js
  • 2023-03-15
    • Discussion Todo
    • Image optimization SVG and hero + analysis
    • Improved Whonix Linux installer page
    • Repo web interface research
  • 2023-03-14
    • Instantpage documentation
    • purge extension and fork analysis
    • Donors page thumbnail
    • multipart email thunderbird research
    • Discussion instantpage and multipart email
  • 2023-03-11
    • Discussion Todo
    • mw-combine upgrade feature justcopy + refactoring + documentation
    • DonorCard.css upgrade + DonorTestpage link threshold correction (only s and higher examples)
    • Integration and testing instantpage.js
    • Headscript refactoring
    • Thumbs design fix for gallery thumbs
  • 2023-03-10
    • Design fixed KS Trust page + Whonix HP
    • Discussion ToDo
    • BackToTopButton mobile fadeout
    • Responsive Thumbnails + docu
    • Source map research
  • 2023-03-08
    • Discussion Todo, DonorCard etc
    • Donor cards feature + design upgrade + documentation update
    • Donors and Testpage Donors texts
    • Template intro thumbnail fixes + notpageimage research
    • Content attribution, Design improvements
    • Extension:Popup reference preview research and suggestions
  • 2023-03-07
    • Bugfix PayViaPayPal + upgrade design
    • Research image thumb generation mediawiki
    • Template:intro CSS Firefox fix + upgrade hidden thumbnail thumb parameter + documentation Dev/mediawiki#Intro_paragraph
    • Donors Wiki page related tasks
  • 2023-03-03
    • Bugfix Kicksecure homepage overview-image
    • Bugfix newline bug in HeaderMultiWiki
    • Sitenotice close button upgrade optically and functionally
    • Check image quality
    • PagePreview / TextExtracts bugfix on some pages
    • Template:intro upgrade + documentation
    • Fontawesome preloading
    • Donor Page card design
  • 2023-03-01
    • Banner bigger close + cookie bugfix
    • Discussion CSS optimization and CSS extension
    • Banner rewrite with new method and documentation
    • Multiwiki deploy and testing
  • 2023-02-28
    • Image optimization + metatag Research + new helper program
    • Codeselect upgrade optional img lazy load + docu
    • extension:pagePreviews broken fixes
    • intro template and css upgrade
  • 2023-02-27
    • Discussion ToDo
    • ShareTooltip regexp-bugfix + new mediawiki share logo
    • Textextracts extension research
    • Footer fixing
    • Reduce warnings of w3c validator
    • Banner slim variants
    • short debugging discussion mw-combine error
  • 2023-02-22
    • Bugfix for mobile back button broken
    • Bugfix fors Anchors missing
    • Discussion Todo
    • Fixed Kicksecure Badge svg file
    • Banner dev wanted for Kicksecure was created
    • New banners were uploaded and installed
  • 2023-02-15
    • Creation of 5 banners
    • Discussion donor recognition
  • 2023-02-14
    • MiniModal upgrade all modals close on back button + documentation
    • MwCombineWrapper refactoring
    • Whonix Kicksecure HP minor fixes
    • optimized SVG versions for some logo images
    • coming soon sign
  • 2023-02-13
    • Discussion ToDo
    • PageHomepage
      • Modals share anchors introduced
      • Text can now again be marked and individually copied
      • Highlighting of selected card via url hash + extending hidden areas if needed + open modal if available + back button can be used to return from modal
      • CSS reduction + Firefox fixes
      • MiniModal upgrades + documentation Dev/mediawiki#Mini_Modal
  • 2023-02-06
    • Discussion ToDo
    • CodeSelect highlight language extension variable externalization
    • Minify JS-HTML suggestion
    • mw-combine sanity test and conditional folder creation for src-copy + documentation
    • forums year end banner repair
    • Page editing via header super menu oldid fix
    • Removed nojs.css mentions and updated documentation
    • fonts.css relevance checked and deleted on all wikis
    • multi-wiki-deploy, tests and small bugfixes
  • 2023-02-04
    • CodeSelect Highlight upgrades: less code, better usage, bugfix + documentation
    • Optimization mw-combine: better naming, spacing, formatting, usage
  • 2023-02-03
    • Discussion Todo highlight / prism, discussion strategy
    • Replaced highlight-js with prism-js for CodeSelect + new tests on Testpage + feature target highlight + prevent highlight for CodeSelect icon form for speed optimization
    • Nojs.css deleted and purged from build.json + styles moved to other style files (closer to nojs styles
    • mw-combine improved: folder sanity check, array check for build.json categories
  • 2023-02-02
    • Discussion Todo
    • Research highlight js libs, removed Highligh extension, installation of highlight.js
    • CodeSelect integration of deferred highlight.js + new Feature "lang" to control highlight language or set to auto / none
    • CodeSelect examples were created Testpage1
    • CodeSelect documentation was updated Dev/mediawiki#CodeSelect


  • 2023-01-31
    • Code review for link-to-archive
    • CodeSelect review research + rewrites + new feature "target" + nojs adjustments + template lang research + documentation
  • 2023-01-27
    • push to the mediawiki-extensions-CookieToBodyClass git repository
    • headscript fail open investigation, research, testing
    • New Feature SiteNotice replacement for DismissableSitenotice + documentation Dev/mediawiki#SiteNotice_Donation_Banner
  • 2023-01-26
    • Tor Browser noscript optical bug fix + documentation
    • Hide banners cleanup
    • New Mediawiki Extension CookieToBodyClass + documentation
  • 2023-01-25
    • Header Donate designfix
    • Login image bug and localWiki option concept
    • Reproduce attempt for wide resolution bug
    • Simplify hide_all_banners + documentation
    • Discussion ToDo
    • Whonix outreach communication
    • Kicksecure vector text convert to path
    • About / FAQ mininav unification
    • Mediawiki extension research
  • 2023-01-24
    • Todo discussion
    • Footer QR Modal empty img to JS + Testing
    • Header Refinement images + multiwiki deploy
    • Homepages shaking hands bugfix
    • main mw-combine js defer
    • fontawesome experiments and research
  • 2023-01-23
    • Kicksecure and Whonix homepage and footer image optimization including link rewrites to thumbs, lazy loading async decoding and re-uploads of images which are too small. Also documentation: Dev/website#Images.2C_Files_and_usage_of_thumb and some style upgrades
    • Kicksecure Header mobile bugfix
    • Mobile bars logo for Kicksecure and Whonix headers. Also 4 main images in header given width and height
  • 2023-01-21
    • Installation wiki on local Kicksecure VM
    • Documentation
    • Mediawiki thumb research
  • 2023-01-20
    • Another test and testing with google pagespeed and gtmetrix + documentation
    • Documentation about deferrable js scripts
    • new feature: pageRefToLinks + documentation,
    • Whonix and Kicksecure HP replace background images with images (for good page metrics)
    • multiwiki-deploy and review
  • 2023-01-19
    • Principle research on mediawiki extensions and review of DismissableSitenotice extension
    • Installation local wiki vm und and ssh keygen
    • Scrollindicator desktop fix + documentation
    • loading eager lazy research with admnin
    • Created multiple test cases for loading with google pagespeed under /test
  • 2022-12-28
    • end-of-year donation banner fix
    • broken PayPal donate button investigation
  • 2022-12-22
    • srcset discussion
    • Whonix homepage replace all background images with foreground + give alt attributes
    • Kicksecure homepage last images from background to foreground
    • srcset sizes research
    • full local file CSS JS documentation
  • 2022-12-21
    • Deactivation and replacement of Bootstrap on Kicksecure and Whonix
    • upgrade MiniModal (retain dom events in content, esp. for CodeSelect)
    • Sitenotice exclude from search
    • Duplicate footer fixed
    • Kicksecure homepage head area + no background images + alt attributes
  • 2022-12-20
    • Discussion page speed
    • Search engine bots no index for functional components
    • Kicksecure homepage: logo as svg + overview image preload blur
    • Whonix homepage slogan and call to action + overview image preview blur
    • mediawiki common.js event alternative
  • 2022-12-19
    • Research Blurhash srcset
    • Mediawiki new version CSS and JS fixes: Search + Editor Fullscreen + all pages, nocache cookie, reduced dependencies
    • SVGs for Kicksecure logos
    • Research hiding repetetive text parts from search bots
    • DebugViaUrlModal upgrades
  • 2022-12-09
    • Outreach thank you mail HTML and mail body + send security discussion
  • 2022-12-08
    • Discussion thank you message
    • Research Multipart-Mime Emails Research + Discussion + Technology outline
    • Outreach thank you mail template
  • 2022-12-07
    • Whonix Exposé 100%
    • Outreach communication
    • ShareTooltip Markdown bugfix
    • Thank you message research
  • 2022-12-06
    • Video via nginx discussion
    • research combine CSS/JS or not
    • CSS column bugfix
    • Real World attacks page
    • Whonix Exposé 60%
  • 2022-12-05
    • Prevent Enhance Headlines feature + Template + documentation
    • HTML5 video on demand HLS DASH etc discussion
    • Preloading fonts in Headscript
    • HTML5 video play (speed) bug fix
    • Templates tcc bug examination
    • Page_homepage.css loading discussion
  • 2022-12-02
    • Whonix Youtube channel go live
    • strategy discussion
    • Footer Youtube and Invidious buttons
    • Whonix Homepage Play button
  • 2022-12-01
    • Whonix outreach communication
    • Whonix 003 Video final render
  • 2022-11-30
    • Whonix 003 Video review + improvements + title image
    • Whonix outreach communication
    • deep exif and ffprobe checks for all videos
    • Kicksecure welcome page all resolutions
    • HTML5-Video research
    • Strategy discussion
    • created Bitchute channel
  • 2022-11-29
    • Whonix 003 Video Cut 100%
  • 2022-11-28
    • Tab Controller new Feature nested tabs
    • Outreach artist reviews and communication
    • Elementary IO compare HP search for our own communication improvements
    • Outreach strategy discussion
    • Page speed analysis and improvement suggestions
    • Outreach video pre-production
  • 2022-11-25
    • Odysee and Rumble accounts created
    • Footer improvement discussion
    • ShareTooltip alt attr improvements
    • outreach video script upgrade and discussion
    • Whonix outreach communication
    • Replace vm and host live mode links
    • Analysed Whonix Host page
  • 2022-11-24
    • Bugfix EOY donation banner contentforSlideserror + refactoring + deploy to Kicksecure and Whonix
    • Whonix outreach communication
    • Bugfix: Kicksecure Welcome page long screen bug + Whonix checkup for bug (no problems) + newest version EOY donation banner + close button bugfix
    • Whonix Forum Post count CSS fix
    • Kicksecure + Whonix Donate pages now MultiWiki
    • Share Tooltip Selector Bugfix
  • 2022-11-23
    • Whonix outreach communication
    • Forums End of year banner + onion compatible + tor testing
    • HTML/CSS validate errors fixed (there was a W3C error)
    • Whonix Forum Search bar Support Link via JS
    • Sitenotice Speedup Kicksecure + Whonix + performance test + documentation
    • Dispora link for Whonix footer
    • Whonix Live Mode page 50%
  • 2022-11-22
    • Forums CORS Research together with admin
    • mw-combine now copies the src files to "src-copy" folder too for different use cases
    • Whonix forum: mixed content error research
    • archive link selector bugfix
    • Forum end of year banner 50%
    • wiki end of year banner performance testing
    • Whonix welcome page static HTML end of year banner
    • Wiki End of year banner Page speed-up research
  • 2022-11-18
    • Local Browser HP
      • Play button bugfix
      • Payment-links fix
      • Tor Research solution attempts
      • Fix cookie by using localstorage
      • jquery depedency from debian package
      • Documentation
  • 2022-11-17
    • Mediaviewer CSS fix
    • Preparation Whonix Live page
  • 2022-11-16
    • EndOfYear for local welcome pages 100%
      • deploy to Whonix and Kicksecure
      • Date limit, not shown after 2022-12-31
      • Move whonix local welcome page endofyear library source to kicksecure local welcome page
      • Dismiss close animation
      • documentation Dev/mediawiki#SiteNotice_End_Of_Year_Banner
    • Whonix outreach communication
  • 2022-11-15
    • Whonix outreach communication
    • EndOfYear finalization, smooth fadeIn, customizable title, nojs, deployed to Wikis
    • Changed Whonix forums search text
    • Changed Whonix and Kicksecure navigation
    • EndOfYear for Kicksecure local HP 30%
  • 2022-11-14
    • Whonix Forum Archive symbol fix
    • EndOfYear crypto-adresses, donate-button-mobile, cookie for dismissing, make it param-generic, content shift prevention, tests and preparation to deploy to forums
  • 2022-11-12
    • Grub-live and USB_installation pages improvements
    • EndOfYear Banner 95%
    • PayViaPaypal as jQueryExtention
    • Whonix forums topics mobile design bugfix
    • Donate page panel mobile + learn more
  • 2022-11-11
    • Whonix outreach + donations discussion
    • EndOfYear Banner 30%
  • 2022-11-10
    • Kicksecure Live_Mode page creation 100% done
    • fontsize CSS helper classes + documentation
    • Grub-live page revision 100% done
    • Template:live navigation update and redirects from former VM_Live_Mode and Host_Live_Mode pages
    • Kicksecure USB_Installation page review 100%
  • 2022-11-09
    • Discussion LiveMode and Marketing
    • Kicksecure new Live Mode page 30%
  • 2022-11-08
    • Whonix outreach communication
    • Possible shop research and discussion
    • Kicksecure GUI images
    • Discourse No Jump + Mobile fixes + documentation
    • Live Mode content review
  • 2022-11-07
    • Encrypted Support v1.1 deploy attemps
    • Kicksecure Logo Telegram fix
    • Discourse forums documentation
    • Discourse forums footer + research
  • 2022-11-03
    • Kicksecure Forum new images + new categoris
    • Kicksecure and Whonix forums legal banner
    • Kicksecure and Whonix forums Nojs research and solution
    • Encrypted support v1.1 - 20%
  • 2022-11-02
    • Virtualbox transfer to Whonix
    • Forum improvements for Kicksecure and Whonix
    • new Whonix forum category images
    • Kicksecure logo re-imagining suggestions
  • 2022-11-01
    • Hidden text danger demonstration Nojs fix
    • VirtualBox page improvements
    • Content discussions and improvements
    • VirtualBox/XFCE page improvements
    • General print version improvements of Whonix and Kicksecure
    • mw-combine improvements
    • Newsletter research
    • Whonix outreach voice actor research
  • 2022-10-31
    • Whonix FAQ improvements, analysis of texts and rewrites
  • 2022-10-28
    • Integration of Whonix new tor explainer images
    • Kicksecure Livemode promo image + HP integration
    • Whonix About page improvements
    • LeftRightImage Feature promo style
    • LeftRightImage Feature imagelink + documentation
    • mw-multi-wiki deploy
    • Content and examples for Shell
  • 2022-10-27
    • Kicksecure internal welcome page image attribution
    • skin pref admin documentation
    • hide-all-banners noscript research
    • CodeSelect insert-html-mode feature, see Dev/mediawiki#CodeSelect
    • Whonix new tor explainer images
  • 2022-10-26
    • Kicksecure internal welcome page + CC search
    • set-up of git repositories (especially new dark mode fork)
  • 2022-10-25
    • Dark Mode Firefox and Tor Browser research and suggestions
    • Virtualbox and Whonix testing on Ubuntu
    • Stage Server discussion
    • Git deploy call
    • Dark Mode Extension Fork + documentation Dev/mediawiki#Extension_Dark_Mode_.28Fork.29
  • 2022-10-24
    • Multiwiki/LocalWiki refactoring + documentation
    • EditorMultiwikiNotice new + onion feature + documentation see Dev/mediawiki#EditorMultiwikiNotice
    • Whonix wiki old mw-combine quickfix, later revert to stable
    • Whonix outreach campaign communication
  • 2022-10-23
    • Sitenotice mobile scaling bugfix
    • Multiwiki/LocalWiki refactoring + documentation
  • 2022-10-21
    • ShareToolTip markdown/phpbb anchor upgrades bugfixes testing documentation
    • Custom footer research + overlay fix
    • Footer Randomnews replacement
    • Dark mode button for custom footer
    • CSS fixes for editorautobackup
    • Multiwiki deploy of new features to Whonix and testing
  • 2022-10-20
    • ShareToolTip upgrade + Clipboard options
    • Dark Mode bugfix research + fix
    • Footer overlays important review tools research and solution suggestions
    • Whonix outreach campaign communication
  • 2022-10-13
    • Kicksecure homepage updated like Whonix HP (structure, css, fns, content)
    • added Kicksecure HP Features
    • changed Kicksecure HP cumulative changed metric from 0.24 → 0.02 by predictable image sizes
    • seo images research
  • 2022-10-12
    • ShareTooltip new Sharing Options
    • Whonix HP content shift reduction and speed optimizations
    • Kicksecure HP Features + Upgrade 50%
  • 2022-10-10
    • Review outreach storyboard and corrections
    • new landing page feature cards
    • mw-combine more dontload options
    • landing page pagespeed optimizations
  • 2022-10-09
    • Meeting pagespeed analysis and optimization + documentation
  • 2022-10-08
    • Headline Bug (hidden behind padding)
    • gtmetrix / pagespeed analysis – performance test strategy
    • new image for everything Tor
  • 2022-10-07
    • ShareTooltip upgrade as jQuery Extension
    • CodeSelect upgrade as jQuery Extension
    • Creation EnhanceHeadlines
    • Deployment to Kicksecure and Whonix
    • Testing
    • Documentation
    • Homepage new features cards and images
  • 2022-10-01
    • realization contractor communication, negotiation and clarification
  • 2022-09-30
    • Script 003 outreach improvements and realization contractor research and communication
  • 2022-09-29
    • Script 003 outreach preproduction: storyboard (incl. texts, images, restructuring)
  • 2022-09-28
    • Shortened rewrite Script 003 outreach
    • discussion privacy first mobile operating systems
    • small bugfix leftRightImage
  • 2022-09-23
    • Script 003 outreach
    • Whonix installation and virtualbox testing
    • documentation
  • 2022-09-22
    • ShareTooltip further upgrades and finalization
    • user group promo texts and images collage
  • 2022-09-21
    • outreach artwork finalization
    • ShareTooltip, bugfix, documentation and deployment
  • 2022-09-20
    • ShareTooltip upgrades and revisions
    • outreach artwork reviews
  • 2022-09-19
    • Introduction of ShareTooltip component
    • work on social media strategy
  • 2022-09-16
    • User Groups concept images
    • coordination with artist
    • Homepage new image Linux account separation research
    • Homepage tooltip upgrade
    • Homepage link symbol repositioning
  • 2022-09-13
    • Homepage clickable boxes logos
    • Homepage apps Section alignment
    • improved intro paragraph
  • 2022-09-12
    • Download page optimization
    • video content script and review
    • new feature Left-Right Image Text
  • 2022-09-09
    • video content script
    • video content banner
  • 2022-09-08
    • video content logo, setup, texts
  • 2022-09-07
    • bugfix Modal Search
    • bugfix EditorSave
    • video content production
  • 2022-09-06
    • new promo images
    • MiniModal vertical cut fix
    • video content production
  • 2022-09-02
    • Homepage fixes
    • new promo images
  • 2022-09-01
    • Homepage content review
    • new promo images
    • improved modals
    • mobile fix for section press
  • 2022-08-30
    • Improved Whonix Homepage
    • Improved images
    • Improved Whonix Main_Page
  • 2022-08-29
    • new tool Icon-Bullet-List widget, CSS and documentation
    • new CSS feature Color Schemes + documentation
    • new feature vspacer
    • improved Download Button onion link
    • Fixed hidden banner issue
  • 2022-08-25
    • Whonix content production
  • 2022-08-24
    • Whonix content production
    • table icon improvements: Whonix comparison with VPNs
  • 2022-08-23
    • New tool: info-tooltip
    • added new nojs-classes
    • new Mediawiki:Pages.js
    • table improvements: Whonix comparison with VPNs
  • 2022-08-22
    • Whonix webpage improvement, table Whonix comparison with VPNs
  • 2022-08-20
    • Whonix content production
  • 2022-08-18
    • Whonix content production
  • 2022-08-17
    • Content Review
    • improved
    • Mininav upgrade for external links
    • reverted Download-Button back to widget
    • converted Responsive Thumbnail into template
    • created intro paragraph design class
  • 2022-08-16
    • Content Review
  • 2022-08-15
    • CSS and JS validation and review with linters
    • reviewed and changed mobile.js
    • improved hide-enlarge
  • 2022-08-05
    • Improvement on Whonix Homepage
  • 2022-08-04
    • Javascript Dom Timing bug research
    • Mediawiki Newline Bug research and report
  • 2022-08-03
    • Improved mw-combine allow comments in build.js and docu
    • changed from Widget to Template Download-button
    • Kicksecure HP mobile fixes
    • TOC level switcher upgrade
    • MediaWiki newline bug research
    • small Headscript content upgrades
  • 2022-08-02
    • Fix Sitenotice only visible on pages with localSkin
    • small Homepage fix
    • Thumbnails fix
    • Deploy Fixing
    • CSS Refactoring
    • Headscript content upgraded
  • 2022-08-01
    • HeadScript Upgrade nojs.css
    • headscript-upgrade nojs.css
    • Template Header minified
    • CSS Extension review
    • Kicksecure Footer fix
    • Documentation of new include concept
  • 2022-07-30
    • HeadScript Upgrade mw-autogen
    • mw-combine.php
    • headscript-content.php
    • refactored existing JS files
  • 2022-07-29
    • Javascript research and development of new include concept with autogenerated JS and CSS
  • 2022-07-25
    • MultiWiki refactoring
    • info-box improvement thumbs
  • 2022-07-22
    • Fix Vector 22 search mobile
    • MultiWiki Restructure plan and Doc
    • MiniModal Navi Fix
    • EditorAutoBackup V2 plan
  • 2022-07-21
    • Docu Flagged Revisions
    • Research, analysis, docu for skins
    • Fix search for Vector 2022 skin
    • Fix burger menu for Vector 2022 skin
  • 2022-07-18
    • restructuring of Dev/mediawiki finalization
    • new module MiniModal
    • new module EditorAutoBackup
  • 2022-07-16
    • Research regarding wgCanonicalNamespace
    • restructuring of Dev/mediawiki
  • 2022-07-15
    • Whonix BIMI Logo SVG fix
    • FlyInNotification converted to MultiWiki
    • General MultiWiki conversion
  • 2022-07-13
    • Continued and finished work on Homepage.
  • 2022-07-12
    • og:image on all pages
    • image for chroot
    • fixed Kicksecure Text Logo
    • improved Download, Donate
    • Kicksecure BIMI Logo SVG created
    • improved Header and Header Menu
    • created Homepage and style first and second section
  • 2022-03-23
    • Tried to separate data of Mediawiki:FlyInNotification.js into separate JSON file. Failed because of insufficient Mediawiki Javascript content and data access API
  • 2022-03-19
    • Kicksecure new logo finalization
    • data export to Kicksecure
  • 2022-03-18
    • Kicksecure logo new design
  • 2022-03-17
    • Welcome page finalization
    • new improved version of Whonix concept image
  • 2022-03-16
    • Redesign Welcome page part 1
    • FlyInNotification improvements
    • Upgrade of Template:Box
  • 2022-03-15
    • FlyInNotification finalization
    • predictable column break classes für 3-column areas
  • 2022-03-10
    • creation of module FlyInNotification
  • 2022-03-09
    • Redesign of Homepage amendments
  • 2022-03-07
    • Redesign of Homepage finalization and made responsive
  • 2022-03-05
    • Redesign of Homepage part 2
  • 2022-03-04
    • Redesign of Homepage part 1
  • 2022-03-03
    • DownloadButton now responsive
    • NoJS version of ExpandAll
    • Mobile scrollbars
  • 2022-02-26
  • 2022-02-24
    • images (.thumb, .thumbinner) made responsive, examples see Warning
    • Donation panel, mininav, EUR page improvements
    • Download_Button redirect feature
  • 2022-02-23
    • Improved donation panel: Payment links, design
    • Improved our Extension:CSS fork, alternative inclusion method for local CSS
    • further new Vector skin fixes: min-width
  • 2022-02-22
    • new Vector skin activated, resulting problems fixed
    • 10 year banner: close improved, scaling for mobile
  • 2022-02-21
    • 10 year banner created
    • SiteNotice improvements and fixes
    • Php Notice Undefined Index fixes
  • 2022-02-11
    • donation panel Nojs solution
    • donation panel realization and images for other payments
  • 2022-02-10
    • improved FullScreenEditor for CodeMirror
    • improved donation panel
  • 2022-02-08
    • donation panel crypto section finished
    • donation panel paypal section design finished
  • 2022-02-07
    • development start of donation panel
    • creation of original QR logo
  • 2022-02-05
    • improved Header overlap: no found occurrences anymore. Plus documentation: Dev/mediawiki#Fixed_Header_Overlap_for_anchors
    • improved Mininav style when item stack and for smaller displays
    • research and documentation about DismissableSitenotice
    • research and documentation about GDPR CookieWarning
  • 2022-02-04
    • SiteNotices beautified, enhanced via JS and documented
    • Footnotes Newline in the normal html way again, <br> for newline
    • BackToTopButton documentation
    • Mediawiki notifications (e. g. "Your edit was saved") beautified for whonix theme and placed visibly below header
  • 2022-02-03
    • SaveAndContinue-Button: Modal improvement
    • Back to Top Button introduced
    • Rejected: Scrollable Table Bugfix - this is a result of the table being hidden in an invisible element, so not a bug. If the table is hidden is has no dimension and so it cannot "know" if its content is oversize
    • Footnotes always respect newlines setting and discussion (later reverted)
    • Widget:Download_Button: responsive for small displays (under 450px)
  • 2022-02-02
    • mini navigation (buttons on top of some pages) visually enhanced
    • wiki edit preview our-footer overlaps save bar bugfix
    • Archive_link: explained wrong "|onion={{QubesOS_onion}}" vs correct use "|onion=http://{{QubesOS_onion}}"
  • 2022-01-31
    • RandomNews for footer shortened and improved
    • TOC hide/show improved
  • 2022-01-20
    • tables oversize solution introduced, also for mobile swipe indicator for oversize
    • Download Page, supported icons improved
  • 2022-01-19
    • improvements for mediawiki search
    • new mono font introduced
    • pre alternative for special cases introduced
    • table of contents jump paddings corrected
  • 2022-01-18
    • improved styles for tables, lists, blockquotes, pre, code etc
  • 2022-01-17
    • codeSelect Bugfixes and style improvements
  • 2022-01-15
    • Development of Extension:CSS fork with new functionality
    • Header improved for JS users
  • 2022-01-14
    • Header overlapping jump targets fixed
    • Vector Skin remove external link symbols
    • Editor Fullscreen Feature for editor added
    • Header made responsive down to 370px and optimized for mobile usability
    • CodeSelect Nojs style fix + new parameter inline so multiple instances can be combined in one line --target virtualbox , --target qcow2 , and --target raw
  • 2022-01-13: Completely new Header developed and installed
    • Header is inserted as a Template and fixed to top
    • Header features like the header form 2022-01-09
    • Completely Nojs and Mobile friendly
  • 2022-01-11: SaveAndContinue-Button: New JS-Feature for faster Development
  • 2022-01-10: Creation of BodyScript2 Mediawiki Extension
  • 2022-01-09: New Header developed
    • Restructuring via Sidebar
    • unifying all menus in one supermenu
    • replacement of donate button
    • Main Logo links to
    • nice hover effects
    • Search in modal instead of box (for js users, else go to search page)
  • 2022-01-08: Nojs.css incorporated - styles exclusively for Nojs visitors
  • 2022-01-06: New footer incorporated
    • new Style, better layout and ordering
    • Bootstrap modals for content
    • engaging action buttons
    • Integration of whonix news
  • 2022-01-03: Crypto address templates unified and Crypto address images unified
  • 2021-12-31: Footer RandomNews. Solution: RandomNews template was not available in Footer2 widget (because: widget), so RandomNews was called in Footer2-Template. In template it is hidden by CSS and the whonix random news section in footer is filled with generic text. If JS is available RandomNews are moved to Footer (true HTML widget area)
  • 2021-12-31: CodeSelect Improvements, Refinements #3. Green color and check mark if copy is clicked
  • 2021-12-30: CodeSelect Improvements
    • after clicking the copy symbol, the copy symbol changes into a green checkmark, later changes back
    • CodeSelect can be called as a template but also simply by
      <div class="code-select">code</div>
      - essential for usage in Widgets
  • 2021-12-29: Footer subdomain fixes by protocol and apex domain for forums subdomain ( and .onion)
  • 2021-12-28: Footer redesigned
  • 2021-12-23: CodeSelect further improved: less white space, more compact, better nojs-version, better js-animation
  • 2021-12-23: Combi task: External Links / Template + Widget Archive-Link
    • Improved Mediawiki Extension "Link to archive"
      • differentiate automatically between normal link, onion-link and link to
      • Show logos instead of long "[archive]" text
      • logo / title attribute / logo link href according to linked url: normal → archive symbol + archive link / onion → onion logo and onion link / archive link → archive logo and same link
    • Template Template:Archive_link and Widget:Archive_link and MediaWiki:Archive Link.css created: Similar to "Link to archive", but you can choose if you want an archive link, onion link or both
  • 2021-12-21: Whonix Logo Format: discussed: jpeg and png specific use cases. And logo-text and logo delivered without padding
  • 2021-12-21: Whonix Logo finished
  • 2021-12-20: mediawiki skin selection
    • Whonix? -> Keeping mediawiki skin Foreground and adding CSS fixes later.
    • Kicksecure: Which skin should be used as foundation? -> Same but with different CSS to have distinctive styles/colors.
  • 2021-12-19: Colored Platform Icons, 500px*500px
    • some icons pulled from web in better solution
    • apple logo rights research. Seems using the logo is in most of the world public domain and in copyrighted jurisdictions logo is considered fair use and used by open source projects (means no licence)
    • kvm logo complete redesign
    • review/improve colored symbols for Template:Supported_Platforms_Icons since these are used on Download and homepage
  • 2021-12-18: Whonix old logo refinement, old text removed, text "Whonix" redrawn
  • 2021-12-17: CodeSelect finished
    • HTML restructured, Style improved
    • direct copy button added, info tooltip added
    • modernized und documented JS mechanic
    • improved upon old mechanic with sidescrolling
    • Non-JS compatible with similar style
  • 2021-12-16: Update Download Button VirtualBox wiki page Download Button: prettify and easier functionality
  • 2021-12-14: invoice template improvements
  • 2021-12-13: discuss (easy, not important): cannot click inspect on other websites


Unfinished: This wiki is a work in progress. Please do not report broken links until this notice is removed, use Search Engines First and contribute improving this wiki.