nothing  Stop fucking whining then, eh? |
|
|
|
Quote from: McHammer on Today at 10:07:16 AM
yea... last crash was 100% bot initiated
price gets 99,5% determined by them
rly nice ...
you can only pray whales wanna pump
mb they dump tomorrow -70%
is that a "free market"?
then the silver market is not rigged too
rofl If Bots are so bad for the market why are they allowed? Huh The exchanges and their buddies big money botting. It IS a free market, they're just better equipped to manipulate and therefore profit from it. + if this is no manipulated market there are no manipulated makets lets pray to the whale "pump" if i had a exchange i would not ban them too mass volume ... fees. mnom mnom, who cares about the burned trader Of course, it's absolutely a manipulated market, Cryptsy, Mintpal, all of them are as bent as it gets, but it's as free as anything else - the biggest cats eat first and the rest of us get the scraps. What are you going to do about it?  |
|
|
|
This is an entrenched dynamic - wishful thinking isn't going to change it.
I've got some wishful thinking for you:  Yep, that's well and truly and beautifully distracting...  |
|
|
|
yea... last crash was 100% bot initiated
price gets 99,5% determined by them
rly nice ...
you can only pray whales wanna pump
mb they dump tomorrow -70%
is that a "free market"?
then the silver market is not rigged too
rofl
If Bots are so bad for the market why are they allowed?  The exchanges and their buddies make big money botting. It IS a free market, they're just better equipped to manipulate and therefore profit from it. |
|
|
|
Monday.
I kinda doubt it. DRK is over the shitcoiners' heads. No matter what happens with the development, they just have that mouth-open blank stare... Yeah, open source isn't going to change the price much by itself, nor are we going to see a new rash of clones, because you can't clone a thousand VPS's. My post about forgetting shitty crypto blogs was serious, preaching to anyone inside the crypto scene is an utter waste of effort - we need to get the word out to the spooks, the political dissidents, the junkies, the tax evaders, cheating spouses, etc. People sick of being cheated, violated, and robbed at gunpoint by politicians are not bad people. Did I say that? I'm one of them, but the blunt truth is that the sentient have been out-competed by the clinical sociopaths. We need to develop better predation tactics to survive.Do we? Is the only way to counteract sociopaths to become even more ruthless than them?
Or smarter.  We know how they operate... I think people should just stop being so gullible and finally accept that there are wolves in sheeps clothing among us.
If everybody recognized the wolves there would be no problem.
But that's never going to happen. Wolves like easy prey. Sociopaths like easy prey, they always isolate the sickest, weakest sheep. They hate resistance. The problem lies in all the sheeple who believe that the "charming wolf" (politicians and other cultleaders) is their friend, ... until the end.  This is an entrenched dynamic - wishful thinking isn't going to change it. |
|
|
|
Monday.
I kinda doubt it. DRK is over the shitcoiners' heads. No matter what happens with the development, they just have that mouth-open blank stare... Yeah, open source isn't going to change the price much by itself, nor are we going to see a new rash of clones, because you can't clone a thousand VPS's. My post about forgetting shitty crypto blogs was serious, preaching to anyone inside the crypto scene is an utter waste of effort - we need to get the word out to the spooks, the political dissidents, the junkies, the tax evaders, cheating spouses, etc. People sick of being cheated, violated, and robbed at gunpoint by politicians are not bad people. Did I say that? I'm one of them, but the blunt truth is that the sentient have been out-competed by the clinical sociopaths. We need to develop better predation tactics to survive. |
|
|
|
Monday.
I kinda doubt it. DRK is over the shitcoiners' heads. No matter what happens with the development, they just have that mouth-open blank stare... Yeah, open source isn't going to change the price much by itself, nor are we going to see a new rash of clones, because you can't clone a thousand VPS's. My post about forgetting shitty crypto blogs was serious, preaching to anyone inside the crypto scene is an utter waste of effort - we need to get the word out to the spooks, the political dissidents, the junkies, the tax evaders, cheating spouses, etc. Coins101 is on the right track with gambling sites. edit: lol, this is about the fourth 1st post on page 3183 - mods on a deletion spree again? |
|
|
|
I doubt anyone here is more of a newbie than I am with Arch Linux. I have been playing with it for less than a week. This morning heard about the bash bug, ran the test, and yes I was vulnerable. Hmm... heard how easy Arch is to update so for the first time ran "sudo pacman -Syu"
BOOM--vulnerability gone. Way to go Arch. I'm starting to like this...
I played with Arch, never could get used to it. I'm still do "emerge world -uND" [take a nap]That sure brings back some good memories! Stage 1 FTW! Thanks +1 good to see people still using gentoo. too bad their best times are over. for now I'll stick with arch, too. My whole clusters and clients are all in gentoo  It's really a nightmare. Gentoo taught me a lot. Mostly, that the seconds of my life were too precious to waste watching all that crap scroll by. |
|
|
|
nope, northern cali and I just upgraded my distro, but still no joy. Why always me? ROFLMAO
The 'fix' doesn't work anyway it seems... |
|
|
|
Come on... The same shit again  (Nevertheless, thank you for the update.) What if $SHELL=/bin/ksh (KornShell)? It's not clear reading that link whether it's just the RH fix that's incomplete. edit: nope, 4.3.11(1) is still vulnerable to the examples posted. ubuntu@ip-172-31-23-218:~$ bash --version
GNU bash, version 4.3.11(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
ubuntu@ip-172-31-23-218:~$ env -i X='() { (a)=>\' bash -c 'date'
bash: X: line 1: syntax error near unexpected token `='
bash: X: line 1: `'
bash: error importing function definition for `X'
ubuntu@ip-172-31-23-218:~$ ls -l date
-rw-rw-r-- 1 ubuntu ubuntu 0 Sep 25 22:53 date
edit: now, how do I undo whatever I just did?  |
|
|
|
Yah, I don't know why it won't update. I even changed the sources. The problem is probably on my end.... just gotta keep at it I guess? I've rebooted again, still no joy. version number says 4.2.45(1) crouton, that's all I had to do on my other node. they should be exactly alike, the two nodes.... hummmm Are your instances in Ireland? Those paddy bog trotters may be a bit slow on the updates. |
|
|
|
Heh, not much of an intelligence service if they don't know either of the following: 1) Using Bitcoin is like wearing a G-String and sun-baking on a busy beach (thanks GeorgeM - Memory Burn) 2) Secret agents prefer the Dark We should be sending press releases to Langley, MOSSAD, GCHQ etc. - sod useless crypotoblogs. |
|
|
|
No, that's wrong. Finally check: env x='() { :;}; echo vulnerable' bash -c "echo this is a test" It should return bash: warning: x: ignoring function definition attempt if everything is okay. Bourne parser is fucked up, for how long?! 20 years?! nope, it's not echoing, LOL $ env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
vulnerable
this is a test All I did on my Amazon MN's was run 'sudo apt-get install bash' - came back with 4.3.11 and passed the echo test. |
|
|
|
mv / /dev/null
When the BOFH has finally had enough of this sorry world, he will hurl himself into the meatgrinder just so. |
|
|
|
Bash* at major risk. Bitcoin indirectly through someone exploiting bash. I read that the other day on slashdot - pretty scary actually just how prone to exploits even relatively simple low(ish) level software is. Add five (or fifteen) more layers of crap to get a GUI, do more complex stuff, talk to the world etc. and the whole system is a timebomb. And that's OSS. Proprietary crap is is pure Russian Roulette. I dreamed last night about a mechanical Darkcoin wallet. Made by Benelli, or maybe Glock. Alas, I'm no Babbage to invent such a thing. |
|
|
|
Do you really think paypal accepting bitcoin / darkcoin will be good for the price of the coins.
I don't think so because all conis received by paypal will be converted to fiat directly.
I haven't seen the details of paypal's charging structure for BTC use, but if it's cheaper than regular paypal, the demand I believe will outstrip the dumping and a price rise will ensue. Perhaps the bigger eventual benefit though is in raised public awareness - paypal are playing with fire here, a lot of people hate them but aren't aware of any alternative - that's about to change, and again, IMO this will push BTC price up through increased demand. |
|
|
|
What I did was to check for an existing .conf file, and if it didn't exist, or if it threw an error anyway as it didn't include an rpc user/pwd, run the daemon, take the suggested name/pwd and... stick it in the .conf file, because you're going to need it next time you start the daemon before you can do anything.  That's actually a great idea. The frontend could create the conf file, and save whatever you want in it. We could make the conf file editable from within the frontend itself. Save the conf file, stop the daemon, restart the daemon, all without the need to restart the frontend itself. Adding additional Nodes (addnode, as if darkcoin needs those with this fantastic masternode network) would be easy as never before. Definitely stick a start/stop daemon button in there somewhere, you can always remove it for production and hardcode the startup and shutdown behaviour, I have /path/to/datadir and /path/to/daemon entry boxes too among other things, for testing having the control within the tool is very handy. At one point I had my app call darkcoind help and then automatically create and place buttons for every call that help listed, but I couldn't find a way of arranging 43 buttons or whatever within a sensibly sized window that didn't look hideous... maybe I'll go with a dropdown menu next time... |
|
|
|
A question, how many dummy masternodes are active on the TESTNET on average and at the moment?
How can I find out?
Are only enough of them online when we are making RC bug hunting, or do people generally keep a few of them testnet masternodes active?
or is it possible to run masternode and testnet masternode side by side on the same server?
Just put testnet=1 in your conf or commandline call and run masternode count / masternode list. There are usually some up even between active testing phases. It's not too hard to run main and test net MN's alongside each other as they use different ports (9999 main and 19999 test), you don't need to get creative with IP tables, just use different datadir's (or different users) for each. |
|
|
|
Try it. You're going to be seeing this: Error: To use darkcoind, you must set a rpcpassword in the configuration file:
/home/stu/.darkcoin/darkcoin.conf
It is recommended you use the following random password:
rpcuser=darkcoinrpc
rpcpassword=FgS1HunBZZjp71789svfbkDB56gvzdiuygEq7QxedJgtro6Sw47L
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "DarkCoin Alert" admin@foo.com
Nope , you simply add >E:\darkcoin/darkcoind -rpcuser=darkcoinrpc -rpcpassword=FgS1HunBZZjp71789svfbkDB56gvzdiuygEq7QxedJgtro6Sw47L -testnet=1 Any conf file in the blockchain folder must not exist, or else the daemon will still go looking for it after it starts. (and possibly override your parameters? I am not sure, have not tested this case, I keep no conf file) As I said, you can completely ommit the conf file IF you have direct shell access possibility to the daemon. (which is key) I just tested it again, and it works.  You have to understand, this command is not written somewhere... it's a shell command call that the frontend.exe is making on the fly, it does not need a textfile somewhere, hence no need for a conf file. You can do that, but you'll need to generate a unique pwd for each user - otherwise you'll have a bunch of users with the same rpc credentials which is probably not a great idea. What I did was to check for an existing .conf file, and if it didn't exist, or if it threw an error anyway as it didn't include an rpc user/pwd, run the daemon, take the suggested name/pwd and... stick it in the .conf file, because you're going to need it next time you start the daemon before you can do anything. |
|
|
|
Not at all. I am not talking about RPC calls that need a specific port to be open or something.
I am talking about direct commandline communication between Frontend and darkcoind.
Frontend.exe and darkcoind.exe would best be in the same folder.
It's like when you type commandline commands by hand, but now the frontend.exe makes this for you (with the darkcoind running in the background invisible)
You still need to generate an RPC user/pwd and stick it in the conf file for that to work. At least I had to. It has nothing to do with RPC. It's not remote at all. It's direct communication with the daemon, adding any command and parameters you need to, and reading the return the darkcoind itself gives back. An example: Suppose this is the folder where the darkcoind resides: Now I simply start it by making a Commandcall and the daemon starts. I can even start it with parameters, for example: >E:\darkcoin/darkcoind -datadir=E:\blockchains/drk/ this tells the darkcoind where to look for the blockchain and wallet.dat. WITHOUT the need for any conf file telling it to do that. Everything you put in a conf file can also be added as a parameter when you start the darkcoin daemon. A conf file is not needed if you work like that. So... after the darkcoind is ready, I can make calls to it, for example getblockcount, and it will return the JSON string. >E:\darkcoin/darkcoind -datadir=E:\blockchains/drk/ getblockcount (not that all previous parameters must be repeated) etc. I can start the darkcoind in testnet mode by making the call like that: >E:\darkcoin/darkcoind -testnet=1 I can combine any parameters: >E:\darkcoin/darkcoind -datadir=E:\blockchains/drk/ -testnet=1 and so forth. By using Adobe Air's native extensions functionality I can use ANY external executables I like and trigger their functions and pass the results/data back to the frontend. This would also work with multiple coins at the same time.  Try it. You're going to be seeing this: Error: To use darkcoind, you must set a rpcpassword in the configuration file:
/home/stu/.darkcoin/darkcoin.conf
It is recommended you use the following random password:
rpcuser=darkcoinrpc
rpcpassword=FgS1HunBZZjp71789svfbkDB56gvzdiuygEq7QxedJgtro6Sw47L
(you do not need to remember this password)
The username and password MUST NOT be the same.
If the file does not exist, create it with owner-readable-only file permissions.
It is also recommended to set alertnotify so you are notified of problems;
for example: alertnotify=echo %s | mail -s "DarkCoin Alert" admin@foo.com
|
|
|
|
|
Show Posts
