log☇︎
440700+ entries in 0.267s
ascii_field: but already said this.
ascii_field: i'm not really happy with the removal of the rpc password generator
punkman: why no title assbot
ascii_field: then again, i wouldn't put it past some chinese grad student to throw it in somewhere
ascii_field: funkenstein_: mno. it's accurate enough for 3d shooter, that's more or less it
funkenstein_: thestringpuller, wow that is awesome. do people use this in grav. or e&m simulations?
ascii_field: appears to be fully explained in the lined article.
thestringpuller: tell me about this magic i've found
assbot: Why did victims in Islamic State beheading videos look so calm? They didn’t know it was real. - The Washington Post ... ( http://bit.ly/1I0dtRl )
ascii_field: https://www.washingtonpost.com/blogs/worldviews/wp/2015/03/11/why-did-victims-in-islamic-state-beheading-videos-look-so-calm-they-didnt-know-it-was-real << usg's canned response to ^
assbot: Staged ISIS Beheading Video Hacked from McCain Staffer | Veterans Today ... ( http://bit.ly/1Hul4lp )
ascii_field: (they don't appear to believe in pgp, so i cannot say if authentic)
thestringpuller: you talking about the real bitcoin? or bitcoind?
gernika: sorry, not qntra node, bitcoind node referenced in qntra article. canonical bitcoind node is a better term?
ascii_field: , the sausage is just the start of it—that's ground up and made into meatballs, meatloaf, and a million other products.'
ascii_field: 'The site’s support documentation explains how it works: “First you write a normal original article. Then you make two rewrites of it. All three articles (PDF) must have the same number of paragraphs and each paragraph of each article must have about the same meaning.” This is because the end product is cut up, chopped, and changed to create even more alternative stories. In the content-producing machine
gernika: Maybe the qntra node is running short of connections?
assbot: True confessions: I wrote for an Internet content mill | Ars Technica ... ( http://bit.ly/1I0c6lC )
mod6: 365261 = 909.83kB - 693 txs
mod6: 365260 = 249.83kB - 467 txs
mod6: 365259 = 908.97k - 1090 tx's
danielpbarron: on a pogo the answer is a few minutes
mod6: would be inetersting/nice to see the ms time on how long it takes to process blocks {365`251, 365`252}; blocks > 900kb
danielpbarron: don't think so, or at least I did nothing to correct anything
ascii_field: danielpbarron: was this a clock problem ?
ascii_field: https://www.os3.nl/_media/2013-2014/courses/ccf/chromecast-cedric-peter.pdf << re: the device spoken of yesterday. discusses fw reflashing
ascii_field: and that's the default nick
ascii_field: trinque: folks who click the link on phuctor www get a webportal into freenode
ascii_field: trinque: that's proper
trinque: anyone else noticed the from* pattern of nicks?
ascii_field: (why not write to google? they censor first, ask questions later)
ascii_field: nor google, which appears to be the proximate cause of his sorrows
ascii_field: none of which the fool wrote to, presumably
fluffypony: it's not like this is a revenge porn site and we're laughing at the diminutive size of his member
ascii_field: aha. not even in schmuckistan where i live, can you win this.
fluffypony: I do find the righteous indignation humorous
ascii_field: nor that this fella's mother gave him this name (again, which name?)
ascii_field: trinque: we haven't even any reason to believe that mr x owns the private key to this pubkey (which? also no idea)
trinque: they ought to have a test for this in early childhood
fluffypony: although you do remind me of this: https://www.reddit.com/r/legaladvice/comments/3cd6oj/im_in_highschool_and_money_was_stolen_from_my/
fromphuctor: nah, ill take your compan's info
ascii_field: fluffypony: nah he wants to give mp his money
fluffypony: so you can hear the same thing again?
ascii_field: fromphuctor: the answer is no. any other questions ?
jurov: name and email (optionally even photo!) are part of public key and thus public.
fromphuctor: im not asking for sympathy, Im asking you to remove my name and information from your website
ascii_field: you are welcome to wait until mircea_popescu logs on, and ask him for a contact address where to file a frivolous lawsuit. he loves winning those.
fromphuctor: I'm pretty sure I uploaded it to sks years ago
ascii_field: fromphuctor: did you upload your key to sks? or did it live under your pillow, and you are telling us that someone stole it and uploaded it ?
fromphuctor: right, and I want that removed
ascii_field: fromphuctor: what other information? the only things visible are what is in your key - the name and email addr entered when it was generated.
ascii_field: fromphuctor: we even have a list of folks for whom some hooligan submitted entirely fraudulent (as far as we can tell) keys. nothing can be done about this.
fromphuctor: im not concerned about the key floating around, just the other information listed on nosuchlabs
funkenstein_: maybe one day we will learn to use namecoin
fluffypony: also known as the "sorry for you" problem
fluffypony: public keys that never go away, a form of "keyserver plaque".'
fluffypony: 'Once a public key has been uploaded, it is difficult to remove. Some users stop using their public keys for various reasons, such as when they forget their pass phrase, or if their private key is compromised or lost. In those cases, it was hard to delete a public key from the server, and even if it were deleted, someone else can upload a fresh copy of the same public key to the server. This leads to an accumulation of old fossil
ascii_field: i am under no obligation to modify my code to make 'mr x' (whose name we do not yet know, nor have any proof that 'his' key is his) disappear every time someone submits him.
assbot: Key server (cryptographic) - Wikipedia, the free encyclopedia ... ( http://bit.ly/1I0QyDm )
ascii_field: i.e. your enemy can submit the key again
fluffypony: SKS doesn't mandate that you remove data to keep in sync
ascii_field: fromphuctor: realize that anyone can submit anything to sks
fromphuctor: do you maintain the database for nosuchlabs
fluffypony: hosted by the Glorious Defenders of Privacy at MIT
ascii_field: which is mirrored 1,001 times worldwide.
trinque: but it's really important that *this* one be taken down
ascii_field: aha, virtually all of the pubkeys in phuctor come from sks.
trinque: I'm still perplexed by the idea that someone would be bothered by what is a highly beneficial *free* service annotating entirely *public* data
fromphuctor: which country is that
fromphuctor: im pretty sure there's laws in place that give me the right to have that info removed ☟︎
mod6: yeah, iirc keys will not be removed from the phuctor pool.
trinque: what is this, the right to be forgotten?
fromphuctor: I'm aware of that
trinque: fromphuctor: a public key is called public because it is safe to distribute
fromphuctor: I dont want the other associated info on the net
nubbins`: means nobody else's key is suspiciously similar to yours :D
trinque: fromphuctor: then why would you want that info taken off the internet?
fromphuctor: not sure what that means but it's green
trinque: fromphuctor: sks is the system which distributes public keys
nubbins`: trying to find clues as to broken implementations, flaws in rsa, etc
mod6: its purpose is to factor keys with GCD
nubbins`: phuctor is smashing numbers together, right now, churning through huge data sets of pgp keys
danielpbarron: fromphuctor, was the text all a happy green or a mean red?
nubbins`: it's to find keys that were generated insecurely
fromphuctor: sure it's to store my public gpg key
trinque: fromphuctor: maybe you don't understand the purpose of phuctor?
mod6: hmm, that error comes from one place: http://btc.yt/lxr/satoshi/source/src/main.cpp#0442 << perhaps thats when all of those tiny tx's started filling up the block space?
danielpbarron: fromphuctor, but is the key cracked? I'm sure a bunch of people would like to know how you created it if it was.
fromphuctor: I no longer use the key and I just dont want my info being indexed by google
nubbins`: curious minds wish to know
jurov: fromphuctor: did you remove the info from SKS keyserver, too?
fromphuctor: so should I private message them or wait here?
assbot: Logged on 14-07-2015 08:20:36; mircea_popescu: "in front of a four year old" wtf is the snotty shit, a judge now ?
danielpbarron: http://log.bitcoin-assets.com/?date=14-07-2015#1200705 << a guy threatened to punch me in the face for offering him some cannabis infront of his 4ish year old the other day ☝︎
danielpbarron: i don't think you can, but asciilifeform and mircea_popescu are the ones that could do it if it can be done
danielpbarron: ERROR: AcceptToMemoryPool() : not enough fees << lots of this in my debug.log
mod6: (gentoo) turned mine on to try. node must be down or something.
mod6: ok, yeah, im getting the same thing.
gernika: My OpenBSD bitcoind has stopped syncing: trying connection x.x.x.x:8333 lastseen=-371358.4hrs lasttry=-399136.2hrs | it had been syncing from the address in the qntra post.
mats: dun think so