Lady @Lady@cat.family

@kit fossil is very concerned with creating an immutable record of code changes, or an accurate depiction of code history, or not “throwing away” data

it takes issue with git rebase, for example, calling it “dishonest” and saying it “omits historical information” https://fossil-scm.org/home/doc/trunk/www/rebaseharm.md

any archivist knows that what you throw away is as important as what you keep. i want full control over the authorship of the code history so that i can publish it as intentional statement, including and up to throwing out and rewriting large parts of it to make more narrative sense. is this “dishonest”? only if your interpretation of the repository is as a factual and immutable ledger of code changes, and not a narrative explanation for how code, in its current form, more or less, came to be. i think the second is the more powerful and useful interpretation, personally

broken code, bad ideas, and dead ends are definitely data, but are they useful data? why is the expectation that repositories preserve these things?

@kit fossil is interesting but unfortunately approaches code repositories in the exact opposite way from how i would want to

@wallhackio i was looking thru photos.app

@wallhackio @aescling no i would just post it to fedi lol

@wallhackio @aescling

@wallhackio @aescling

@wallhackio @aescling i used facebook exclusively to cryptic anime post and instagram exclusively to share weird bits of text pasted over animal crossing new horizons screenshots

@wallhackio @aescling my cousin who liked kill la kill was on there

@wallhackio @aescling it's a screenshot of a text conversation containing a screenshot of a facebook conversation

@wallhackio @aescling watch kill la kill with me bitch

@alyssa @aescling @Satsuma gatita ni siquiera descargó el programa de tarjetas 😔