TODO: Difference between revisions
add link to wantedpages |
Removed some completed requested templates |
||
| (9 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This page is a list of projects currently being worked on and references to relevant information. | This page is a list of projects currently being worked on and references to relevant information. | ||
Please check [[Special:WantedPages| | Please check our list of [[Special:WantedPages|Wanted Pages]] 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 : == | == Easy first project : == | ||
* mpeg container format | * mpeg container format | ||
| Line 18: | Line 16: | ||
== In Progress Pages : == | == 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 | * Finish LUKS guide , and probably split it up into simpler and more advanced guides | ||
**[[LUKS]] | **[[LUKS]] | ||
** NOTES: | **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. | *** 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." | *** "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." | ||
| Line 29: | Line 28: | ||
**** 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 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 | *** 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 == | == Needs Research / Implementation == | ||
| Line 52: | Line 52: | ||
*** DRAFT : [[User:Everlastingred]] | *** 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 | ** TODO item template? probably to gather information from relevant pages but some TODOs will likely not have a page? dunno, something to think about | ||
** | ** 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 : | |||
*** something like : | ***** beginner : only talk about installing software via easy methods on a device with its pre-installed OS | ||
**** 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 | ||
**** novice : willing to try safer OSes like linux | ***** intermediate : can use a command line shell for simple things , and can edit config files | ||
**** 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 | ||
**** 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 | ||
**** 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 | ||
*** 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 | ||
**** will try to figure some of this out when working on LUKS | |||
* Unfinished pages : | * Unfinished pages : | ||
** [[LUKS]] | ** [[LUKS]] | ||
** [[Lens]] | ** [[Lens]] | ||
** ( the rest of the roles pages have not even been started ) | ** ( the rest of the roles pages have not even been started ) | ||