Tait Hoyem
2 years ago
parent
a6d5360ce4
commit
5d51233189
@ -0,0 +1,62 @@
|
||||
---
|
||||
layout: default
|
||||
title: "Blind Linux Config Files"
|
||||
permalink: "/blind-linux-config/"
|
||||
---
|
||||
|
||||
Here are some configuration files that I have found helpful for blind and visually impaired Linux users:
|
||||
|
||||
{% include toc.html %}
|
||||
|
||||
## Chromium/Electron
|
||||
|
||||
To enable accessibility in Chromium and Electron, use the following flags in `$XDG_CONFIG_HOME/chromium-flags.conf` and `$XDG_CONFIG_HOME/electron-flags.conf` respectively. `$XDG_CONFIG_HOME` defaults to `$HOME/.config`.
|
||||
|
||||
```text
|
||||
--force-renderer-accessibility
|
||||
--enable-caret-browsing
|
||||
```
|
||||
|
||||
You will also want to add the following to your `~/.bashrc`:
|
||||
|
||||
```text
|
||||
export ENABLE_ACCESSIBILITY=1
|
||||
```
|
||||
|
||||
## Wi-Fi
|
||||
|
||||
There are a lot of different ways to connect to the internet on Linux, my favourite is with NetworkManager using `nmcli`.
|
||||
It can be done as one command like the following (rememnber that `$` is just indicating that a command is being run):
|
||||
|
||||
<pre class="terminal">
|
||||
$ nmcli dev wifi con "ssid_here" password "password_here" name "saved_name_for_future"
|
||||
</pre>
|
||||
|
||||
And without a password (open network):
|
||||
|
||||
<pre class="terminal">
|
||||
$ nmcli dev wifi con "ssid_here" name "saved_name"
|
||||
</pre>
|
||||
|
||||
Now that's all well and good, but it's pretty long to remember, so I made a little script in my [scripts repository](https://git.tait.tech/tait/scripts/).
|
||||
This has all sorts of nice tools related to making everything easier to use from the command line (which incidently *should* make it easier for blind peeps as well).
|
||||
|
||||
## GPG/PGP/pass
|
||||
|
||||
By default (on some distributions), when `gpg` asks for a private key password, it asks for it in a GUI pop-up window.
|
||||
I find this annoying and it is slow on devices like the [PinebookPro](/2021/06/02/pinebook-pro/).
|
||||
To disable this and have a plain prompt in your terminal instead, use the following in your `$HOME/.gnupg/gpg-agent.conf`:
|
||||
|
||||
```text
|
||||
pinentry-program /usr/bin/pinentry-tty
|
||||
```
|
||||
|
||||
To activate it, restart gpg-agent by killing it, then attempting to use a private key:
|
||||
|
||||
<pre class="terminal">
|
||||
$ killall gpg-agent
|
||||
# using gpg directly
|
||||
$ gpg --encrypt ...
|
||||
# using the pass password manager
|
||||
$ pass show your/password
|
||||
</pre>
|
||||
@ -0,0 +1,62 @@
|
||||
---
|
||||
layout: default
|
||||
title: "Blind Linux Config Files"
|
||||
permalink: "/blind-linux-configs/"
|
||||
---
|
||||
|
||||
Here are some configuration files that I have found helpful for blind and visually impaired Linux users:
|
||||
|
||||
{% include toc.md %}
|
||||
|
||||
## Chromium/Electron
|
||||
|
||||
To enable accessibility in Chromium and Electron, use the following flags in `$XDG_CONFIG_HOME/chromium-flags.conf` and `$XDG_CONFIG_HOME/electron-flags.conf` respectively. `$XDG_CONFIG_HOME` defaults to `$HOME/.config`.
|
||||
|
||||
```text
|
||||
--force-renderer-accessibility
|
||||
--enable-caret-browsing
|
||||
```
|
||||
|
||||
You will also want to add the following to your `~/.bashrc`:
|
||||
|
||||
```text
|
||||
export ENABLE_ACCESSIBILITY=1
|
||||
```
|
||||
|
||||
## Wi-Fi
|
||||
|
||||
There are a lot of different ways to connect to the internet on Linux, my favourite is with NetworkManager using `nmcli`.
|
||||
It can be done as one command like the following (rememnber that `$` is just indicating that a command is being run):
|
||||
|
||||
<pre class="terminal">
|
||||
$ nmcli dev wifi con "ssid_here" password "password_here" name "saved_name_for_future"
|
||||
</pre>
|
||||
|
||||
And without a password (open network):
|
||||
|
||||
<pre class="terminal">
|
||||
$ nmcli dev wifi con "ssid_here" name "saved_name"
|
||||
</pre>
|
||||
|
||||
Now that's all well and good, but it's pretty long to remember, so I made a little script in my [scripts repository](https://git.tait.tech/tait/scripts/).
|
||||
This has all sorts of nice tools related to making everything easier to use from the command line (which incidently *should* make it easier for blind peeps as well).
|
||||
|
||||
## GPG/PGP/pass
|
||||
|
||||
By default (on some distributions), when `gpg` asks for a private key password, it asks for it in a GUI pop-up window.
|
||||
I find this annoying and it is slow on devices like the [PinebookPro](/2021/06/02/pinebook-pro/).
|
||||
To disable this and have a plain prompt in your terminal instead, use the following in your `$HOME/.gnupg/gpg-agent.conf`:
|
||||
|
||||
```text
|
||||
pinentry-program /usr/bin/pinentry-tty
|
||||
```
|
||||
|
||||
To activate it, restart gpg-agent by killing it, then attempting to use a private key:
|
||||
|
||||
<pre class="terminal">
|
||||
$ killall gpg-agent
|
||||
# using gpg directly
|
||||
$ gpg --encrypt ...
|
||||
# using the pass password manager
|
||||
$ pass show your/password
|
||||
</pre>
|
||||
@ -0,0 +1,54 @@
|
||||
---
|
||||
layout: default
|
||||
title: "Cheese"
|
||||
---
|
||||
|
||||
This is a list of good cheeses and why I like them;
|
||||
I realize this is sort of a snobby thing.
|
||||
Tried fancy cheese once and it's so good I decided to make a little page for recipies and types of cheese.
|
||||
|
||||
Each second level heading is for some section of the page: recipies, cheese types, stores, etc.
|
||||
|
||||
## Recipies
|
||||
|
||||
Simple crackers are sometimes the absolute shit!
|
||||
Add a tomato and some basil (or pesto) and you are set.
|
||||
|
||||
Here are some good stuff to add on a cracker with cheese:
|
||||
|
||||
### Good With Crackers
|
||||
|
||||
* Tomato slice
|
||||
* Turkey ham slice (or thicker ham if you want some high protein)
|
||||
* Avacado
|
||||
* Basil
|
||||
* Pesto
|
||||
* Cilantro (called coreander in the U.K.)
|
||||
|
||||
### Cracker Types
|
||||
|
||||
* Breton plain
|
||||
* Breton garden vegatable
|
||||
|
||||
## Stores
|
||||
|
||||
### Vancouver, BC, Canada
|
||||
|
||||
* Le Ami Du Fromage
|
||||
* Very friendly
|
||||
* Decent value (for fancy cheese, lol)
|
||||
* Address: XYZ
|
||||
|
||||
## Cheeses
|
||||
|
||||
### Favourites
|
||||
|
||||
* Breichet
|
||||
* Swiss
|
||||
* unpasturized, cow's milk base
|
||||
* Medium firmness
|
||||
*
|
||||
* Brie
|
||||
*
|
||||
* Smoked Gorgonzola
|
||||
* Medium firmness
|
||||
@ -0,0 +1,12 @@
|
||||
---
|
||||
layout: default
|
||||
math: true
|
||||
title: "MathML | Examples"
|
||||
---
|
||||
|
||||
Here is an example of an equation with sufficient complexity to warrent the use of MathML:
|
||||
|
||||
{% katex display %}
|
||||
x = \frac{-b \pm \sqrt{b^{2} - 4ac}}{2a}
|
||||
{% endkatex %}
|
||||
|
||||
@ -0,0 +1,45 @@
|
||||
---
|
||||
layout: default
|
||||
---
|
||||
|
||||
# Licenses
|
||||
|
||||
I agree with free-culture licenses; I am a hippie at heart.
|
||||
I license all the content on my site under the [CC-BY-SA](TODO).
|
||||
|
||||
## Other Licenses
|
||||
|
||||
### GPL
|
||||
|
||||
The GPL is the only license which guarantees code openness.
|
||||
It allows people to redistribute and modify your code with no restrictions except that they must also share all changes back to the original author.
|
||||
|
||||
### MIT/BSD/Apache/Mozilla/etc.
|
||||
|
||||
The MIT and BSD licenses are more considered more "permissive" in that they allow closed source derivatives of the code to exist.
|
||||
Part of me wants to like this more: more freedom right?
|
||||
Sure, I suppose, but not freedom for users: the vast majority of the time this is freedom only for corporations.
|
||||
I'm sure this occasionally helps a small business, but I see the MIT and BSD licenses as mostly a way to get big corporations free software that they can then sell for a profit.
|
||||
To be clear, you can do this under the GPL as well, but at least with the GPL and changes made by a corporation making money from the software get shared back with the author and makes the *software* better for everyone.
|
||||
|
||||
### CC-based licenses
|
||||
|
||||
Creative Commons (CC) based licenses are more for artistic works (like blog articles and information) and apply very rarely to programs.
|
||||
CC licenses may have a combination of a few different restrictions, or no restrictions (also known as the CC0 or Public Domain license).
|
||||
|
||||
The restrictions are as follows:
|
||||
|
||||
* BY--the original author must be credited.
|
||||
* SA (Share-alike)--all derivative works must share the same license.
|
||||
* NC (Non-commercial)--the material may not be used for profit.
|
||||
* ND (No derivatives)--the material may only be used as is; you may not edit the materials and redistribute them.
|
||||
|
||||
I considered giving this site a CC-based license but ultimately decided against it;
|
||||
you never know who is going to just take it and then credit you in tiny invisible letters at the bottom of the page.
|
||||
So to avoid that whole fiasco, I use the final license:
|
||||
|
||||
### Copyright
|
||||
|
||||
Full copyright means no derivatives or redistributions may be made in any way, shape or form.
|
||||
I use this on my own pages to protect myself, but I'd be happy to let someone use it no problem if they just ask.
|
||||
It gives me a bit more control over where my content ends up.
|
||||
Loading…
Reference in new issue