TODO

This page is a list of projects currently being worked on and references to relevant information.

Please check this list and see if there's anything you're interested in writing about! Also, check out Drafts to see existing pages that are not yet completed.

Easy first project :

• mpeg container format
  • h264
• hardware accelerated media playback

• Write a page describing how matrix works, how it relates to FASSAG, and some client quirks to be aware of.
  • Maybe these should be separate pages?
  • [Thread] consider having a dedicated page to matrix
  • [Thread] the matrix.to page is apparently just broken ,,, the icon is just not viewable .
  • [Thread] Yeah so it commet receives a thread reply, it inserts the thread parent into the thread body instead of the new thread reply message

In Progress Pages :

• The Drafts page lists all pages that use Template:Draft, and so it's a good place to start if you're looking for work to do.
• Finish LUKS guide , and probably split it up into simpler and more advanced guides
  • LUKS
  • NOTES:
    • for a bit of context as to why i wanted to write this in the first place, someone asked me "if i want the best security, how do i setup a LUKS partition?" and based on that question, I assume that just telling them "the defaults are fine" would not be a particularly satisfying answer. so i did my best to research everything, and tried to compile an exhaustive list of reasons why the defaults are OK. i went in assuming that there might be like, some algorithm that has a very strong performance cost for better security, but ultimately concluded, that wasn't really the case . but like , only after trying to understand everything.
    • "a good amount of this information is pulled from [link]" by itself sounds kinda weird, like why should someone read your post instead of just going to that link immediately? perhaps "The [cryptsetup FAQ](...) is a great in-depth resource on all the available security options, but it's pretty long and complex. This post will cover the basics so you can get set up quickly with a reasonably secure system."
    • if your system is starved of entropy, one technique I've seen is to use random.org , e.g. curl -Ss https://www.random.org/cgi-bin/randbyte?nbytes=16384&format=f > /dev/random
      • then you should be able to run any programs that would block on /dev/random
    • you should define what "post quantum resistant" means if you're going to mention it, IMO
    • ZFS actually uses an authenticated encryption mode by default (AES-GCM) which is how it can detect tampering. i think this is what you meant, but saying "XTS vulnerabilities can be mitigated with ZFS or BTRFS"  is a little less clear than "XTS has vulnerabilities under certain threat models, such as A, B and C [IMO if you're going to mention this you should also explain what the vulnerabilities are, you can't just drop this with no context]. If you are concerned about these issues, you should use an authenticated encryption mode like AES-GCM, which is unfortunately not available with LUKS due to the additional space needed for the authentication tags, but can be accomplished with a supporting filesystem such as ZFS."
      • i don't remember where i read that "ZFS and BTRFS will help with the corruption issues of XTS" they may not have even been talking about LUKS directly and i just got confused (it was probably Wikipedia)
    • i guess to expand on this, if you have a good idea of what your target audience is then you should be evaluating everything in the post from that point of view. suppose you are a beginner who doesn't know anything about crypto. "XTS has vulnerabilities" and "AES-256 is post quantum" are meaningless to u without further context. maybe the context for those things isn't the point of the post, but in that case u could maybe link to further resources or have some further explanation in footnotes
• Linux anatomy

Needs Research / Implementation

• A guide on how to use and navigate around the WIKI would be a very good idea
  • TBH I'm not entirely sure how wikis are usually structured, maybe something to look into
    • from what i can remember offhand, usually the home page has some links to more specific topics, which then link out to other articles
      • probably there *shouldn't* be an orphaned articles
  • we could also figure out if we want to have a more "document" focused theme for desktop like maybe BlueSpice
    • if we have something less functional than BlueSpice though, we'll want to explain in the guide how to change the default user theme if someone is interested in doing editing
  • how to use tables
  • how to use templates
  • how to use the WYSIWYG editor

• Braille / TTS support on linux
  • [Matrix] reference
• Templates
  • user profile information template (need to flesh out how this will look)
    • should have information about how they are best motivated
    • should have matrix account
    • should describe teams they are in and what roles they want to play in those teams
      • Roles are now defined through Template:Add role and Template:User roles in a user page.
    • a description of their skills and interests
    • DRAFT : User:Everlastingred
  • TODO item template? probably to gather information from relevant pages but some TODOs will likely not have a page? dunno, something to think about
  • "this page is a placeholder"
  • "this page is an accessory to another?" (maybe see or see also cover this, IDK)
  • tiered information.
    • We are now using Template:Guide and sub-pages (use 'SomeGuide/advanced' etc with a slash) to determine a guide's tier and link to other tiers of the same guide.
    • a graph of the different tiers of depth on the main page may also be a good idea ? probably should also try to figure out some ground rules about what kind of content is even suitable for which tier , how many tiers there should be , etc . for example , on the LUKS page , since that is assuming like , someone is installing linux , that's already like , above the base tier imo , which is just like " the OS that came on your computer "
      • something like :
        • beginner : only talk about installing software via easy methods on a device with its pre-installed OS
        • novice : willing to try safer OSes like linux
        • intermediate : can use a command line shell for simple things , and can edit config files
        • advanced : can write simple scripts and programs and knows their way around a CLI
        • expert : able to understand with low-level concepts like memory management and CPU instructions
      • though this might be too many ? or not enough , i dunno . i guess it would depend on the amount of content we have to talk about for any given subject
        • will try to figure some of this out when working on LUKS
• Unfinished pages :
  • LUKS
  • Lens
  • ( the rest of the roles pages have not even been started )