elfbert:

nadiaoxford:

brynwrites:

There are two types of writers…

Writer A: “I’ve fleshed this character out to the point where they’re more real then I am. I know everything about them, including their blood type, their thirty-first favorite song, what they did for their sixth birthday, and which brand of apples they prefer.”

Writer B: “This character exists as a full person in my head, but I know absolutely nothing about them. Once I forced them to talk about themselves,  and they simultaneous lied about their past and told me accurate trivia facts I don’t remember learning.”

I am B. I am certainly B.

B. All the way. I think I know something about a character I have mainly created in my head and I turn out to be wrong….

iguanastevens:

AO3, fanfiction, and comments: the system isn’t working. 

Fic authors have a problem with feedback – or rather, with the lack of it. Fanfiction has a notoriously low ratio of comments to hits, and many of us have expressed our frustration that we can get a hundred, two hundred, five hundred, even a thousand views on our stories, but only a handful of readers will leave kudos, let alone comments.   

Unfortunately, this only gets worse for long, multi-chapter stories (aka, the longfics we know, love, and would sell our souls in a second if it meant an update), which also happen to be the stories that authors need the most support to continue and complete. Law of diminishing returns, y’all, and it sucks. 

We’re not here to guilt you into leaving comments.

We want to address the problem by changing the format, and we need your help to do it. 

The goal is to increase the amount of feedback authors get from readers, especially on stories with multiple chapters, and to make it easier for everyone to show how much we love fics. We’re opening a discussion with ao3 to figure out how/if any of these options can be implemented, but first we need options to present! 

Some of our current ideas: 

• Ability to leave a form of kudos on every chapter, instead of only once on the entire story: this lets authors know that you’re here and you’re reading their updates, so their hard work isn’t getting tossed into the internet void. 
• Comment templates: suggested comments that can be customized or posted as-is. Many of us draw a blank or get nervous when we try to think of a comment, so having pre-made options will both increase the total level of feedback and serve as practice, making it easier to leave more in-depth comments in the future. 
• Upvoting/leaving kudos on comments themselves: positive reinforcement makes giving feedback more fun and rewarding, and it lets the author know that readers are present and agreeing with other comments, even if they don’t leave one themselves. 

We’ll contact AO3 to discuss the possibility of adding any of these as native features, and if that won’t work, we’re looking into creating and sharing a user script. 

 What you can do to help: 

•  As a reader, what would you like to have? What would you be most likely to use? New ideas, opinions on ideas that are listed here, they’re all good. 
• As a creator, how would you feel about each of these options? Can you think of other ways of receiving or encouraging feedback? 
• Pros and cons of these (note: our thoughts on this are discussed in this google doc) 
• GET THE WORD OUT! Reblog this post, send it to your friends, link to it from your stories. We need as much input and support as possible to get this off the ground. 

Feedback makes for happy authors. Happy authors make for more stories. Let’s keep this part of fandom alive! 

More details about our thoughts, discussions, and ideas can be found in this google doc.

One of my few strong beliefs is that if X spends days/ weeks/ months making something, and this something gives W, Y and Z a few moments of joy/ pleasure/ thought/ tears/ laughs, then it’s fair that W, Y and Z should let X know. X will keep on making things anyway, but they will feel a little happier and more confident while doing it.

brooklynboobala:

the-fertix:

toughestfrail:

isnerdy:

rolypolywardrobe:

systlin:

darkersolstice:

max-vandenburg:

eldritchscholar:

So the other night during D&D, I had the sudden thoughts that:

1) Binary files are 1s and 0s

2) Knitting has knit stitches and purl stitches

You could represent binary data in knitting, as a pattern of knits and purls…

You can knit Doom.

However, after crunching some more numbers:

The compressed Doom installer binary is 2.93 MB. Assuming you are using sock weight yarn, with 7 stitches per inch, results in knitted doom being…

3322 square feet

Factoring it out…302 people, each knitting a relatively reasonable 11 square feet, could knit Doom.

Hi fun fact!!

The idea of a “binary code” was originally developed in the textile industry in pretty much this exact form. Remember punch cards? Probably not! They were a precursor to the floppy disc, and were used to store information in the same sort of binary code that we still use:

Here’s Mary Jackson (c.late 1950s) at a computer. If you look closely in the yellow box, you’ll see a stack of blank punch cards that she will use to store her calculations.

This is what a card might look like once punched. Note that the written numbers on the card are for human reference, and not understood by the computer. 

But what does it have to do with textiles? Almost exactly what OP suggested. Now even though machine knitting is old as balls, I feel that there are few people outside of the industry or craft communities who have ever seen a knitting machine. 

Here’s a flatbed knitting machine (as opposed to a round or tube machine), which honestly looks pretty damn similar to the ones that were first invented in the sixteenth century, and here’s a nice little diagram explaining how it works:

But what if you don’t just want a plain stocking stitch sweater? What if you want a multi-color design, or lace, or the like? You can quite easily add in another color and integrate it into your design, but for, say, a consistent intarsia (two-color repeating pattern), human error is too likely. Plus, it takes too long for a knitter in an industrial setting. This is where the binary comes in!

Here’s an intarsia swatch I made in my knitwear class last year. As you can see, the front of the swatch is the inverse of the back. When knitting this, I put a punch card in the reader,

and as you can see, the holes (or 0′s) told the machine not to knit the ground color (1′s) and the machine was set up in such a way that the second color would come through when the first color was told not to knit.

tl;dr the textiles industry is more important than people give it credit for, and I would suggest using a machine if you were going to try to knit almost 3 megabytes of information.

@we-are-threadmage

Someone port Doom to a blanket

I really love tumblr for this 🙌

It goes beyond this.  Every computer out there has memory.  The kind of memory you might call RAM.  The earliest kind of memory was magnetic core memory.  It looked like this:

Wires going through magnets.  This is how all of the important early digital computers stored information temporarily.  Each magnetic core could store a single bit – a 0 or a 1.  Here’s a picture of a variation of this, called rope core memory, from one NASA’s Apollo guidance computers:

You may think this looks incredibly handmade, and that’s because it is.  But these are also extreme close-ups.  Here’s the scale of the individual cores:

The only people who had the skills necessary to thread all of these cores precisely enough were textile and garment workers.  Little old ladies would literally thread the wires by hand.

And thanks to them, we were able to land on the moon.  This is also why memory in early computers was so expensive.  It had to be hand-crafted, and took a lot of time.

I knew some of this but then it took such a turn!!!!

@lokirulz 8U!!!

I may not understand math, code, and computers, but I sure do understand little old ladies mending garments! This is beautiful.

WOW.