TODO - Revision history

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 )

CRYSTL: added motivation info , and clarified that roles are specific to teams

2026-05-03T19:47:45Z

added motivation info , and clarified that roles are specific to teams

← Older revision		Revision as of 19:47, 3 May 2026
Line 30:		Line 30:
	* Templates		* Templates
	** user profile information template (need to flesh out how this will look)		** 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 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.		**** Roles are now defined through [[Template:Add role]] and [[Template:User roles]] in a user page.
	*** a description of their skills and interests		*** a description of their skills and interests

CRYSTL: added link to LUKS page , removed old cryptpad page .

2026-05-03T19:25:29Z

added link to LUKS page , removed old cryptpad page .

← Older revision		Revision as of 19:25, 3 May 2026
Line 7:		Line 7:
	** [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>]
	* 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
	** ~~https://cryptpad.fr/pad/#/2/pad/view/v9+28PcpFVoMr4eVf-NpF64Do35ocDL3tQLbaWq2Bfk/~~		**[[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.

CRYSTL: completed table of contents ( MediaWiki:Sidebar )

2026-05-03T19:20:41Z

completed table of contents ( MediaWiki:Sidebar )

← Older revision		Revision as of 19:20, 3 May 2026
Line 18:		Line 18:
	*** 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
	* 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
	** maybe also a table of contents or something?
	** 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
	*** from what i can remember offhand, usually the home page has some links to more specific topics, which then link out to other articles		*** from what i can remember offhand, usually the home page has some links to more specific topics, which then link out to other articles

CRYSTL: remove document > guidance TODO

2026-05-03T18:06:24Z

remove document > guidance TODO

← Older revision		Revision as of 18:06, 3 May 2026
Line 24:		Line 24:
	** we could also figure out if we want to have a more "document" focused theme for desktop like maybe [[mediawikiwiki:BlueSpice\|BlueSpice]]		** we could also figure out if we want to have a more "document" focused theme for desktop like maybe [[mediawikiwiki:BlueSpice\|BlueSpice]]
	*** if we have something less functional than [[mediawikiwiki:BlueSpice\|BlueSpice]] though, we'll want to explain in the guide how to change the default user theme if someone is interested in doing editing		*** if we have something less functional than [[mediawikiwiki:BlueSpice\|BlueSpice]] though, we'll want to explain in the guide how to change the default user theme if someone is interested in doing editing
	** consider whether guide or documentation is a better word to use
	*** probably i ended up choosing documentation because R&D ( research and documentation ) was kinda cool but TBH it's also a bit confusing, so guides are probably better
	** how to use tables		** how to use tables
	** how to use templates		** how to use templates

VV at 17:42, 3 May 2026

2026-05-03T17:42:06Z

← Older revision		Revision as of 17:42, 3 May 2026
Line 34:		Line 34:
	** user profile information template (need to flesh out how this will look)		** user profile information template (need to flesh out how this will look)
	*** should have matrix account		*** should have matrix account
	*** should describe teams they are in and what roles they want to play		*** should describe teams they are in and <s>what roles they want to play</s>
			**** Roles are now defined through [[Template:Add role]] and [[Template:User roles]] in a user page.
	*** a description of their skills and interests		*** a description of their skills and interests
	*** DRAFT : [[User:Everlastingred]]		*** DRAFT : [[User:Everlastingred]]