-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Article submission on the rhetorical stylistics of databending. #13
base: master
Are you sure you want to change the base?
Conversation
then, has attributed a set of values to databending \(act\) and its datamoshy output | ||
\(consequence\). From such source-level practices, Briz attempts to persuade users who conduct his | ||
GCT and most likely already have some degree of value placed on its output, to espouse this value, | ||
perhaps aready shared by consumers of glitch art on the output-end, through the a person's |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be 'already', yea?
And I'm going to be that person that thinks one thing and types another. The above Latour should be Reassembling the Social. I mentally combined it with Making Things Public. |
In Brock's article[^brock1], he analyzes developers' use of metaphors in naming conventions within | ||
the bounds of more professional spheres. In this article, I examine a different community who | ||
engages with source code, using alternative methods of source development, or, perhaps, | ||
manipulation. Specifically, I examine how new-media artist Nick Briz[^briz1] demonstrates a glitch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know that you provide a brief introduction to glitches & glitch art below in the next section, but it seems like this introduction needs its own accessible intro to or overview of glitch(ing). Specifically, you may want to clarify that it's a set of activities that work with code in ways unanticipated or unintended by the original developer(s)--a point of detail that can help set up the discussion of metaplasm and transformation toward which you ultimately work.
No description provided.