FASSAG Wiki - User contributions [en]

User:VV

2026-04-19T20:07:23Z

CRYSTL:

'''This page has been vandalized 1 times.''' ''You can help by vandalizing it.''

ඞ

TODO

2026-04-19T19:41:07Z

CRYSTL:

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

* 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?
** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$9flQpMULrrZ9q3sM1CIKtDdwpHCC_YFOCDbXeAevn7M?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Thread] consider having a dedicated page to matrix</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>]
* Finish LUKS guide , and probably split it up into simpler and more advanced guides
** https://cryptpad.fr/pad/#/2/pad/view/v9+28PcpFVoMr4eVf-NpF64Do35ocDL3tQLbaWq2Bfk/
** 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. <code>curl -Ss <nowiki>https://www.random.org/cgi-bin/randbyte?nbytes=16384&format=f</nowiki> > /dev/random</code>
**** 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
* 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
**** 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 [[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
** 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 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 matrix account
*** should describe teams they are in and what roles they want to play
*** 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 a placeholder"
** "this page is an accessory to another?" (maybe see or see also cover this, IDK)

User:Everlastingred

2026-04-19T19:31:08Z

CRYSTL:

== About Me ==
{| class="wikitable"
|+
! colspan="2" |Contact
|-
|Matrix
|@everlastingred:chat.solarpunk.moe
|-
!Teams
!Roles
|-
|Super Spahgetti Squadron
|Head Osaka Kasuga image procurer
|-
|MTF Gamma-5 (“Red Herrings”)
|Moral Support girlie
|}

== Skills and Interests ==

=== Skills: ===

* Programming
* Pro Gramming

=== Interests: ===

* Osaka
* Gaming

TODO

2026-04-19T18:43:19Z

CRYSTL: added braille / TTS section

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

* 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?
** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$9flQpMULrrZ9q3sM1CIKtDdwpHCC_YFOCDbXeAevn7M?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Thread] consider having a dedicated page to matrix</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>]
* Finish LUKS guide , and probably split it up into simpler and more advanced guides
** https://cryptpad.fr/pad/#/2/pad/view/v9+28PcpFVoMr4eVf-NpF64Do35ocDL3tQLbaWq2Bfk/
** 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. <code>curl -Ss <nowiki>https://www.random.org/cgi-bin/randbyte?nbytes=16384&format=f</nowiki> > /dev/random</code>
**** 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
* 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
**** 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 [[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
** 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
* 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 matrix account
*** should describe teams they are in and what roles they want to play
*** a description of their skills and interests
** 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 a placeholder"
** "this page is an accessory to another?" (maybe see or see also cover this, IDK)

TODO

2026-04-19T18:40:24Z

CRYSTL: formatting and such

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

* 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?
** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$9flQpMULrrZ9q3sM1CIKtDdwpHCC_YFOCDbXeAevn7M?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Thread] consider having a dedicated page to matrix</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>]
* Finish LUKS guide , and probably split it up into simpler and more advanced guides
** https://cryptpad.fr/pad/#/2/pad/view/v9+28PcpFVoMr4eVf-NpF64Do35ocDL3tQLbaWq2Bfk/
** 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. <code>curl -Ss <nowiki>https://www.random.org/cgi-bin/randbyte?nbytes=16384&format=f</nowiki> > /dev/random</code>
**** 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
* 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
**** 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 [[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
* 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
*
* Templates
** user profile information template (need to flesh out how this will look)
*** should have matrix account
*** should describe teams they are in and what roles they want to play
*** a description of their skills and interests
** 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 a placeholder"
** "this page is an accessory to another?" (maybe see or see also cover this, IDK)

TODO

2026-04-19T18:25:42Z

CRYSTL: add more notes to the LUKS article

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

* 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?
** [https://matrix.to/#/!dkSMcP-EtUFhf2SZZR4nwSHGI0RVq1Sr2p-zguVoLNI/$9flQpMULrrZ9q3sM1CIKtDdwpHCC_YFOCDbXeAevn7M?via=chat.solarpunk.moe&via=matrix.org <nowiki>[Thread] consider having a dedicated page to matrix</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>]
* Finish LUKS guide , and probably split it up into simpler and more advanced guides
** https://cryptpad.fr/pad/#/2/pad/view/v9+28PcpFVoMr4eVf-NpF64Do35ocDL3tQLbaWq2Bfk/
** 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 , eg `curl -Ss <nowiki>https://www.random.org/cgi-bin/randbyte?nbytes=16384&format=f</nowiki> > /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 brtfs will help with the corruption issues of xts " they may not have even been talking about luks directly and i just got cornfused ( 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 noob 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
* Templates
** user profile information template (need to flesh out how this will look)
** 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 placeholder "
** " this page is an accessory to another? " ( maybe see or see also cover this , idk )

TODO

2026-04-19T18:22:38Z

CRYSTL: fix punctuation

TODO

2026-04-19T18:21:44Z

CRYSTL: start TODO page

Main Page

2026-03-29T20:38:14Z

CRYSTL: updated link to the fassag entrance

Welcome to the '''FASSAG Wiki'''. This editable knowledge base contains an ever-changing collection of resources developed by the organization.

== What is FASSAG ? ==

====== The Free Accessible Safe Software Advocacy Group ======
Our mission is to reach out and make technology accessible and easy to understand. We seek to provide resources and guidance on computer safety, guides on various software, at whatever level of complexity is right for you. You can get involved as much as you'd like! Whether you want to help out with research, or writing guides, or perhaps you're a developer and want to help improve software, we'd be happy to have your support.

== Getting Started ==

* [https://fassag.dev Home] -- Get a top level view on our mission.
* [[Operations]] -- Get a detailed look at how we operate.
* [https://codeberg.org/FASSAG Forge] -- The Codeberg organization where all our code is stored.
* [https://matrix.to/#/#fassag-entrance:chat.solarpunk.moe?client=element.io Matrix Space] -- Join to chat about FASSAG.

Organization

2026-03-29T18:35:24Z

CRYSTL:

There are both Teams and Roles; Teams function to organize the work that is being done, and Roles are meant to guide how the Teams should organize. Which Roles you take will depend on what skills and experience you have, and what is needed by the Team your are interested in participating. You can have multiple Roles in multiple Teams, if you are able to keep up with the workload.

== Teams ==
There are currently two Teams, but if needs arise, we may create more later, or possible split up existing teams to spread the workload better.

=== R&D : Research and Documentation ===
The main goal of the R&D Team is to create the documentation you are currently reading, and to inform the direction of the Development Team. Let's push the boundaries of what it means for software to be friendly and usable! There's no way to know what needs to be worked on without testing of existing tools, and keeping notes on it. But additionally, what we are able to share with the world, is what we have written here, in the wiki.

=== Development ===
The Development Team is for developing software solutions to software problems! We will need designers, artists, writers, translators, and of course, coders, to make this possible. Good software should adhere as much as possible to the goals laid out in [[Operations]]. Let's try to make our work as modular as we can. We want to be able to work in parallel as much as possible to get things done quickly, but we don't want spaghetti code. Cooperation is important! If you're working on something you think might affect what someone else is doing, ask them about it and make sure your not going to step on each others toes.

== Roles ==
Roles are fluid and you are encouraged to try out different roles to see how well you do, and how well you work with your team. You can of course take more than one Role, but do not over-work yourself! Talking to your Team about what roles you think you would do well at, and what types of roles are needed is very important! We all work best when we work together. Remember, the point of these rules is not to create a power structure, but to organize.

=== Role Templates ===
These roles are well documented and therefore are good to pick from. If you think a different role would be helpful or that something is missing here, please bring it up in [https://matrix.to/#/#fassag-general:chat.solarpunk.moe General]! None of these roles are intended to be exclusive to any Team!

* Lens
Lenses help focus the Team. Lenses should encourage, motivate, and direct. Members should have an idea of how they are best motivated, but if not, Lenses should try to help them figure that out. Lenses also function as oversight, to try to catch potential problems before they happen.
* Scribe
Scribes learn and document. Scribes are heavily encouraged to talk to other members of their team to fill in gaps in their understanding. Whether documenting a project the Development Team is working on, or writing for the R&D team, Scribes should try to write as Accessibly as possible. Of course, developer documentation will inherently be a bit more technical, but they should aim to not make things any more technical than it has to be.
* Engineer
Engineers focus primarily on software itself. When implementing user-facing components, aim to follow guidelines we have already written! If nothing exists however, this is something to bring up with your team! Engineers are also very useful for research, as they will be able to understand why something is the way it is, in a way that those who cannot read code will not be able to.
* Designer
Designers have a very important job, as they will be focusing now just on what looks nice, but also on what is safe and accessible. Designers can help with style guides for writing, icons, UIs, or whatever else really. The goal here is to be creative!
* Tester
Testers should try to push the limits and find bugs and edge cases with the software we are working on and studying. Testers should try to also work with disabled people, to get a better understanding of what methods they use to interact with software, to test out different software using those methods.
* Outreach
This is for the bigger picture stuff. Whether it's managing social accounts, putting up posters, or whatever else, the goal is to get people involved, or at the very least, make people aware of our documentation. Our goal is to help people, and we cannot help them if they do not know about us!

Organization

2026-03-29T17:51:47Z

CRYSTL: add roles meta info

Operations

2026-03-22T18:56:26Z

CRYSTL: fix capitatlization

FASSAG has three main branches, to facilitate the development of our resources; The documentation group, the research group, and the software development group. It's what we think are the three most important aspects to focus on to achieve our goals.

== Documentation ==
'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.

'''Accessible''' documentation isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the documentation being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:

* Screen readers
* High-Contrast modes
* Magnification
* Scaling settings
* Clear design
* Good documentation
* Translations
* Low-end hardware

'''Safe''' software focuses not just on privacy and security, though of course those are important, but also things like no user-hostile features. Addictive design patterns for example, are very dangerous for many people. Things like, Infinite scrollers, algorithmic recommendations. It's also important to have guide rails to prevent the user from breaking their system, though of course experienced users should be able to lower them.

== Advocacy ==
It is important that people understand the importance of safe, secure, and private computing, especially now. A general malaise seems to have gripped much of the current populous about this, a feeling that it's not possible or feasible to have these goals. This however, is very important to fight against! Privacy, Security, and Safety are rights that everyone should have, especially when using a computer.

Being safe online is not just about making sure your accounts get stolen, but also thinking about what data you put where, and how that could be used against you. Make sure you are only trusting as much as you have to, and don't assume that a corporation is safe and has your back. Corporations are made of people, and their cloud, or servers, are just computers that they control. Think about where you're sending your data before you post a message or upload an image.

Part of advocacy is making sure that if there is no good solution, that we help to create one. While we're in early stages, our development capacity will be limited, but whenever we have the ability to, we should try to either improve existing software in these regards, or if impossible, make our own. Be reasonable though! Big goals like making an entire OS would be amazing, but we have to keep in mind how much time and effort we have at our disposal.

We'd also love to have some way to share computers with each other. Some of us may not have a laptop, maybe just a tablet, or a phone, and helping them get access to good computing hardware is critical for our mission. Figuring out how to do this safely and respectfully is a very important goal!

== [[Organization]] ==
To facilitate work being done well, and also to help people figure out what Role to play within FASSAG, we have created several Teams and Roles. These Teams and Roles are fluid, and it's encouraged to switch between them if necessary or desired. These Teams and Roles are also not meant to indicate a power-structure, are goals require us to cooperate as equals.

Remember, it is very important that you do not over-work yourself. Pushing yourself too hard and burning out is the easiest way to hurt yourself while participating in a group like this, and we do not want you to hurt yourself! Also, check on your Teammates, to ensure they are not overworking themselves, but do keep in mind, everyone has different limits.

Different people also respond well to different types of motivation. You are encouraged to describe how you like to be motivated on your wiki profile! If you do not know, then you can ask your Teammates to try out different strategies with you and see how it works for you. For example, some people like reminders/management, and some don't want to be pressured. Some ground-rules though, deadlines are always soft. If you fail to meet a deadline there *must* not be any serious consequences for this. Rushing to meet hard deadlines is an easy way to burn yourself out.

Operations

2026-03-22T18:55:30Z

CRYSTL: change organization to be a link

FASSAG has three main branches, to facilitate the development of our resources; The documentation group, the research group, and the software development group. It's what we think are the three most important aspects to focus on to achieve our goals.

== Documentation ==
'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.

'''Accessible''' documentation isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the documentation being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:

* Screen readers
* High-Contrast modes
* Magnification
* Scaling settings
* Clear design
* Good documentation
* Translations
* Low-end hardware

'''Safe''' software focuses not just on privacy and security, though of course those are important, but also things like no user-hostile features. Addictive design patterns for example, are very dangerous for many people. Things like, Infinite scrollers, algorithmic recommendations. It's also important to have guide rails to prevent the user from breaking their system, though of course experienced users should be able to lower them.

== Advocacy ==
It is important that people understand the importance of safe, secure, and private computing, especially now. A general malaise seems to have gripped much of the current populous about this, a feeling that it's not possible or feasible to have these goals. This however, is very important to fight against! Privacy, Security, and Safety are rights that everyone should have, especially when using a computer.

Being safe online is not just about making sure your accounts get stolen, but also thinking about what data you put where, and how that could be used against you. Make sure you are only trusting as much as you have to, and don't assume that a corporation is safe and has your back. Corporations are made of people, and their cloud, or servers, are just computers that they control. Think about where you're sending your data before you post a message or upload an image.

Part of advocacy is making sure that if there is no good solution, that we help to create one. While we're in early stages, our development capacity will be limited, but whenever we have the ability to, we should try to either improve existing software in these regards, or if impossible, make our own. Be reasonable though! Big goals like making an entire OS would be amazing, but we have to keep in mind how much time and effort we have at our disposal.

We'd also love to have some way to share computers with each other. Some of us may not have a laptop, maybe just a tablet, or a phone, and helping them get access to good computing hardware is critical for our mission. Figuring out how to do this safely and respectfully is a very important goal!

== [[Organization]] ==
To facilitate work being done well, and also to help people figure out what role to play within FASSAG, we have created several Teams and Roles. These teams and roles are fluid, and it's encouraged to switch between them if necessary or desired. These teams and roles are also not meant to indicate a power-structure, are goals require us to cooperate as equals.

Remember, it is very important that you do not over-work yourself. Pushing yourself too hard and burning out is the easiest way to hurt yourself while participating in a group like this, and we do not want you to hurt yourself! Also, check on your Teammates, to ensure they are not overworking themselves, but do keep in mind, everyone has different limits.

Different people also respond well to different types of motivation. You are encouraged to describe how you like to be motivated on your wiki profile! If you do not know, then you can ask your Teammates to try out different strategies with you and see how it works for you. For example, some people like reminders/management, and some don't want to be pressured. Some ground-rules though, deadlines are always soft. If you fail to meet a deadline there *must* not be any serious consequences for this. Rushing to meet hard deadlines is an easy way to burn yourself out.

Organization

2026-03-22T18:55:03Z

CRYSTL: add teams

Operations

2026-03-22T18:51:26Z

CRYSTL: add section about motivation / management

FASSAG has three main branches, to facilitate the development of our resources; The documentation group, the research group, and the software development group. It's what we think are the three most important aspects to focus on to achieve our goals.

== Documentation ==
'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.

'''Accessible''' documentation isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the documentation being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:

* Screen readers
* High-Contrast modes
* Magnification
* Scaling settings
* Clear design
* Good documentation
* Translations
* Low-end hardware

'''Safe''' software focuses not just on privacy and security, though of course those are important, but also things like no user-hostile features. Addictive design patterns for example, are very dangerous for many people. Things like, Infinite scrollers, algorithmic recommendations. It's also important to have guide rails to prevent the user from breaking their system, though of course experienced users should be able to lower them.

== Advocacy ==
It is important that people understand the importance of safe, secure, and private computing, especially now. A general malaise seems to have gripped much of the current populous about this, a feeling that it's not possible or feasible to have these goals. This however, is very important to fight against! Privacy, Security, and Safety are rights that everyone should have, especially when using a computer.

Being safe online is not just about making sure your accounts get stolen, but also thinking about what data you put where, and how that could be used against you. Make sure you are only trusting as much as you have to, and don't assume that a corporation is safe and has your back. Corporations are made of people, and their cloud, or servers, are just computers that they control. Think about where you're sending your data before you post a message or upload an image.

Part of advocacy is making sure that if there is no good solution, that we help to create one. While we're in early stages, our development capacity will be limited, but whenever we have the ability to, we should try to either improve existing software in these regards, or if impossible, make our own. Be reasonable though! Big goals like making an entire OS would be amazing, but we have to keep in mind how much time and effort we have at our disposal.

We'd also love to have some way to share computers with each other. Some of us may not have a laptop, maybe just a tablet, or a phone, and helping them get access to good computing hardware is critical for our mission. Figuring out how to do this safely and respectfully is a very important goal!

== Organization [[Organization|Main Page]] ==
To facilitate work being done well, and also to help people figure out what role to play within FASSAG, we have created several Teams and Roles. These teams and roles are fluid, and it's encouraged to switch between them if necessary or desired. These teams and roles are also not meant to indicate a power-structure, are goals require us to cooperate as equals.

Remember, it is very important that you do not over-work yourself. Pushing yourself too hard and burning out is the easiest way to hurt yourself while participating in a group like this, and we do not want you to hurt yourself! Also, check on your Teammates, to ensure they are not overworking themselves, but do keep in mind, everyone has different limits.

Different people also respond well to different types of motivation. You are encouraged to describe how you like to be motivated on your wiki profile! If you do not know, then you can ask your Teammates to try out different strategies with you and see how it works for you. For example, some people like reminders/management, and some don't want to be pressured. Some ground-rules though, deadlines are always soft. If you fail to meet a deadline there *must* not be any serious consequences for this. Rushing to meet hard deadlines is an easy way to burn yourself out.

Operations

2026-03-22T18:30:35Z

CRYSTL: add note about overwork to organization section

FASSAG has three main branches, to facilitate the development of our resources; The documentation group, the research group, and the software development group. It's what we think are the three most important aspects to focus on to achieve our goals.

== Documentation ==
'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.

'''Accessible''' documentation isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the documentation being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:

* Screen readers
* High-Contrast modes
* Magnification
* Scaling settings
* Clear design
* Good documentation
* Translations
* Low-end hardware

'''Safe''' software focuses not just on privacy and security, though of course those are important, but also things like no user-hostile features. Addictive design patterns for example, are very dangerous for many people. Things like, Infinite scrollers, algorithmic recommendations. It's also important to have guide rails to prevent the user from breaking their system, though of course experienced users should be able to lower them.

== Advocacy ==
It is important that people understand the importance of safe, secure, and private computing, especially now. A general malaise seems to have gripped much of the current populous about this, a feeling that it's not possible or feasible to have these goals. This however, is very important to fight against! Privacy, Security, and Safety are rights that everyone should have, especially when using a computer.

Being safe online is not just about making sure your accounts get stolen, but also thinking about what data you put where, and how that could be used against you. Make sure you are only trusting as much as you have to, and don't assume that a corporation is safe and has your back. Corporations are made of people, and their cloud, or servers, are just computers that they control. Think about where you're sending your data before you post a message or upload an image.

Part of advocacy is making sure that if there is no good solution, that we help to create one. While we're in early stages, our development capacity will be limited, but whenever we have the ability to, we should try to either improve existing software in these regards, or if impossible, make our own. Be reasonable though! Big goals like making an entire OS would be amazing, but we have to keep in mind how much time and effort we have at our disposal.

We'd also love to have some way to share computers with each other. Some of us may not have a laptop, maybe just a tablet, or a phone, and helping them get access to good computing hardware is critical for our mission. Figuring out how to do this safely and respectfully is a very important goal!

== Organization [[Organization|Main Page]] ==
To facilitate work being done well, and also to help people figure out what role to play within FASSAG, we have created several Teams and Roles. These teams and roles are fluid, and it's encouraged to switch between them if necessary or desired. These teams and roles are also not meant to indicate a power-structure, are goals require us to cooperate as equals.

Remember, it is very important that you do not over-work yourself. Pushing yourself too hard and burning out is the easiest way to hurt yourself while participating in a group like this, and we do not want you to hurt yourself! Also, check on your Teammates, to ensure they are not overworking themselves, but do keep in mind, everyone has different limits.

Operations

2026-03-22T18:20:02Z

CRYSTL: add organization stub

FASSAG has three main branches, to facilitate the development of our resources; The documentation group, the research group, and the software development group. It's what we think are the three most important aspects to focus on to achieve our goals.

== Documentation ==
'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.

'''Accessible''' documentation isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the documentation being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:

* Screen readers
* High-Contrast modes
* Magnification
* Scaling settings
* Clear design
* Good documentation
* Translations
* Low-end hardware

'''Safe''' software focuses not just on privacy and security, though of course those are important, but also things like no user-hostile features. Addictive design patterns for example, are very dangerous for many people. Things like, Infinite scrollers, algorithmic recommendations. It's also important to have guide rails to prevent the user from breaking their system, though of course experienced users should be able to lower them.

== Advocacy ==
It is important that people understand the importance of safe, secure, and private computing, especially now. A general malaise seems to have gripped much of the current populous about this, a feeling that it's not possible or feasible to have these goals. This however, is very important to fight against! Privacy, Security, and Safety are rights that everyone should have, especially when using a computer.

Being safe online is not just about making sure your accounts get stolen, but also thinking about what data you put where, and how that could be used against you. Make sure you are only trusting as much as you have to, and don't assume that a corporation is safe and has your back. Corporations are made of people, and their cloud, or servers, are just computers that they control. Think about where you're sending your data before you post a message or upload an image.

Part of advocacy is making sure that if there is no good solution, that we help to create one. While we're in early stages, our development capacity will be limited, but whenever we have the ability to, we should try to either improve existing software in these regards, or if impossible, make our own. Be reasonable though! Big goals like making an entire OS would be amazing, but we have to keep in mind how much time and effort we have at our disposal.

We'd also love to have some way to share computers with each other. Some of us may not have a laptop, maybe just a tablet, or a phone, and helping them get access to good computing hardware is critical for our mission. Figuring out how to do this safely and respectfully is a very important goal!

== Organization [[Organization|Main Page]] ==
To facilitate work being done well, and also to help people figure out what role to play within FASSAG, we have created several Teams and Roles. These teams and roles are fluid, and it's encouraged to switch between them if necessary or desired. These teams and roles are also not meant to indicate a power-structure, are goals require us to cooperate as equals.

Operations

2026-03-22T17:58:50Z

CRYSTL: add advocacy section

FASSAG has three main branches, to facilitate the development of our resources; The documentation group, the research group, and the software development group. It's what we think are the three most important aspects to focus on to achieve our goals.

== Documentation ==
'''Free''' means that their should be as little costs as possible to everyone involved. Free to contribute, and free to read. Getting permission to contribute is as simple as asking in the [matrix] space. It's important for our community model that we can talk to and discuss changes that people have made if we need to.

'''Accessible''' documentation isn't just about screen readers. The text should be written so that it is easy to read, and tries to avoid overly-technical explanations with a lot of jargon. Paragraphs should be capped at 5 or so sentences to avoid the "wall of text" effect. Docs should also try to target different skill/knowledge levels. But besides the documentation being accessible, it's important to document how to *make* computers be more accessible. That means testing things like:

* Screen readers
* High-Contrast modes
* Magnification
* Scaling settings
* Clear design
* Good documentation
* Translations
* Low-end hardware

'''Safe''' software focuses not just on privacy and security, though of course those are important, but also things like no user-hostile features. Addictive design patterns for example, are very dangerous for many people. Things like, Infinite scrollers, algorithmic recommendations. It's also important to have guide rails to prevent the user from breaking their system, though of course experienced users should be able to lower them.

== Advocacy ==
It is important that people understand the importance of safe, secure, and private computing, especially now. A general malaise seems to have gripped much of the current populous about this, a feeling that it's not possible or feasible to have these goals. This however, is very important to fight against! Privacy, Security, and Safety are rights that everyone should have, especially when using a computer.

Being safe online is not just about making sure your accounts get stolen, but also thinking about what data you put where, and how that could be used against you. Make sure you are only trusting as much as you have to, and don't assume that a corporation is safe and has your back. Corporations are made of people, and their cloud, or servers, are just computers that they control. Think about where you're sending your data before you post a message or upload an image.

Part of advocacy is making sure that if there is no good solution, that we help to create one. While we're in early stages, our development capacity will be limited, but whenever we have the ability to, we should try to either improve existing software in these regards, or if impossible, make our own. Be reasonable though! Big goals like making an entire OS would be amazing, but we have to keep in mind how much time and effort we have at our disposal.

We'd also love to have some way to share computers with eachother. Some of us may not have a laptop, maybe just a tablet, or a phone, and helping them get access to good computing hardware is critical for our mission. Figuring out how to do this safely and respectfully is a very important goal!

Operations

2026-03-22T17:39:59Z

CRYSTL: add documentation summary

Operations

2026-03-18T14:35:52Z

CRYSTL:

Operations

2026-03-18T02:56:40Z

CRYSTL: Created page with "== Overview == FASSAG has three main branches, to facilitate the development of our resources."

== Overview ==
FASSAG has three main branches, to facilitate the development of our resources.

Main Page

2026-03-18T02:52:56Z

CRYSTL: add a summary

User:CRYSTL

2026-03-17T01:28:34Z

CRYSTL: created page

Hello , we are CRYSTL !

We are happy to help with whatever problems you may have !

You can reach us on matrix at @crystallinefire:chat.solarpunk.moe

Main Page

2026-03-17T00:07:33Z

CRYSTL: added link to operations page

Welcome to the '''FASSAG Wiki'''. This editable knowledge base contains an ever-changing collection of resources developed by the organization.

== Getting Started ==

* [https://fassag.dev Home] -- Get a top level view on our mission.
* [[Operations]] -- Get a detailed look at how we operate.
* [https://codeberg.org/FASSAG Forge] -- The Codeberg organization where all our code is stored.
* Matrix Space -- Join to chat about FASSAG.