Emma Humphries emceeaich

Merlin's First Fruity Pleaser

Ingredients

Peychaud's Bitters | 3-5 squirts
Angostura Bitters | 2-5 squirts
Regular Crappy Bottled ReaLime® | 1+ capful
Seltzer Water | 12 oz | Chilled

Steps

So you want to use Mastodon API! Great!

Overview

Mastodon API is a simple REST api. What's REST? Not important, it's a kind of HTTP API. What's HTTP? It's what web pages are loaded with and kind of thing that everyone is using these days.

How do you load something from Mastodon? You do request like

GitLab to GitHub Enterprise Cloud (GHEC) migration playbook

This playbook is a step-by-step guide to assist you with migration from GitLab to GitHub.com Enterprise Cloud GHEC.

Steps & Tasks	Description
Step One	Let's get ready for the migration. This step gives you an overview of what is required to start the migration process
Step Two	Creating the artefact to be imported on GitHub requires special access to the Enterprise Cloud Import tool. This step will help you understand what is required to get access to the tool.
Step Three	With the file ready to be imported, this step will guide you on how to connect and upload the file to your GitHub Enterprise Cloud instance.

React Bias

It may seem like a bold suggestion that we as web developers can choose the wrong tools for the job because we tend to be swayed by appeals to popularity or authority, but simple statistics imply just that. For example, React (https://reactjs.org/) is a JavaScript framework that emphasizes componentization and simplified state management. It enjoys strong advocacy from a vocal and dedicated userbase within the developer community.

Despite React’s apparent popularity, however, The HTTP Archive observed in 2020 that React only accounted for 4% of all libraries in use across the 7.56 million origins it analyzed (https://almanac.httparchive.org/en/2020/javascript#libraries).

For context, The State of JS 2020 Survey (https://2020.stateofjs.com/en-US/), which surveyed roughly 23,765 respondents, offers the following statistics:

70.8% of respondents identified as white.
91.1% identified as male, whereas 5.8% identified as female and 0.9% identified as non-binary/third gender.

What happens after Outreachy?

Disclaimer: These thoughts are my own (Bianca Danforth) based on my experience starting as an Outreachy at Mozilla and now working as a Senior Software Engineer.

Congratulations! You’ve just completed your Outreachy internship. You may be wondering: Where do I go from here? How do I get a job in software engineering? Below are a set of steps I recommend based on my own experience.

Introspect

Identify goals
- What are your professional goals?
- If you're not sure where to start, ask other people you admire what their professional goals are.
Identify skills
What skills do you need to achieve your goals (those you already have, those that you need to improve, and those you need to learn)?

It just crystallized for me what I think has been mistaken about thinking of unwanted interaction on social networks as a "privacy" problem. It's not.

A privacy problem is things becoming known more widely than they should, subject to surveillance and contextless scrutiny.

The onslaught of sexual harassment on platforms like early Twitter (and later twitter for people of notability), @KeybaseIO, every naive social network is an attack on the right to exist in public. It is the inverse of a privacy problem.

But the conceiving of this as a privacy problem brings the wrong solutions. It means we are offered tools to remove ourselves from public view, to restrict our public personas, to retreat from public life. It means women are again confined to private sphere, denied civic life.

It's so endemic, so entrenched, and so normal that women should have to retreat to protect ourselves that we think of this as part of femininity. A strong civic life is seen as unfeminine, forward. It poisons us politically, socia

	// 3D Dom viewer, copy-paste this into your console to visualise the DOM as a stack of solid blocks.
	// You can also minify and save it as a bookmarklet (https://www.freecodecamp.org/news/what-are-bookmarklets/)
	(() => {
	const SHOW_SIDES = false; // color sides of DOM nodes?
	const COLOR_SURFACE = true; // color tops of DOM nodes?
	const COLOR_RANDOM = false; // randomise color?
	const COLOR_HUE = 190; // hue in HSL (https://hslpicker.com)
	const MAX_ROTATION = 180; // set to 360 to rotate all the way round
	const THICKNESS = 20; // thickness of layers
	const DISTANCE = 10000; // ¯\\_(ツ)_/¯

	This gist describes the process of making a self-hosted installation
	of Wordpress run with SQLite as a backing store, rather than MySQL.

	This is not a step-by-step guide, and will require some degree of
	comfort with your filesystem, editors, and logging. This involves
	both fighting with and lying to these systems, and consequently
	comes with no guarantees whatsoever.

	---------------

	<?xml version="1.0" encoding="UTF-8"?>
	<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
	<xsl:output method="xml" encoding="UTF-8" indent="yes" omit-xml-declaration="yes" />

	<xsl:template match="opml">
	<xsl:text disable-output-escaping="yes"><![CDATA[<!DOCTYPE html>]]></xsl:text>
	<html>
	<head>
	<meta charset="utf-8" />
	<xsl:apply-templates select="head/title" />

	global
	log 127.0.0.1:1312 local0

	# generated 2021-05-25, Mozilla Guideline v5.6, HAProxy 2.3.10, OpenSSL 1.1.1.k-1, modern configuration
	# https://ssl-config.mozilla.org/#server=haproxy&version=2.3.10&config=modern&openssl=1.1.1.k-1&guideline=5.6
	# modern configuration
	ssl-default-bind-ciphersuites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
	ssl-default-bind-options prefer-client-ciphers no-sslv3 no-tlsv10 no-tlsv11 no-tlsv12 no-tls-tickets
	ssl-default-server-ciphersuites TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
	ssl-default-server-options no-sslv3 no-tlsv10 no-tlsv11 no-tlsv12 no-tls-tickets