TODO: Difference between revisions

(7 intermediate revisions by 2 users not shown)

Line 1:

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

== Easy first project : ==

* write about the distinction between distro / kernel / init / userspace / DE / windowing system / compositor / package manager

* 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.

Line 6:

Line 14:

** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$B46BEaqrLtxuJ5BvQt_z8qzDZD4VIq2grk2MS1R6F_I?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Thread] the matrix.to page is apparently just broken ,,, the icon is just not viewable .</nowiki>]

** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$-TvpInGLsJ_8wHilOnuKDYtP8D9T4C5DJIMQRsiAf_U?via=chat.solarpunk.moe&via=matrix.org <nowiki>[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</nowiki>]

== In Progress Pages : ==

* Finish LUKS guide , and probably split it up into simpler and more advanced guides

** ~~https://cryptpad.fr/pad/#/2/pad/view/v9+28PcpFVoMr4eVf-NpF64Do35ocDL3tQLbaWq2Bfk/~~

**[[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.

Line 17:

Line 27:

**** 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

== Needs Research / Implementation ==

* A guide on how to use and navigate around the WIKI would be a very good idea

** maybe also a table of contents or something?

** 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

Line 27:

Line 38:

** how to use templates

** how to use the WYSIWYG editor

* Braille / TTS support on linux

** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$YQue0cGGqU5KXtuNEOPpbZUl_-M25V1fj46S8kJA2q0?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Matrix] reference</nowiki>]

* 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 <s>what roles they want to play</s>

*** should describe teams they are in and <s>what roles they want to play in those teams</s>

**** 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 not yet completed" / "this page is a draft?"

** "this page is not yet completed" / "this page is a draft?" ( would be nice to have a directory of all unfinished pages as well )

** "this page is a placeholder"

** "this page is an accessory to another?" (maybe see or see also cover this, IDK)

** tiered information ? as in , there will be a main page which gives a high level overview , and links to pages with more detail , and those pages would need a template to link back to the main page ? or perhaps the " See also " template would be enough , dunno . 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 )

@@ Line 1: / Line 1: @@
 This page is a list of projects currently being worked on and references to relevant information.
+== Easy first project : ==
+* write about the distinction between distro / kernel / init / userspace / DE / windowing system / compositor / package manager
+* 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.
@@ Line 6: / Line 14: @@
 ** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$B46BEaqrLtxuJ5BvQt_z8qzDZD4VIq2grk2MS1R6F_I?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Thread] the matrix.to page is apparently just broken ,,, the icon is just not viewable .</nowiki>]
 ** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$-TvpInGLsJ_8wHilOnuKDYtP8D9T4C5DJIMQRsiAf_U?via=chat.solarpunk.moe&via=matrix.org <nowiki>[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</nowiki>]
+== In Progress Pages : ==
 * Finish LUKS guide , and probably split it up into simpler and more advanced guides
-** https://cryptpad.fr/pad/#/2/pad/view/v9+28PcpFVoMr4eVf-NpF64Do35ocDL3tQLbaWq2Bfk/
+**[[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.
@@ Line 17: / Line 27: @@
 **** 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
+== Needs Research / Implementation ==
 * A guide on how to use and navigate around the WIKI would be a very good idea
-** maybe also a table of contents or something?
 ** 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
@@ Line 27: / Line 38: @@
 ** how to use templates
 ** how to use the WYSIWYG editor
 * Braille / TTS support on linux
 ** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$YQue0cGGqU5KXtuNEOPpbZUl_-M25V1fj46S8kJA2q0?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Matrix] reference</nowiki>]
 * 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 <s>what roles they want to play</s>
+*** should describe teams they are in and <s>what roles they want to play in those teams</s>
 **** 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 not yet completed" / "this page is a draft?"
+** "this page is not yet completed" / "this page is a draft?" ( would be nice to have a directory of all unfinished pages as well )
 ** "this page is a placeholder"
 ** "this page is an accessory to another?" (maybe see or see also cover this, IDK)
+** tiered information ? as in , there will be a main page which gives a high level overview , and links to pages with more detail , and those pages would need a template to link back to the main page ? or perhaps the " See also " template would be enough , dunno . 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 )