71400+ entries in 0.504s

davout: design
a way for them to talk together
davout: yeah, take
a few trbs and cut different parts from each basically
davout: and even if single binary, still sounds like
a large architectural rewrite
davout: well, as i understand it the end result is
a different set of binaries that talk together through
a $to-be-defined queue mechanism
davout: so now, re your description, i'm not sure what
a good start would be, because cutting it the way you described sounds like
a mega-project that encompasses more than the mere wallet
davout: which allowed any existing node to trivially serve any arbitrary wallet, at the cost of
a 2gb memory scan for unspent outs
☟︎ mircea_popescu: keeping
a pile of ALL utxos, as the alternative, is not very good, because you end up storing
a bunch of (potentially toxic) crap
mircea_popescu: i don't see the user has
a leg to stand on, "i'm not sure which my addresses are". if you add some - there's
a (minor) penalty.
davout: mircea_popescu: i agree that the description made in the convo you linked is
a very desirable target architecture
mircea_popescu: i also recall
a thread re how to do this with maybe mimi or else deedbot, which i don't think is that one
a111: Logged on 2017-01-27 19:00 davout: thestringpuller: UTXO set is ~2gb tops, indexing might be nice but necessary to scan for UTXOs that match
a given set of addresses, also the wallet part can cache them if that particular wallet is the only one able to actually spend those UTXIs
mircea_popescu: did what you have in mind come from
a discussion here at any point ?
mircea_popescu: Framedragger they have
a point, indians don't do unit tests.
mircea_popescu: i suppose the fellow who was looking to be useful could write
a phuctor - confirmed - by - wikileaks piece for qntra.
mircea_popescu: in fact -- if ANY professor is better through video than writing, and i don't mean better overall - if he is better in any one definite way, then THEREFORE that person is not
a professor but
a hunting dog.
mircea_popescu: i don't give
a shit. there's
a woman on her knees polishing my floor as we speak. you propose her trade is academic also ?
Framedragger: (not implying that there's much worth for any noob to start running
a tor node *now*.)
ben_vulpes: in more lcs gold:
http://archive.is/XcC3N << not only are the damned things made of paper and disintegrate as soon as you drop them in the water, but the amount of money that the usg.navy has burnt on them is actually so embarrassing as to be worth
a classification fight
mircea_popescu: fig 7 directly what you'd expect based on the competent discussion of "What is
a timer"
Framedragger: i wonder how well
a typical hashtable with 2**64 elements work in practice, tho. where would store its elements?
mircea_popescu: 64 SEEKS. thousands of asm lines. all i do is
a mult. one.
Framedragger: i mean, i have in mind an 'actually properly configured static site'. maybe it's
a nonexistent spherical cow in vacuum, sure.
Framedragger: trinque: point taken. :) (i'll only repeat one thing here: in
a 'proper static site' setup, one is *not* exposing vulns of
a scripting language to the web. only those of the webserver.)
trinque: Framedragger: oh also, take
a look at the history of exploits against python sometime.
trinque: if you're sitting there saying "huh, now my writes take
a year because I have to update sidebar comments on every page I ever wrote"
trinque: as always with tools, there is not
a one-size-fits-all rule to be dumbly applied
Framedragger: btw, if you store 2**64 nodes in
a (balanced) binary tree, wouldn't the "number of seeks" be ~64? i suppose that doesn't look too pretty, but considering that an ssd's seek time is ~0.1ms... not that these numbers are rigorous or anything.
mircea_popescu: neways ; i shall be back to town. anyone wanting to argue the above -- in
a few hours.
Framedragger: right, basically i'm putting
a lot of trust into fs, fundamentally. hence disagreement - fair enough. (to summarise.)
mircea_popescu: Framedragger imagine you have
a 64 bit maxint stored as binary tree (provedly - fastest) and now you seek... how many nodes ?
mircea_popescu: it's certainly and always larger. but whether it's faster is
a harder problem.
Framedragger: ...that's why it's great to host this on
a disk with great random access times.
Framedragger: first off, the former has
a less clear attack surface, may depend on script in question, etc. second off, may scale not as well (no this is not the same as kiddie complaining that an rdbms is "not web scale").
mircea_popescu: what is the cogent difference between these symbols, "script-specific php processes" and "
a standardised additional unit of its resources" ?
Framedragger: well, the compression-decompression process is so to speak serialised / offloaded to an fs. not
a bad thing!
mircea_popescu: in your flat scheme, the words "Trilema -
a blog by mircea_popescu " would appear... 72k times!
Framedragger: i can't see how i can be convinced that launching script-specific php processes is ~same as
a webserver allocating
a standardised additional unit of its resources (memory / thread etc.)
Framedragger: right, well-managed permissions ensure that any 'break-in' would only result in one being able to *read* some files. but i think your abstraction breaks quickly: i'm sure your php user is able to write files (file upload), even if to
a single dir, and to write to db. so it's still not the same.
mircea_popescu: and the notion that you won't expose the language to the web is not equivalent to the actuality that you opt to use such
a banal language nothing can be done which to your mind is equivalent to "not exposing". the man who doesn't lock his door because his chamber contains no maid is not the same thing as the man who doesn't lock his door because his maid is more danger to the youths about than they to her.
Framedragger: as regards language choice, yeah, i see your point, "just use the right tool". thing is, with an *actual* static site, you would not expose the language to the web, at all. the only attack surface would be that of the webserver. cf.
a wordpress site which as folks say is
a "web shell with blog functionality on the side" :)
Framedragger: mircea_popescu: that's not the only difference.
a 'php' site launches and runs additional process(es) to serve user requests. now i guess you could say that "it's just
a detail", on the grand picture it's the same (nginx requires additional resources to serve static files), but that would be stretching it.
mircea_popescu: that you go fd.com/article/comments/5/reply/ or somesuch and i go mp.com/article/ is not so much
a difference as it appears.
mircea_popescu: turn it any way you want,
a flat, disk-bound website IS in point of fact
a "dynamic" website loaded into
a de facto disk-bound database. the only difference is that you chose to stupidify the index, which is now "exposed" to the user as
a band-aid measure over the fact that you failed to do anything with it.
mircea_popescu: anyway, re static : in context "static" denotes "how much comes from the disk as opposed as through cpuization", there's no other measure.
a page stored as files with the extension .html is ~slightly~ more static than
a page which is stored as files with the extension .txt in
a directory structure that is their de-facto index and are then mixed together into
a thing whenever
a page is called.
mircea_popescu: php is
a hypertext preprocessor. that's what it does, websites. just like the rubber dome in your bathroom unclogs the toilet. does it disgust you ? it's
a tool, you're not expected to keep it on the diner table.
Framedragger: mircea_popescu: i see what you mean, but you can't really call it 'static' by any metric. in point of fact i'm surprised you're not grossed out over the fact that the whole thing is
a large stinking pile of dynamic php. i guess the counterargument is that it *gets the job done*, very well, over many years. :) so there's that. but i'd like to ditch the 'wp' from 'mp-wp' one day. but maybe baby steps.
mircea_popescu: the calls are isolated, wouldn't be the end of the world to replace with
a filesystem equivalent.
mircea_popescu: Framedragger thinking about it, the ~only correct solution is for the mp-wp maintainer to remove mysql in favour of
a flatfile "db" system. then it will be properly static, or as close as its job allows.
shinohai shudders at the thought of
a cucumber strapon
shinohai: I had
a no-shit "Vegan Dominatrix" follow me the other day. Whole new subculture I never heard about.
BingoBoingo: shinohai: Have you considered starting
a something to get some editorial experience? Perhaps you can be the publisher of "The Most Serene Republic's Journal Of Gardening And Whoreticulture"?
☟︎ shinohai: Not yet .... I stood up
a copy on lan and played with it some but you know me and blogging.
shinohai: I still have
a copy in archives, but haven't tinkered with it much. jhvh1 and trb keep me pretty busy.
a111: Logged on 2017-03-05 04:04 lobbes: I cannot think of any other way either without even
a tiny bit of JS
mircea_popescu: lobbes not
a terrible idea, only problem is it cuts to irc line. some comments are long. (otherwise i'd have moved myself)
Framedragger: what i _would_ like is to be able to have these kinds of comments in an otherwise static site (the comment box would be the dynamic component, so to speak - an autonomous backend module/script/whatever). not
a part of
a large ugly php blob.
ben_vulpes: anyways, doing it right is
a small shitton of work, very nearly all of which and more is wrapped up in oldish wordpress.
ben_vulpes: my trinque-simulator sez "wtf with this sqlite; have
a process listening for changes to the comments table and re-rendering the comments page upon submission"
Framedragger: it sure would be nice to just be able to post simple comments on
a blogpage, tho.
Framedragger: sure, but in that case one may as well just implement
a gpggram-to-blog-comments interface (not that it's
a wholly bad idea or anything)
Framedragger: ben_vulpes: yes, but it requires
a dynamic component on the backend, right?
Framedragger: my maybe-convoluted personal plan was to have
a static site generator but to have the comment box be rendered by
a dynamic component (hence loaded separately upon user clicking to comment, or sth.) that component does the 'fraud prevention without JS' magic (like with trilema's comments - IP address is sent to html form to be returned as hidden value / whatnot). when comment is submitted, it gets added to some queue
lobbes: I cannot think of any other way either without even
a tiny bit of JS
☟︎ Framedragger: i guess they could include blog post number at least, but then not full proper quotation as you say. arbitrary selection within
a DOM element only possible with some JS (trilema and archive.is at least have that JS piece tucked nicely in one place, not
a total horror)
lobbes: yeah, seems like it'd be
a pain for the commenter to have to manually input that info to the bot
Framedragger: (i'd like
a static site + comments-without-captcha-or-JS setup, too, yeah)
Framedragger:
http://btcbase.org/log/2017-03-05#1622326 << just checked and realised that your trilema comments don't seem to have any JS, so it seems like i was wrong. (i now realise i had
a (rather arbitrary) additional constraint with the original comment long ago, "make it work with
a static site", but that's another matter/project altogether.)
☝︎ Framedragger: ah, that's one way to do it, via
a saner interface with much less cruft...
lobbes: I almost want to try something like
a !Qcomment command via lobbesbot that'd store comment in
a sqlite db. I'm thinking I may be able to 'default deny' input that way, somehow.
Reuel: hmm, there was something on the radio
a few days ago about the Dutch central bank running blockchain tests
Reuel: like I said, I dont like to be
a net taker but I don't have much time atm