tmsr - Search: UCI

211 entries in 0.849s

mircea_popescu: asciilifeform yes, they have. it's called uci.

mircea_popescu: if we had the uci ready, we could run republican dns on these.

asciilifeform: they're running obummer's uci.

mircea_popescu: should have prolly run uci on them rather. but of course no uci yet.

mircea_popescu: i jus' did, and best i can see it is sufficient, and how we'll do stuff like rsa encryption/decryption over uci once gossipd is here.

mircea_popescu: i'm not interested in the branching, will be happy to have a bignum machine that's securely separable via uci.

mircea_popescu: in other words : paillier in UCI over gossipd seems capable of bignum.

mircea_popescu: i have nfi what you're on about. again : i want to multiply C1 by C2. I fire up the UCI, i ask C2 processes to add C1 to the result of the previous process adding C1 to the result of the...

a111: Logged on 2016-10-19 14:19 trinque: mod6: I'm considering bringing up common lisp UCI nodes once payment is done

trinque: mod6: I'm considering bringing up common lisp UCI nodes once payment is done ☟︎

tb0t: Projects: UCI | t | trb | v

mircea_popescu: mats no, the unobvious part in all that is, i suppose for lack of vocal underlining, the owner. in the uci model, any individual piece of hardware has one owner, who makes it available through the uci, sets the prices, etc ; and some tenants.

trinque: mats: seems moar like you'd pay per request of whatever is offered through the UCI

mats: on a different subject, i admit i have trouble imagining how to make uci useful

trinque could not be more enthusiastic about joining the UCI conversation when he tires of beer and beauty, bbl!

trinque: asciilifeform: UCI is a replacement for AWS or "hosting" or "computing for hire" or whatever you like; comparing it to your beloved home "ox" is ridiculous

mircea_popescu: this is neither here nor there, inconvenient as it may be, it has no more bearing on uci than it has on hypocaloric diets.

mircea_popescu: that's one level. and it informs the practical definition of uci, an implementation thereof, as you quote it.

asciilifeform: it is worth thinking about wtf the point of uci was

mircea_popescu: you want contact to my uci interface, we agree in advance, and i whitelist your key.

asciilifeform: the important thing is that usg's 1,000,000,001 emulated uci sybils should have no bearing on the workings of genuine nodez.

mircea_popescu: fundamentally uci is a lateral pill for the hardware problem, oddly enough.

mircea_popescu: "is your dec alpha/toaster/bitcoin miner pluggable into uci ? cool, then it makes money. no ? it's broken fix it"

mircea_popescu: the whole point of uci is for there to be no more platform in that sense. course, this seems an unlikely goal.

mircea_popescu: anyway. uci is not gossipd. there is a good reason to implement gossipd OVER uci, but on the uci layer the thing shouldn't be concerned with this kind of security i don't thinl

asciilifeform: there are 2 basic angles to approach uci : the standard botnet model, which appears to be what mircea_popescu is thinking of, where nodes are individual boxes running specific program that does fairly straightforward thing,

mircea_popescu: then uci responds with "script ran, results os and so, paqy here"

mircea_popescu: ie, uci admin thing advertises what it does, gets an order.

ben_vulpes: how would someone in the wot interact with the uci; operation by operation over irc? shoop a script in uciasm for execution and billing upon completion?

asciilifeform: mircea_popescu: speaking of uci, ever consider generalizing luby's algo to ~calculation~ ?

ben_vulpes: mircea_popescu: http://thebitcoin.foundation/tickets/UCI_tickets.html#6 << what all would be encompassed by 'networking'?

ben_vulpes: 2020 something something egalitarian treatment of UCI nodes

a111: Logged on 2016-06-09 23:02 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 accept

mod6: <+mircea_popescu> also important, suppose i want to split up a ticket later. what should i do, delete and re-enter ? << so saythat UCI ticket 7 needs to become two seperate tickets and the original didn't capture what it was supposed to capture; i would just make a new ticket, and then edit the existing one to reform what would be or seem correct.

mircea_popescu: (uci) -> (gossipd) -> (user).

mircea_popescu: the obvious pill being, of course, point to point encryption via uci on top of end to end encryption via gossipd.

mod6: which is why I think your graph for UCI is correct.

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: %p UCI 7

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,

mod6: %p UCI 8

mircea_popescu: but not exactly see, because for instance in uti oops i mean uci thing : 4 doesn't block 7 if 3 is present say.

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.

mod6: %p UCI 2

davout: http://btcbase.org/log/2016-06-09#1479673 <<< it does, however when i look at http://thebitcoin.foundation/tickets/UCI_tickets.html it seems to me #7 should be an antecedent of 3,4,5,6 but not the other way around ☝︎

mircea_popescu: "apparently an intern installed uci. it's the third time this week."

a111: Logged on 2016-06-09 22:59 mircea_popescu: %add UCI F "Create UCI worker for Windows (10, 7, 8/8.1)" "Worker should interface with kernel, execute all UCI commands, meter resource usage."

mircea_popescu: http://thebitcoin.foundation/tickets/UCI_tickets.html << only 4 tickets oddly.

mod6: %p UCI 8

mod6: %p UCI 7

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.

mod6: %p UCI 6

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.

mod6: %p UCI 5

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.

mod6: %p UCI 4

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.

mod6: %p UCI 3

mod6: %p UCI 2

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.

mod6: %p UCI 1

mod6: %p uci 1

trinque: seems you could execute things on a variety of UCI workers and compare results

mircea_popescu: %p UCI 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 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

mircea_popescu: %p UCI 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 ☟︎

mircea_popescu: %p UCI 7

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.

mircea_popescu: %p UCI 6

mircea_popescu: %add UCI F "Create UCI worker for Embedded/ARM" "Worker should interface with kernel, execute all UCI commands, meter resource usage."

mircea_popescu: %p UCI 5

mircea_popescu: %add UCI F "Create UCI worker for Mobile (Android, iOS/OS X)" "Worker should interface with kernel, execute all UCI commands, meter resource usage."

mircea_popescu: %p UCI 4

mircea_popescu: %add UCI F "Create UCI worker for Linux (Ubuntu, Debian, Mint, Fedora, Centos etc)" "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.

mircea_popescu: %p UCI 3

mircea_popescu: %add UCI F "Create UCI worker for Windows (10, 7, 8/8.1)" "Worker should interface with kernel, execute all UCI commands, meter resource usage."

mircea_popescu: %p UCI 3

mircea_popescu: %r UCI 4

mircea_popescu: %r UCI 3

mircea_popescu: %p UCI 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.

mircea_popescu: %p UCI 4

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.

mircea_popescu: %p UCI 3

mircea_popescu: %p UCI 2

mircea_popescu: %p UCI 6

mircea_popescu: %add UCI F "Create UCI worker for Embedded/ARM" "Worker should interface with kernel, execute all UCI commands, meter resource usage."