14400+ entries in 0.026s
mod6: i dunno, i guess i could. my understanding was that most of these greenhouses start the seeds in like march time-frame. but maybe i'm way off there.
mod6: well, its pretty much ungrowable until like first week of may here.
mod6: but ~maybe~ next year.
mod6: a little short on space for that. :/
mod6: BingoBoingo: yeah. for now, just learning. was actually thinking, while getting drenched, if I can find a place to start from seeds & get appropriate sun, would do it.
mod6: yeah! man, phesant is excellent.
mod6: got all the tomatoes, basil, pumpkins, eggplants, squash, and r. lettuce planted in the pouring rain. tomorrow: strawberries, watermelon, broccoli, early/late cabbage, short/long cukes, brussel sprouts, and dill
mod6: we're pretty close to the first testing of it in here -- have some loose ends to tie up (the remaining ~20%). if history is any guide, there will be more to do as change requests, etc. but at least we'll have somethign that works.
mod6: shinohai: heh, hopefully by the time we're done there it'll hold together.
mod6: people will be expected to interact {add,edit,remove,view} tickets through tbot - which is probably .. eh, 70% complete.
mod6: so I think, hopefully sometime today, i'll send out t.pl to the ML as is - however i don't really expect anyone to use t.pl themselves. sending it to the ML for more of posterity purposes.
mod6: oh nevermind, i think shinohai has it covered. totally didn't see that.
mod6: anyone wanna help me test the cmd line version of t.pl?
mod6: send your application to me
mod6: built with 'stator'
mod6: i have an openbsd with some custom patches and tweaks.
mod6: <+mircea_popescu> anywya, once mod6 gets that T thing going we can actually create tickets for all this, which'll make the task less insane. << making daily progress!
mod6: to put out the blow torch
mod6: think she wants some water
mod6: think i should get off her first
mod6: soooo i went through the epic headache of setting up sks server on dulap, only to learn that the thing will not work without blessing from existing sks operators. <<< uuuuugh
mod6: was thinking it'd be neat to cross-ref the email to some live twitter acct and tag 'em
mod6: im ciked that phuctor is crushing keys while i sleep, ride the train, eat a sandwich
mod6: anyone outside can get their vpatch "sponsored" after review & needsRebase returns false
mod6: it should be that anyone in L1 can use it really.
mod6: if anyone has some interesting in working on a CI project with ole mod6, lemme know. it'll take some doing, but it could be pretty worthwhile.
mod6: <+shinohai> just as a backup at least cuz i love t so much << ok no worries then, just wanna ensure we're not duplicating work and what not.
mod6: everyone should do these things on their own.
mod6: yah, but this verifies stuff for historical purposes and helps regression test a bit.
mod6: yeah, bunch of stuff there. something to work towards.
mod6: someone drops in their vpatch somewhere, it verifies that it doesn't have to be rebased, then spins up an instance somewhere and builds the full orchastra, and then runs tests against it.
mod6: what i also want to build is a CI thingy for trb
☟︎ mod6: <+shinohai> ;;later tell mod6 my tbot can now add/remove tickets, little ugly but working :D << ah, ok. are you wanting to take yours all the way?
mod6: shinohai: ah cool man.
mod6: i'll work on it a bit more later.
mod6: want a tbot sneak peak?
mod6: anal fisting site should have expected to get their backdoor penetrated
mod6: i've done so much work with peopel over irc or even screen-sharing while remote, this irl stuff is insane
mod6: we'll have to put a flag in here so I can give the details later when I go to next_place. XXX
mod6: and yah phf, that's usually how its done.
mod6: i don't feel the need to try to improve someone else.
mod6: cause whatever, jera
mod6: she's probably better with spring and shit like that than me though.
mod6: phf: i can't stand watching her type. nor her formatting. and she doesn't really understand version control.
mod6: i'd much rather work remote and "pair" that way. it's not super bad or anything, cept for the commute, and not being able to sneak off to tmsr~
mod6: and we're moving too fast to wait for someone to wait for a PR, respond in there and then refactor/rearchitect and update PR
mod6: we're writing a lot of the stuff together so architecture decisions aren't "made in a silo"
mod6: but most of it is like talking through a bunch of shit.
mod6: some tasks are somewhat async.
mod6: peer. so i've been hacking all the code together and 'driving' while she sits there.
mod6: i've been architecting a performance framework
mod6: all day. every day.
mod6: haha. she's been watching me type.
mod6: but since like... at least mid-feb, a lady has been watching my every move.
mod6: when i don't have someone watching my every move during the day, i usually can login and chat during the day at the office.
mod6: worked downtown for a half-day today, wfh rest of day.
mod6: where ``keep it'' invoves doing the hard, useful things that need doing.
mod6: "A republic, if you can keep it"