@akjcv@types.pl the default stance should always be to not archive and archiving should have to be justified on a case-by-case basis, as a general principle
no data is secure and no machine connected to the internet is private
that’s not to take the extreme stance that nothing should ever be recorded, but recording a significant quote somebody said to you in your journal is different than keeping a continuous record of everything they have ever said, and the fact that it is easier to do with computers doesn’t change the ethical considerations with it
@coriander tobacco road by common market
actively requiring documents to be served with a media type of application/xml instead of a more specific media type: why
@wikipediahaiku both senses of “virtually” here are good
the #lycanroc tag is full of people who want to fuck her
i’m running a code sharing service for humans here, not a piece of computing infrastructure; if you want reliable computing infrastructure i encourage you to manage your own repo on your own platform
why? because i’m not interested in hosting broken code, and because you should be using hashes not tags for anything you need an immutable identifier for
“but using a hash doesn’t help if that hash ceases to be available” i’m not interested in hosting broken code
my git policy by the way is that versions before the latest are immutable; anything goes after that point
i can and do retag latest versions and do fixups on them
there are lots of new features i want to add, some of which are really useful!! but i’m refusing to do so until i have a proper release of what i have
Administrator / Public Relations for GlitchCat. Not actually glitchy, nor a cat. I wrote the rules for this instance.
“Constitutionally incapable of not going hard” — @aescling
“Fedi Cassandra” – @Satsuma
I HAVE EXPERIENCE IN THINGS. YOU CAN JUST @ ME.
I work for a library but I post about Zelda fanfiction.
For the time being, this is mostly a mirror of <https://status.ladys.computer/>. Want to get in touch? E·mail me!