TODO - Revision history

VV: /* In Progress Pages : */ oops

2026-07-01T01:12:57Z

In Progress Pages :: oops

← Older revision		Revision as of 01:12, 1 July 2026
Line 20:		Line 20:
	* 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]]
	**[[Linux anatomy]]		**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 30:		Line 29:
	**** 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 ==

VV: /* In Progress Pages : */ added Linux Anatomy

2026-07-01T01:12:08Z

In Progress Pages :: added Linux Anatomy

← Older revision		Revision as of 01:12, 1 July 2026
Line 20:		Line 20:
	* 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]]
			**[[Linux anatomy]]
	** 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.

VV: /* Needs Research / Implementation */ Update on the status of the Guide template

2026-06-17T02:27:37Z

Needs Research / Implementation: Update on the status of the Guide template

← Older revision		Revision as of 02:27, 17 June 2026
Line 55:		Line 55:
	** "this page is a placeholder"		** "this page is a placeholder"
	** "this page is an accessory to another?" (maybe see or see also cover this, IDK)		** "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 "		** tiered information.
	*** something like :		*** 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.
	**** beginner : only talk about installing software via easy methods on a device with its pre-installed OS		*** 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 "
	**** novice : willing to try safer OSes like linux		**** something like :
	**** intermediate : can use a command line shell for simple things , and can edit config files		***** beginner : only talk about installing software via easy methods on a device with its pre-installed OS
	**** advanced : can write simple scripts and programs and knows their way around a CLI		***** novice : willing to try safer OSes like linux
	**** expert : able to understand with low-level concepts like memory management and CPU instructions		***** intermediate : can use a command line shell for simple things , and can edit config files
	*** 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		***** advanced : can write simple scripts and programs and knows their way around a CLI
	**** will try to figure some of this out when working on LUKS		***** 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 :		* 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 )

VV: /* Needs Research / Implementation */ remove TODO about draft as it is completed.

2026-06-16T23:49:11Z

Needs Research / Implementation: remove TODO about draft as it is completed.

← Older revision		Revision as of 23:49, 16 June 2026
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
	** ~~"this page is not yet completed" / "this page is a draft?" ( would be nice to have a directory~~ of all unfinished pages ~~as well~~ )		** Directory of all unfinished pages (pages which include the Draft template)
	** "this page is a placeholder"		** "this page is a placeholder"
	** "this page is an accessory to another?" (maybe see or see also cover this, IDK)		** "this page is an accessory to another?" (maybe see or see also cover this, IDK)

CRYSTL: add link to wantedpages

2026-06-16T23:34:11Z

add link to wantedpages

← Older revision		Revision as of 23:34, 16 June 2026
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\|this list]] and see if there's anything you're interested in writing about!

	== Easy first project : ==		== Easy first project : ==

CRYSTL at 00:31, 27 May 2026

2026-05-27T00:31:02Z

← Older revision		Revision as of 00:31, 27 May 2026
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.

			== Easy first project : ==

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

	* mpeg container format		* mpeg container format
Line 10:		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/$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>]		** [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		* Finish LUKS guide , and probably split it up into simpler and more advanced guides
	**[[LUKS]]		**[[LUKS]]
Line 21:		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 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

			== Needs Research / Implementation ==
	* A guide on how to use and navigate around the WIKI would be a very good idea		* 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		** TBH I'm not entirely sure how wikis are usually structured, maybe something to look into
Line 30:		Line 38:
	** how to use templates		** how to use templates
	** how to use the WYSIWYG editor		** how to use the WYSIWYG editor

	* Braille / TTS support on linux		* Braille / TTS support on linux
	** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$YQue0cGGqU5KXtuNEOPpbZUl_-M25V1fj46S8kJA2q0?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Matrix] reference</nowiki>]		** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$YQue0cGGqU5KXtuNEOPpbZUl_-M25V1fj46S8kJA2q0?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Matrix] reference</nowiki>]
Line 49:		Line 58:
	**** 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

Moonbeanz: media playback

2026-05-27T00:21:49Z

media playback

← Older revision		Revision as of 00:21, 27 May 2026
Line 2:		Line 2:

	* mpeg container format		* 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.		* Write a page describing how matrix works, how it relates to FASSAG, and some client quirks to be aware of.

Moonbeanz: mpeg container format

2026-05-27T00:10:25Z

mpeg container format

← Older revision		Revision as of 00:10, 27 May 2026
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.

			* mpeg container format

	* Write a page describing how matrix works, how it relates to FASSAG, and some client quirks to be aware of.		* Write a page describing how matrix works, how it relates to FASSAG, and some client quirks to be aware of.

CRYSTL: added notes for tiers

2026-05-10T18:11:31Z

added notes for tiers

← Older revision		Revision as of 18:11, 10 May 2026
Line 40:		Line 40:
	** "this page is a placeholder"		** "this page is a placeholder"
	** "this page is an accessory to another?" (maybe see or see also cover this, IDK)		** "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 :		* 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 )

CRYSTL: added unfinished pages sections

2026-05-03T20:38:12Z

added unfinished pages sections

← Older revision		Revision as of 20:38, 3 May 2026
Line 37:		Line 37:
	*** 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
	** "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 a placeholder"
	** "this page is an accessory to another?" (maybe see or see also cover this, IDK)		** "this page is an accessory to another?" (maybe see or see also cover this, IDK)
			* Unfinished pages :
			** [[LUKS]]
			** [[Lens]]
			** ( the rest of the roles pages have not even been started )