i just have this dumb little script that i use that huffs my immediate network down into an rdf graph, and then i can do operations (like disgorge the csv files gephi needs to import) from there the new thing, though, is i have it coughing up a proper spreadsheet:

sooo i pulled down my bsky orbit the other day (it looks like this: doriantaylor.com/file/2026-06... —i don't download all the connections because that would be insane) anyway i just hacked the little script i wrote to do this to disgorge a spreadsheet so i can have a better look…

wat about a zune

looks like @stream.place is having a bit of a menty b

qui le porte le mieux

for your next video call

i propose gremlins (this kind)

lol did a new one of these doriantaylor.com/file/2026-06...

this isn't an ideal case, it's an architectural stipulation intertwingler is at root a microservice bus it has transform queues which themselves are implemented as microservices the bus (used to) POST the previous response body to each transform successively but QUERY is better

i suppose; it takes a bit to fill up

get in loser we're going drinking^Wbaseball

what i need is a safe* request method that accepts a request body†, and QUERY (RFC10008) is precisely that * (www.iana.org/assignments/...) †

so, no the requirements for POST to cache (in addition to this) are that the representation would be the same as if you were to GET it for the thing i'm doing i initially had it POST and when i discovered the draft spec (it wasn't an rfc yet) i was like, that is the correct way to do it

and then the computer basically does this

christmas for sickos

my skills at drawing a farting butt have greatly atrophied

lol now running late because i flew out the door with bacon wrapped in butcher paper that i had gotten out to put in a proper bag before heading to gf's for the weekend and realized before getting on the train and had to go back for it

llms for "target generation" is giving

i am surprised and delighted

Brawndo™ The Thirst Mutilator: It's Got What Fish Crave®

…and like i think discussed at some point (i was dozing so i will have to revisit) was how the misunderstandings have to be treated as legitimate interpretations because they'll just (at least attempt to) reify them by brute force

like think about what a pull request is actually saying: • some random person shows up on your doorstep with a package • you don't know what's in the package (yet) • they say please assume custody of this package forever • also, do it now i believe the natural response to an overture like that is