5900+ entries in 0.02s
Framedragger: but i have to stop presenting ideas i do not really believe in myself. i guess i thought it may garner some useful feedback tho.
Framedragger: mircea_popescu: secret bot is an irc user in a channel which no-one knows to be a bot (or a bot of particular use). scriba also has that kind of hostmask (unaffiliated/framedragger/bot/scriba) but everyone knows what scriba is for.
Framedragger: but it appears the whole range thing fucks things up too much to be useful
Framedragger: oh yeah. i'm there for the lulzy headlines. but you're right asciilifeform
Framedragger: *sigh*. "that's boring". no, you're right, i agree.
Framedragger: it's not really reliable. but i may just be doing that slippery slope insane adversary thing myself here. :/
Framedragger: thru other services and just plain syn flood or w/e
Framedragger: of course of course; but as was stated multiple times, it's about making things more *difficult* / costly for adversaries. you can always slippery slope into "such powerful adversary with infinite motivation" and win the argument - and that's legit, sure
Framedragger: not in terms of bigbro collection stuff, but in terms of making it more difficult to ddos
Framedragger: the "but kant" homage to mp (maybe?) made me lol btw :D
Framedragger: eh, the chan is educational and therefore useful on that merit alone, and that's nice
Framedragger: ah damn i must have heard of him in a lithuanian context but i probably know nothing of him, even though evidently i should. /shame
Framedragger: there could be multiple monstrosities like this, tho!
Framedragger: i think my tolerance levels are (finally) decreasing in some kind of accelerated fashion, hopefully in line with growing experience, but there's still ways to go. but yeah, war it is
Framedragger: asciilifeform: "Everything pertaining to Automake was nuked" - so nice. i used to doubt (or maybe i still do - in itself a healthy habit, perhaps) whether i didn't *get* something fundamental in modern s/w development. (maybe i still don't, of course). "shitloads of build targets and convoluted build chain? maybe there's no way more elegant? i must be a truly stupid person."
Framedragger: that does sound like a plan. total failover scenario #1 recorded, then
Framedragger: also, while it's not exactly contradictory it's still funny what status bitcoin holds in tmsr's infrastructure, while being based on EC
Framedragger: fwiw iirc that lib exposes abstracted parts; but, yeah, no easy way to change those internal parts
Framedragger: dude, a first-on-the-planet decent cryptolib would be nice
Framedragger: yeah that i really like. reminds of that bitcoin wallet spec - no non-ascii parts
Framedragger: but in all seriousness, i'm a bit afraid, but it may be good education for me. not that i see this as a game to be fucked up at the first step
Framedragger: i heard there was, like, a way to, like, store results from a dynamic system, to be served in a static manner
Framedragger: they become submissive by entering mp aura zone
Framedragger: nasa's coding manual (which doesn't allow recursive code - because the rovers are, you know, sorta far away, and you write in a turing complete language) may have it - i wonder
Framedragger: look at that one person knows to actually include human readable timestamp into the inside of a pgp signed message which deals with timing-sensitive info!!!
Framedragger: mircea_popescu: no disagreement there; just pointing out that sometimes small arrangement disagreements still prop up; say, different order of variable initialization (which otherwise bears no actual significance); etc. of course one *could* have a convention spec so precise taht it would include things like "if there is arbitrary order of initialization of $x then default to alphanumerical order".
Framedragger: cosmetic conflict = differently arranged lines or multiple implementations of some simplistic algorithm; overusing the whole "develop in multiple branches and merge things and stuff" thing. sorry - multitasking; trying to eradicate this habit fwiw.
Framedragger: i understand that i'd be more internally..consistent if i just ditched the *whole* thing, however.
Framedragger: well fwiw i'm not overusing it. i don't subscribe to the "resolve cosmetic conflicts by doing more redundant work" thing, either;and i don't do it
Framedragger: "overengineering minutia and spending cognitive resources on bullshit" - maybe
Framedragger: you may be just right; fwiw i have the same inkling feeling, hm
Framedragger: i don't see why this necessarily yields some kind of conceptual moral failure or whatever
Framedragger: mircea_popescu: you mean in the sense of a logical "third"? i'm not sure. i guess i get it conceptually, re. conflicts; but on a more mundane practical level, conflicts happen because, say, two people implemented some particular thing a bit differently; or their feature touched upon code from another place which was also being worked at; whatever
Framedragger: right. i *think* i get it. i mean, fair enough. and i should try to publish with it huh.
Framedragger: shit, i just got what you're trying to say - i'm slow. it's only a publishing mechanism. how to collaborate internally is another matter. yes, nice separation of concerns. (though i suspect people have thought how to do proper collaboration in V as well - emails with vdiffs etc)
Framedragger: (i understand it's not supposed to make any wanna-be-git development easy)
Framedragger: right. perhaps it's a matter of writing scripts to automate this stuff for V.
☟︎ Framedragger: 2) while automatic merges mask deeper problems (as trinque may have implied) and may or may not be cancer, having many developers be able to work on the same codebase and later easily solve code conflicts is fucking *great*
Framedragger: 1) you may want to retain several versions of the thing you're developing - production, testing environment, development, some-large-feature-im-working-on-thats-currently-breaking-everything
Framedragger: mircea_popescu: there is an implied assumption here of a "large enough" codebase (deliberately vague quantifier here). why i'm using it for scriba: 'cause i like it; and the latter's not a great argument. *but* if you have a large enough project with multiple people working on it, then:
Framedragger: mircea_popescu: gotcha. will simply things. unnecessary complexity indeed
Framedragger: mircea_popescu: just so you know, no need to manually alter urls yourself anymore. unless you have a fetish for that, of course!
Framedragger: i do see your point. and, sure, branches are pointers to heads
Framedragger: ftr there's now a kind of deployment process so i have to make changes in dev branch, make a commit, and then pull from a separate repo which has the dev branch as its upstream. AND I LIKE IT THAT WAY!!1
Framedragger off for now, sorry for pollution; good day for the logs
Framedragger: trinque: ok maybe. but the restriction is an easy way of trapping some non-halting scenarions
Framedragger: trinque: you mean, it's okay for bot to keep repeating same line requested by same person in quick succession? hm maybe
Framedragger: there should be a bot which gives help about bots