my point is that i’m not actually that worried about A·I gobbling up my posts because i’m pretty sure anyone who tries to use it will consider my influence on the model to be the noise, not the signal
they need massive amounts of data in order to normalize and sanitize out precisely all the weird shit that gets produced by freaks like me
@aschmitz oh i mean i would never give access to anyone i didn’t trust OR put anything sensitive on the server ever OR have any kind of uptime or reliability guarantees, if i were to ever do this, to be clear
for my own purposes, i just run make locally and then rsync. but i think that’s a tiny bit too unstructured to be a shared workflow
i think proper CI/CD pipelines with gitea/forgejo/gitlab/github etc are Fine, but wasteful, and also best to do on their infrastructure and not on a friend’s
i think what i actually want is :—
• A GitWeb instance
• A number of users which only have git access, and only to repositories they own
• A straightforward means of getting new repositories (and corresponding subdomains) allocated to users [this can probably just be manual, on request]
• A post-receive hook in every repository which, if the repository has a file named Makefile or GNUmakefile, clones the repository and then runs `make install DESTDIR=public`, serving the contents of the resulting `public` directory from a corresponding subdomain
• Maybe a small amount of allowable additional server configurations besides
@coriander Safe, Sane, conSenSual Sex??
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.