Lady @Lady@cat.family

@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 have some good makefiles you can use; this gets you a lot

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

@aescling you should start a tilde town

i don’t want to operate a tilde town, but i do think all of my friends should have a server they can rsync files to and have them appear on the web

apparently i can process a .5MB TSV with xsltproc extremely quickly with no problems

this xml file is going to end up like half a megabyte and i have a dayjob

@alyssa i think the real problem might be less the pokémon and more the moves; they should make better bug moves and let the bug pokémon use them

@alyssa they should reflect this in the game mechanics and Yet

niantic add Any good bug or poison pokémon to pogo challenge

@aschmitz i am very disappointed in the state of XML parsers as well ​

@aschmitz the other best‐practice with noncharacters is to never store them in a place where anyone other than the program which understands their meaning will see them

having the noncharacters produce XML which isn’t valid provides a bit of a guarantee against that; a downstream recipient SHOULD error out if it receives a document where the noncharacter wasn’t handled/removed

@aschmitz usually the best‐practice as i understand it when using noncharacters (which FFFE and FFFF are) is to first search for them in the string and replace any existing ones with FFFD

this would need to happen to make the XML valid anyway, so that seems acceptable to me; i agree that in the general case you probably shouldn’t assume valid input tho

@aschmitz (well, do not use U+FFFE in a UTF‐16 environment where it might be confused for a byte‐swapped U+FEFF)

@aschmitz U+FFFC is allowed in XML documents; i need a character which is NOT allowed in XML documents but which is still a valid Unicode character

there are three of these: U+0000 (not ideal), U+FFFE, and U+FFFF (both of these last two are great)