Consider code of conduct

[ctrlcctrlv]

Recent incidents of trolling around #20 have led me to consider whether or not a Code of Conduct is worthwhile for this project.

I've contributed to a lot of open source projects over the years, both those with CoC's and those without. Personally, I find CoC's to be beneficial. But, this is a sensitive issue. So, what do those who are currently working on this or wish to want?

I think this project is the first one that's become large enough and that I've been in any kind of decision making role to have this discussion.

[dankamongmen]

if you're asking my opinion, i have never thought much of Codes of Conduct, but i certainly won't protest adding one.

i've gotta say, that interaction was a rather shocking one to me -- i hack open source all day, every day, just about, and don't see stuff like that very often.

either way, i'd either add one and close this bug, or don't add one and close this bug, because it's exactly this kind of non-technological thing that people will drop in and ventilate on. =]

[ctrlcctrlv]

@dankamongmen Good to see you online. Do you mind sending me the sixel-encoded graphic mentioned at saitoha#149? I think I fixed the decoder and have a patch ready for PR, but I have no way to test it. The encoder is still b0rked. I'm treating them as separate issues.

[ctrlcctrlv]

My patch fixes the changing palettes issue in the decoder as well. I discovered it was a two for one deal: the root problem is the same in both cases: clumsily juggling palettes.

[ctrlcctrlv]

I mean I suppose I could hand-encode a transparent background Sixel, but it'd be a lot easier just to have one on hand as a test case 😂

[ctrlcctrlv]

Nevermind, figured it out. It's really ugly, much worse than your test case, but behold, the first transparent output from libsixel! :-D