294300+ entries in 0.183s
a111: Logged on 2016-06-09 23:06 mircea_popescu: do anything you damn well please - from hosting your (uninterdictable) website on half a million random machines
to nuking whitehouse.org
a111: Logged on 2016-06-09 23:04 mircea_popescu: does
this make sense
to anyone outside of yours
truly ? asciilifeform ? davout ? jurov ? phf ?
trinque ?
mod6: i probably could/should have all of
the
tickets clumped under one
tree. but i need
to work on
the
tickets and ordering etc.
mod6: its hard because
there are like a number of disconnected graphs, or hard because of mental gymnastics? i'd like
to make it better, so your input helps.
shinohai: Since we finished
the rss
thing last night, I'm already working on a new one xD
trinque: mircea_popescu: mike_c
told me he was able
to connect
to my db; subsequently haven't heard from him
mod6: watch out or you'll start writing #!/usr/bin/perl all
the
time
shinohai: Well
this place has kinda mrphed into full-time between Bitcoin and Qntra lol
mod6 turning people
to
the dark side, one at a
time.
mod6: much more
to come / work on.
mod6: salud; now
that we've got a
ticketing system, we can see how much
there really is
to do still! haha.
shinohai: Glad
to have been help and not hindrance ... 'twas an honour
to participate.
mod6: Couldn't have done it without you
though,
thanks for all
the
testing help. Most sincerely.
shinohai: btw mircea_popescu "Pace in our
Time!" good one
☟︎ mircea_popescu: mod6 anyway, go ahead an' write it up, i already did a qntra
today
a111: Logged on 2016-06-09 23:39 mod6: I feel like we've needed
this
tool for some
time as he was only needing a way
to
track and graph
the work required.
mod6: unless mircea_popescu wants
to have
the honor,
then by all means.
mod6: he'll get back
to us, im sure its fine.
mod6: jdawg: does
that work ok?
mod6: Ah, he's
the man on
that
then, ok.
mod6: But I'll
take a shot at it I guess as long as
the proceeds can be donated
to
The Bitcoin Foundation.
BingoBoingo: mod6: Well I asked
the question in case you or mircea_popescu wanted
to have
the honor of writing up
T mod6: I feel like we've needed
this
tool for some
time as he was only needing a way
to
track and graph
the work required.
☟︎ mod6: BingoBoingo: did you read
these
tickets? don't miss out on Mr. P.'s vision for
TMSR~ here in
the story.
mod6: and as we start
to work on
these features, it is meant (at least by me)
that
tasks and other atomic work will be children of
the features.
mod6: your
tickets are awesome btw
mod6: that might make it
that much more clear.
mod6: but
to me looks like everything goes
the right way, and dependentcies are in
the correct direction
mod6: i guess
this can be re-worked if it invokes
too much mental gymnastics.
mod6: this looks right
to me
mod6: so yeah, we start with a large chunk, and it breaks down
to smaller chunks.
mod6: and
the same for 3, 4, 5
mod6: so for
ticket 6, i may have put in its antecedent as 7
mod6: yah, i kinda modled it after how
the
tree looks for V.
mod6: and
the 5, 6, 4, 3, are
the leaves
mod6: ok
then
that should be fine it kinda looks funny i suppose. but 1 is
the root.
BingoBoingo: So who is writing up
the Qntra "T Ascendant"?
mod6: so
ticket 1 is a saga, which can't be complete until 8 is complete, correct?
mod6: hm. so is
ticket 1 an antecedent (parent) of
ticket 8?
mod6: the next update ~should~ contain
them all.
mod6: probably because it was related
to
the
timing of entering
the
tickets.
mod6: i'll check into
that.
mod6: ah, yeah, ok. i see all of 'em came in at nearly
the same
time. should have handled it, but looks like it got a bit confused.
mod6: ok, yeah, i see all of
those in
the file. lemme see what happened when you were entering 'em.
thanks for doing
that, might be a weird
timing issue or something, not sure.
tb0t: Project: UCI, ID: 8,
Type: F, Subject: Create UCI supervisor, Antecedents: 2,7, Notes: Interacts with UCI worker
through interface ; interacts with peers
through #trilema standard bot. Maintains list of prices for exposed abilities and Bitcoin address for payments ; list of
trusted peers for accepting orders and verifying Bitcoin payments ; administrative policies as appropriate. Directs worker
to execute accepted commands,
tb0t: Project: UCI, ID: 7,
Type: I, Subject: Research and design UCI/worker interface., Antecedents: 3,4,5,6, Notes: UCI element should expose significant portions of native ability (at a very minimum networking ; math processing - CPU and VidCard ; storage - RAM and HDD)
through an unified, lightweight interface. Feature load less important
than simplicity.
tb0t: Project: UCI, ID: 6,
Type: F, Subject: Create UCI worker for Embedded/ARM, Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: Project: UCI, ID: 5,
Type: F, Subject: Create UCI worker for Mobile (Android, iOS/OS X), Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: Project: UCI, ID: 4,
Type: F, Subject: Create UCI worker for Linux (Ubuntu, Debian, Mint, Fedora, Centos etc), Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: Project: UCI, ID: 3,
Type: F, Subject: Create UCI worker for Windows (10, 7, 8/8.1), Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: Project: UCI, ID: 2,
Type: F, Subject: #trilema standard bot, Antecedents: , Notes: Should be capable of maintaining connection
to channel ; interfacing with deedbot ; interfacing with Lordship/voiced users.
tb0t: Project: UCI, ID: 1,
Type: S, Subject:
TMSR's own Unified Computing Interface, Antecedents: 8, Notes:
The goal of
TMSR as far as computing is concerned is
to deploy a cheap, effectual, networked computing interface
that can not be disrupted significantly under any circumstances by any adversary for whatever reason.
tb0t: No such
ticket was found with id: 1.
mircea_popescu: map
the entire dns system, eavesdrop
the entire internet, create your own dns, launch satellites and nukes (hey, who's
to say what peripherals a given machine has, amirite ?), whatever.
mircea_popescu: do anything you damn well please - from hosting your (uninterdictable) website on half a million random machines
to nuking whitehouse.org
☟︎ trinque: I recall
the last
thread about
this
trinque: seems you could execute
things on a variety of UCI workers and compare results
mircea_popescu: does
this make sense
to anyone outside of yours
truly ? asciilifeform ? davout ? jurov ? phf ?
trinque ?
☟︎☟︎☟︎ tb0t: Project: UCI, ID: 8,
Type: F, Subject: Create UCI supervisor, Antecedents: 2,7, Notes: Interacts with UCI worker
through interface ; interacts with peers
through #trilema standard bot. Maintains list of prices for exposed abilities and Bitcoin address for payments ; list of
trusted peers for accepting orders and verifying Bitcoin payments ; administrative policies as appropriate. Directs worker
to execute accepted commands,
mircea_popescu: %add UCI F "Create UCI supervisor" "Interacts with UCI worker
through interface ; interacts with peers
through #trilema standard bot. Maintains list of prices for exposed abilities and Bitcoin address for payments ; list of
trusted peers for accepting orders and verifying Bitcoin payments ; administrative policies as appropriate. Directs worker
to execute accepted commands, returns results
to peer." 2,7
tb0t: No such
ticket was found with id: 8.
mircea_popescu: %add UCI F "Create UCI supervisor" "Interacts with UCI worker
through interface ; interacts with peers
through #trilema standard bot. Maintains list of prices for exposed abilities (in satoshi/Gb/second of storage for instance) and Bitcoin address for payments ; list of
trusted peers for accepting orders and verifying Bitcoin payments ; administrative policies as appropriate. Directs worker
to execute accepted commands, retur
☟︎ tb0t: Project: UCI, ID: 7,
Type: I, Subject: Research and design UCI/worker interface., Antecedents: 3,4,5,6, Notes: UCI element should expose significant portions of native ability (at a very minimum networking ; math processing - CPU and VidCard ; storage - RAM and HDD)
through an unified, lightweight interface. Feature load less important
than simplicity.
mircea_popescu: %add UCI I "Research and design UCI/worker interface." "UCI element should expose significant portions of native ability (at a very minimum networking ; math processing - CPU and VidCard ; storage - RAM and HDD)
through an unified, lightweight interface. Feature load less important
than simplicity. " 3,4,5,6
tb0t: Project: UCI, ID: 6,
Type: F, Subject: Create UCI worker for Embedded/ARM, Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: Project: UCI, ID: 5,
Type: F, Subject: Create UCI worker for Mobile (Android, iOS/OS X), Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: Project: UCI, ID: 4,
Type: F, Subject: Create UCI worker for Linux (Ubuntu, Debian, Mint, Fedora, Centos etc), Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: Project: UCI, ID: 3,
Type: F, Subject: Create UCI worker for Windows (10, 7, 8/8.1), Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: No such
ticket was found with id: 3.
tb0t: No such
ticket was found with id: 5.
tb0t: Project: UCI, ID: 4,
Type: F, Subject: Create UCI worker for Embedded/ARM, Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.
tb0t: Project: UCI, ID: 3,
Type: F, Subject: Create UCI worker for Embedded/ARM, Antecedents: , Notes: Worker should interface with kernel, execute all UCI commands, meter resource usage.