Will Barton willbarton

Learning Rust

Getting Started + Installation | Cheat Sheet

The Steam Deck can run Mass Effect Legendary Edition with almost no fiddling (at least if you bought it through Steam; Origin installs will not be covered in this guide specifically but most of it should still work if you can get the vanilla game running), but modding it is a different story. You have to run a windows program that has graphical issues without config changes, and give it access to the game directory because the game runs in a sandbox. I will cover how to get the ME3Tweaks Mod Manager running well enough to install and update mods, and lay out the known issues and limitations.

As a reminder, the modding tool set is built for Windows. Linux is not supported and will not be supported in the forseeable future. Linux specific bugs will very likely not get worked on. This guide is to help the small proportion of users who want to use the mod manager on Linux despite the lack of support and the issues and difficulty it will bring.

Most of this guide will happen in Desktop mode, but by the

Infrared and LIRC

*Beware: These instructions have been cobbled together from all of the sources I found that got my specific unit working. I can verify it works on a Pi 3B running the latest OS as of summer 2019. Everyone's hardware and system will be a bit different so your mileage may vary. Before you go crazy trying to debug issues sending a signal, grab an existing lirc config for any remote and use the lirc CLI to send a signal out and verify your hardware is sending the signal by viewing the IR LED through a front-facing smartphone camera (almost all smartphone front cameras - even new iPhones - will not filter out IR light and you should see the LED flash when sending a signal). If you see your hardware is sending a signal and/or you can see that the IR input is seeing some signal, then you know your setup works and the issue may be that the remote you're trying to learn simply won't work with LIRC. I know for a fact that many Comcast/Xfinity cable remotes are actually RF devices and need to have

UPDATE (2021-03-31): I've posted an improved version of this guide with newer versions of the software.

Turn a Raspberry Pi into an Astrophotography Autoguider

@codefinger

I hate when my images turn out like this:

These are some steps that users can take to retain privacy online. These aren't perfect, but aim to strike a balance between privacy and usability.

Level 1

Enable Do Not Track in your browser
Use a tracker blocking plugin such as Privacy Badger or Ghostery
Disable third-party cookies
Use the HTTPS Everywhere browser extension

GPG and git on macOS

Setup

No need for homebrew or anything like that. Works with https://www.git-tower.com and the command line.

Install https://gpgtools.org -- I'd suggest to do a customized install and deselect GPGMail.
Create or import a key -- see below for https://keybase.io
Run gpg --list-secret-keys and look for sec, use the key ID for the next step
Configure git to use GPG -- replace the key with the one from gpg --list-secret-keys

	Notes to make IR shield (made by LinkSprite) work in Raspberry Pi 3 (bought from Amazon [1]).
	The vendor has some documentation [2] but that is not complete and sufficient for Raspbian Stretch.
	Following are the changes that I made to make it work.

	$ sudo apt-get update
	$ sudo apt-get install lirc

	# Add the following lines to /etc/modules file
	lirc_dev
	lirc_rpi gpio_in_pin=18 gpio_out_pin=17

	from logging.handlers import SysLogHandler
	LOGGING = {
	'version': 1,
	'disable_existing_loggers': True,
	'formatters': {
	'standard': {
	'format' : "[YOUR PROJECT NAME] [%(asctime)s] %(levelname)s [%(name)s:%(lineno)s] %(message)s",
	'datefmt' : "%d/%b/%Y %H:%M:%S"
	},
	'verbose': {

	# In order for gpg to find gpg-agent, gpg-agent must be running, and there must be an env
	# variable pointing GPG to the gpg-agent socket. This little script, which must be sourced
	# in your shell's init script (ie, .bash_profile, .zshrc, whatever), will either start
	# gpg-agent or set up the GPG_AGENT_INFO variable if it's already running.

	# Add the following to your shell init to set up gpg-agent automatically for every shell
	if [ -f ~/.gnupg/.gpg-agent-info ] && [ -n "$(pgrep gpg-agent)" ]; then
	source ~/.gnupg/.gpg-agent-info
	export GPG_AGENT_INFO
	else

	Short description explaining the highlevel reason for the pull request

	## Additions

	- List of additions made
	- To the project
	- Within this PR

	## Removals