Journal of (Generative) Punk (Pixel) Art

Best of ("Hall of Fame" of) Punk Writing

July 2022

Inside The Hair Colors of Punk Pixel Characters / Heads - Are Blonde Punkettes Having More Fun? by Gerald Bauer (Crypto Punk's Not Dead)

June 2022

The early history of [Non-Fungible] Tokens, part 4: [24×24px] Game Sprites on the Blockchain: [Matt & John's®] Punks [V1/V2] by Amy Castor and David Gerard (Free Book Chapter Early Access Draft) - Bonus: Article Review / Commentary

May 2022

Digital artists' post-bubble hopes for [non-fungible] tokens don't need a blockchain by Molly White - Bonus: Article Review / Commentary

Marilyn and Punks and Art, Oh My! by Sean Bonner (Photographer) - Bonus: Article Review / Commentary

A [Cryptp Bro & Serial Fraudster] Builder's Journey by Anonymous Azuki's Zagabond - Bonus: Article Review / Commentary

Bored Apes & Monkey Selfies: Copyright & Profile Picture [Non-Fungible] Tokens (PDF Download ~3.1MB), by Alfred 'Dave' Steiner (Meister & Steiner), 14-pages (via SSRN)

February 2022

Are Cryptopunks Copyrightable? (PDF Download ~7.5MB), by Brian L. Frye ( University of Kentucky - College of Law), 21-pages (via SSRN)

November 2021

The 10,000 [pixel punk] faces that launched an non-fungible [art] token revolution by Sandra Upson (Wired)

Oktober 2021

What I learned from building an on-chain ecosystem for CryptoPunks by Anonymous Punk Programmer (Lost Punk Society)

Pixel art HOWTO series - The making of Adam (24x24 pixel punk) from scratch / zero using pixel art designs in the ASCII text format by Gerald Bauer (Crypto Punk's Not Dead)

August 2021

Punks - The Free White Label Quick Starter Edition - (Re)create from zero / scratch a pixel-perfect copy of the 10 000 CryptoPunks collection (Anno 2017) by Gerald Bauer (Crypto Punk's Not Dead)

Inside the CryptoPunksData contract - Decoding the on-chain assets (11 archetypes and 122 attributes) and color palette for easy (re)use "off-chain" by Gerald Bauer (Crypto Punk's Not Dead)

On-chain Cryptopunks - The Cryptopunk images and their attributes now live on-chain! by Matt Hall and John Watkinson (Larva Labs)

July 2021

Creating a 10 000 [non-fungible] token avatar collection - step-by-step by Jeremy Posvar (Expansion Punks)

April 2021

The Cult of CryptoPunks - Ethereum's 'oldest [non-fungible] token project' may not actually be the first, but it's the wildest by Lucas Matney (Tech Crunch)

Christie's Art Auction House - 10 things to know about CryptoPunks, the original [non-fungible] tokens by Christie's - For the first time, 5,184 pixels' worth of a revolutionary [non-fungible] token project will go up for auction at a traditional auction house, courtesy of the project creators and pioneers themselves

June 2017

This ethereum-based project could change how we think about digital art. Yes, you can actually own these digital creations. by Jason Abbruzzese (Mashable)

January 2012

Who Owns an Avatar?: Copyright, Creativity, and Virtual Worlds (PDF Download ~1.7MB), by Tyler T. Ochoa (Santa Clara University School of Law), 35-pages (via Santa Clara Law Digital Commons)

Questions? Comments?

Post them on the D.I.Y. Punk (Pixel) Art reddit. Thanks.

punks.journal's People

Contributors

Stargazers

Watchers

punks.journal's Issues

Feedback on why-the-stdlib-is-broken

Hi! Reading through why-the-csv-stdlib-is-broken.md and reading the code examples, I think you'd get a lot of value out of a gem I maintain, Seeing is Believing. Here's a video showing how much easier the code samples could be than what you're probably doing now:

https://vimeo.com/287668754

Also, the published version of the gem has lots of print statements in it. Eg when I run the first example in the readme, it comes out like this:

If you want some suggestions on the code, LMK :) I don't want to come in and shit on things, b/c I also would like a better CSV lib, but kind of skimming through, there's a number of ways to make kind of annoying things a lot simpler, and it's not following gem etiquette on namespacing.

Maybe a last thought: you make a lot of good points, but a mandatory feature of a CSV lib, for me, is that I can use it in a streaming manner (eg process lines as they become available and emit them as they are processed). I can do that currently with the stdlib's CSV, csvreader will need this feature if it wants to compete.

require 'csv'

read, write = IO.pipe
csv = CSV.new read

write << "1,2,3\n4,5,6\n"
csv.readline # => ["1", "2", "3"]
csv.readline # => ["4", "5", "6"]

write << "7,8,9\n"
csv.readline # => ["7", "8", "9"]

Recommend Projects

cryptopunksnotdead / punks.journal Goto Github PK

punks.journal's Introduction