Skip to content

Latest commit

 

History

History
86 lines (71 loc) · 3.12 KB

README.md

File metadata and controls

86 lines (71 loc) · 3.12 KB
Raw

Babel

Appropriating non-Latin characters (eg: Japanese, Thai, Chinese characters), some tweets create images to express something. The characters are abstracted from their literal meaning and are given a new meaning based solely on imagery. Thus, a new language is formed that is understandable by all-- a sort of pan-humanist language.

The language's "words" have no separation between the word and the meaning. That is to say, the words are self-referential.

This project attempts to create a dictionary for this language. An interface will be created that will crowd-source the creation of this dictionary. The interface shows a new "word" [eg: (∏ ω ∏) ] and Google Image results of that word as a query. Users of the interface are instructed to delete the image results that do not match what the word means. When all of the Google images represent what the word means, the user should "approve" the word, and it will be added to the dictionary. If no images ever represent the word, the word is rejected.

Later, the dictionary can be viewed.

This, of course, is entirely gratuitous, as there is no need for a dictionary for a language of this sort. (Just realized this. Fuck.)

Tweet Filters: Rules for what to filter out

  • Strings of a-z characters (uppercase and lowercase) that are 2+ characters long
  • Strings of 0-9 numerals that are 2+ characters long
  • Parentheticals, quotes, & brackets that contain strings of characters/numerals as described above (ie: if the above strings are enclosed in parentheses, quotes, or brackets, remove the string and their container)
  • Usernames: strings of a-z 0-9 characters following an "@"
  • Retweet formats:
    • RT @___
    • RT @___:
    • RT @___: "
    • "@___
    • " @___
    • Probably all quotes should go (not necessarily the contents of the quotes, but the quotes themselves)
  • Links
  • Standard emoticons:
    • :) / :-)
    • :( / :-(
    • :'(
    • :*
    • ;)
    • ;*
    • :o / :O
    • :D
    • D:
    • :p / :P

Regular Expressions for filtering

  • Retweet Formats: /(RT:?["'\s]{0,2})?(@[a-zA-Z\d]+[:\s"']{1,3})?/g
  • URLs/Links: /(?i)\b((?:https?://|www\d{0,3}[.]|[a-z0-9.\-]+[.][a-z]{2,4}/)(?:[^\s()<>]+|\(([^\s()<>]+|(\([^\s()<>]+\)))*\))+(?:\(([^\s()<>]+|(\([^\s()<>]+\)))*\)|[^\s`!()\[\]{};:'".,<>?«»“”‘’]))/g
  • LtoR Emoticons: /[:;][\-']?[\)\(\[\]\{\}\*oO0DpP]/g
  • RtoL Emoticons: /[D\(\)\[\]\{\}][\-']?[;:]/g

Personal Notes for creating keys at school

This is just a sample project to get the students in a guest lecture at Cooper Union going with GitHub and Heroku.

//Create Keys ssh-keygen -t rsa

heroku login //login

//Clear your previous keys heroku keys:clear heroky keys:add chose the id_rsa key

//cd to the directory cd ~/documents/_tcp/cooper-union-class

//create new heroku instance heroku create

//salt n peppa - push it git push heroku master //where "master" is the branch you want to push