|
Well we could make them fill out a captcha first in order to learn the fact that they cannot sign up. Why give them that information "for free" up front? :evilgrin:
Basically if they are seemingly human, then tell them what it is that they do have to do in order to get someone to create an account for them.
Maybe bearing in mind we know they are willing to deploy captcha-solvers to do it, so whatever it is should bear that in mind. Which might be why we want a sample article or whatever. (Though I guess bots could have libraries of those too.)
-MarkM-
|
|
|
|
Try opentxs showmarkets --server wmY1B8o94PFENzqPVK6wLOLvkog9TvA3GDxZuAMGCpW
(I just tried that, it works for me.) Things like that. opentxs, the subcommand within it you want, and the switches/args. Just don't even bother staying inside opentx or ot "shell mode", FT isn't even trying to make them work anymore I think, like they are deprecated modes or something. So just do oneliners that tell opentxs one command you want it to run for you, with whatever args that subcommand needs. -MarkM- |
|
|
|
I am pretty sure you have to know who owns your stocks, and that they are not "bearer instruments" thus people passing them around changes nothing, in essence the certificate they are passing around either says on it that it certifies that some specific person owns so many shares of whatever stock or it implicitly "says" that due to some kind of serial number or stock number specifying which share it is so the company or their share-tracking agent can look up who it is exactly that specific instance of the stock belongs to. That is part of why it can take three days or so to "clear", the shares being exchanged have to be looked up to check who they belong to, then updated to reflect who they belong to now, and maybe the company the shares are shares of might even have to be notified, though maybe they might not need to know every minute, maybe they just have to submit at year-end or something an up to date list of who their shareholders are and how many shares each holds. It does not seem likely that a company is going to be able to claim like "oh we are innocent, we trusted money-and-stock laundry unicorporated, a p2p network, to do all that legal paperwork for us, if its not done right you should go see them about it... See for example http://www.quatloos.com/bearer_shares.htm-MarkM- |
|
|
|
WARNING: When registering for their website, your password gets emailed to you. A big security no-no. Nothing like feeling safe handing over a couple grand. I think I'll cancel my order.
You don't immediately change your password when that happens? Seems a lot of old code does that kind of silliness, not sure what merchant site package one would have to pick to get around it? -MarkM- |
|
|
|
|
An estimate of how much money needs to be thrown at it to get it ready for them to use would probably be useful...
People have been throwing $300,000 a shot at stuff lately it seems, would this be cheaper than that to deploy, do you think?
-MarkM-
|
|
|
|
|
Crapcoins of the day are not "ready for use" either. They are "ready to hand over your loot to anyone with more hashing power", which is NOT the use you hopefully want?
It'd be a massive amount more work to and sheer hardware and electricity cost to secure even just one blockchain let alone one per IPO, compared to just throwing money at programmers to get coloured coins finished off.
Do you want a pretend toy crappy little mickey-mouse pretend thing or some serious financial application software?
Also, what is the big deal about p2p / distributed? You have to trust the issuer regardless, else the crap is worthless. So might as well trust them to keep their server online, whether on Tor or whatever, and transact directly with them. (e.g. using Open Transactions, or Cyclos, or whatever the heck. Open Transactions has markets, altcoins, off the rack, don't and nor does Cyclos really, just for sale / want to buy ads type of thing.)
-MarkM-
|
|
|
|
Only a patent lawyer or patent clerk would think doing business using money is in any way a new idea.  They are insane nutbars. For example the computing field spend umpteen years working on hypertext and ultimately hypergraphics even, specifically so that you could click on a pixel or pixels to trigger a program or subroutine, then some idiot in the patents system thinks clicking on a pixel to trigger a "sell something to the guy who clicked" routine is a unique new totally non-obvious idea! Like duh, clicking to trigger a procedure / process is not new, idiots! Its darn near the main objective of the entire GUI/web platform fergoshsakes. Who hadn't already thought of it and even used it since years before it was patented? -MarkM- |
|
|
|
|
The commandline "shell" mode doesn't work I think. Do individual commands from the unix shell, like
opentxs status
or whatever instead of invoking opentx or ot and doing commands from its own prompt.
In ~/.ot is a commandline mode defaults file where you can set your default server and nym, and other things that you probably don't want to default.
Otherwise you need --server and --mynym and so on on the commandline.
-MarkM-
|
|
|
|
|
Also no word on when the chips arrived, that Yifu supposedly claimed to have shipped last monday.
Hopefully they arrived, were put on boards 24/7 all weekend, and he has been busy boxing and shipping them all day...
Unless he or Yifu lied? Or customs intervened "again"? Or something?
-MarkM-
|
|
|
|
My two bitfury cards pull ~ 46 watts at 66 Gh/s
Wow that is nice and low, I had tended to imagine figures like that were not at the wall but more like just the chip itself without the support stuff / board and wallwart or ATX etc. -MarkM- |
|
|
|
Dude, your question shows exactly how far back you read... The whole reason this shit about bitfury cropped up is because people were claiming ridiculous numbers on the efficiency of a 65nm chip which for all intensive purposes should not have been possible and then transformed into an argument over whether or not the BF chip was more efficient than KNC's. That was the point he was getting at I believe, people where claiming some crazy shit, with out any proof to back it up...
...
The KNCminer specs from there own data is Energy consumption: 1.6 W/Gh/s. the Bitfury is 1.0W/GH/s what's so hard about that to understand? The Bitfury is more energy efficient, though they both are pretty good. The KnC 1.6 is at the wall though, right? What is bitfury's at the wall? -MarkM- |
|
|
|
|
The problem of how to secure a block chain is why coloured coins are so suitable for this kind of application. The whole blockchain thing is already taken care of for them.
-MarkM-
|
|
|
|
|
Yeah but then you will have imported gosh knows how many dead accounts/coins.
Might be better to only have a fixed window of time in which to claim your ripples, after which we will know for sure exactly how many ripples were put into circulation, the rest can just stay dead in the original address from which the distribution was done.
-MarkM-
|
|
|
|
|
There are too many possibilities.
Many many years ago HP put out a calculator, the HP-25, which was programmable, but had no card-reader type of thing for recording "programs", which were basically up to 25 stored keystrokes.
They had an example pseudorandom number generator that I typed in so many times for playing tabletop roleplaying games that to this day I still remember it: start with a random number less than one (zero point a bunch of digits), add it to pi, raise it to the fifth power, and take the fractional part.
You could probably do that with some chosen number of digits of accuracy yourself with any of a number of arbitrary accuracy calculators such as 'bc'.
But why do exactly that? Why not use root two instead of pi? Or the golden ratio? Or any other famous number easy to look up on the internet? Why the fifth power? Wouldn't the seventh, or thirteenth, or whatever number you would find easy to remember, work just as well?
This does not even use any of the steps involved in the original post so merely bruteforcing using the original post's repertoire of steps ought not stumble upon it...
Plus what number less than one did you even start with? The genesis block hash with a decimal point in front of it? The date in the headline in the genesis block, expressed in seconds since the purported birthtime of some prophet (with a decimal point in front of it) or what? Etc.
And how many digits accuracy, exactly, did you tell your arbitrary accuracy calculator to use? How does that version of it on that architecture "round" or "truncate" extra digits? Etc.
-MarkM-
|
|
|
|
|
We could pick a block number at which to archive a copy of the bitcoin blockchain, then decide how many opensource ripples there are going to be and compare that to the number of bitcoins on the archived blockchain. Then anyone who wants some RIpples produces a request signed by a bitcoin address that had bitcoins at the time the blockchain was archived and receives that many ripples and that address is ticked off as having received its allotment of ripples.
That way we can distribute the ripples and not even actually know whether in fact they will all end up redeemed/distributed, since we do not know how many of the bitcoins in the archived blockchain still have somewhere someone or something that knows or remembers (records) the private key that would be needed to actually redeem those ripples.
To avoid a central authority we could do a whole distributed system for ticking off which addresses have been redeemed (and to what ripple address the corresponding ripples were sent. If we even care, or need to know, to what ripple address they went).
A problem with trying to 51% an existing ripple network is the incumbents do not have to listen to anyone they don't want to. They list only the servers they want to as ones to care about when making a consensus. So they can open source the code but just not bother telling any of the existing servers to pay any attention to any new nodes other than ones they hand pick based on the new node having paid them off, having know your customer rules, having anti money laundering procedures in place, being owned by a direct descendant of Bill Gates or Jed or Obama or whatever criteria they choose to use to decide which nodes their node will give any weight to in the "consensus" process.
-MarkM-
|
|
|
|
Well lets get really specific: we'll assume you are using "tinyfugue" MUD client so your scripts will be tinyfugue (tf) scripts; and we'll assume you went with the race known as Duergar and the profession known as artisan, because seeing in the dark lets you not have to do all the worrying about torches or lamp-oil that races without darkvision have to deal with if they want to work in caves or outdoors-at-night: ~/tf/aduergar: ################################ Aduergar ##########################################
/addworld -Ttelnet aduergar Aduergar MyAccountPassword mudgaard.knotwork.com 5555
/def ln = look north
/def le = look east
/def ls = look south
/def lw = look west
/def lu = look up
/def ld = look down
/def lne = look northeast
/def lse = look southeast
/def lsw = look southwest
/def lnw = look northwest
/def lc = look body
/def lac = look all.body
/def gcc = get coins all.body
/def gac = get all all.body
/set food mushroom
/set healingberry berries
/set weapon shiny newbie dagger
/set wandertask 0
/set berrytopackage berries
/def -waduergar -mglob -t"You package up 50 *erries." aduergar_packaged_berries = \
get all package %; n %; w %; w %; s %;\
s %; s %; s %; s %; s %; s %; s %; s %; s %; w %;\
drop all package %; e %; n %; n %; n %; n %; n %; n %; n %; n %; n %;\
n %; e %; e %; s %; say Berries packaged.
/def -waduergar -msimple -t"You say 'Berries packaged.'" berries_packaged = /nextaction
/def -waduergar packageberries = stand %; package 50 some %{berrytopackage}
/def -waduergar -msimple -t"All items in a package must be absolutely identical. Some here are not." \
aduergar_rotate_berries = get 50 some %{berrytopackage} %; drop all some %{berrytopackage} %; /packageberries
/def -waduergar crafttask = rest
/def -waduergar nextaction = mine
/def -waduergar butcher = /def -waduergar nextaction = butcher body %; butcher body
/def -waduergar cg = cast grow %{*}
/def -waduergar chop = /def -waduergar nextaction = chop %; chop
/def -waduergar ci = cast invisibility
/def -waduergar don = cast "clan donate" %{*}
/def -waduergar ehb = eat %{healingberry}
/def -waduergar fbf = get all "buffalo water skin" from bag %;\
fill buffalo water skin.1 fountain %;\
fill buffalo water skin.2 fountain %;\
fill buffalo water skin.3 fountain %;\
fill buffalo water skin.4 fountain %;\
fill buffalo water skin.5 fountain %;\
fill buffalo water skin.6 fountain %;\
fill buffalo water skin.7 fountain %;\
fill buffalo water skin.8 fountain %;\
fill buffalo water skin.9 fountain %;\
fill buffalo water skin.10 fountain %;\
fill buffalo water skin.11 fountain %;\
fill buffalo water skin.12 fountain
/def -waduergar fbw = get all "buffalo water skin" from bag %;\
fill "buffalo water skin.1" %;\
fill "buffalo water skin.2" %;\
fill "buffalo water skin.3" %;\
fill "buffalo water skin.4" %;\
fill "buffalo water skin.5" %;\
fill "buffalo water skin.6" %;\
fill "buffalo water skin.7" %;\
fill "buffalo water skin.8" %;\
fill "buffalo water skin.9" %;\
fill "buffalo water skin.10" %;\
fill "buffalo water skin.11" %;\
fill "buffalo water skin.12"
/def -waduergar forage = /def -waduergar nextaction = forage %; forage
/def -waduergar freshlantern = /stand %; hold lantern %; fill lantern oil
/def -waduergar gdig = /def -waduergar nextaction = gdig %; gdig
/def -waduergar hl = hold lantern
/def -waduergar makeberrypreserves = /stand %; /def -waduergar nextaction = /makeberrypreserves %;\
/def -waduergar -n1 -msimple -t"You are done making berry preserves." aduergar_berry_preserves_done = \
get all pot %%; put all burnt trash %%; e %%; e %%; open sw %%; sw %%; drop all preserves %%;\
ne %%; w %%; w %%; /nextaction %;\
get 15 berries %; put all berries pot %; foodprep pot
/def -waduergar makebloodwine = /stand %; /def -waduergar nextaction = /makebloodwine %;\
e %; e %; fill pitcher fountain %; w %; w %; get blood %; put blood pitcher %;\
get grapes %; put grapes pitcher %;\
/def -waduergar -n1 -msimple -t"You are done distilling blood wine." aduergar_wine_done = \
e %%; e %%; get all pitcher %%; put all wine tub %%; w %%; w %%; /nextaction %;\
distill pitcher
/def -waduergar maketorches = /stand %; /def -waduergar nextaction = /maketorches %;\
/def -waduergar -n1 -msimple -t"You are done carving a torch." aduergar_torch_done = /nextaction %;\
carve torch %; score
/def -waduergar mine = /def -waduergar nextaction = mine %; mine
/def -waduergar pol = remove lantern %; put out lantern %; fill lantern oil
/def -waduergar r = recall
/def -waduergar react_to_disarmed = get %{weapon} %; wield %{weapon}
/def -waduergar really_tired = rest%; sleep %; /repeat -0:5:0 1 /wakenrest %; /crafttask
/def -waduergar stand = wake %; stand
/def -waduergar wakenrest = wake %; rest
/def -waduergar -msimple -t"A buffalo water skin is empty." buffalo_water_skin_empty = \
put "buffalo water skin" in bag
/def -waduergar -msimple -t"A hooded brass lantern flickers and burns out." aduergar_hb_lantern_out = /freshlantern
#/def -waduergar -msimple -t"A roaring campfire is no longer burning." aduergar_campfire_faded = light fire
/def -waduergar -msimple -t"A torch flickers and burns out." aduergar_torch_out = hold torch
/def -waduergar -msimple -t"A waterskin is empty." water_skin_empty = \
put waterskin in bag
/def -waduergar -msimple -t"An oil flask is empty." oil_flask_empty = \
put oil flask in bag %; fill lantern oil
/def -waduergar -mglob -t"* disarms you!" aduergar_opponent_disarmed_me = /react_to_disarmed
/def -waduergar -msimple -t"Not while you are sleeping." aduergar_not_while_sleeping = wake
/def -waduergar -msimple -t"You are hungry." am_hungry = wake %; eat %{food}
/def -waduergar -msimple -t"You are sleeping!" aduergar_are_sleeping = wake
/def -waduergar -msimple -t"Huh?" aduergar_huh = /mine
/def -waduergar -msimple -t"You are thirsty." am_thirsty = wake %; drink water
/def -waduergar -mglob -t"You are done chopping*" aduergar_chopping_done = /nextaction
/def -waduergar -mglob -t"You are done digging out *" aduergar_digging_done = /nextaction
/def -waduergar -mglob -t"You are done foraging*" aduergar_foraging_done = /nextaction
/def -waduergar -mglob -t"You are done mining*" aduergar_mining_done = /nextaction
/def -waduergar -mglob -t"You are done skinning and butchering *" aduergar_butchering_done = /nextaction
/def -waduergar -msimple -t"You are now listed as AFK." react_to_afk = /crafttask
/def -waduergar -mglob -t"You continue digging out * completed). " aduergar_continue_gdig = smile
#/def -waduergar -msimple -t"You don't think this is a good place to forage." aduergar_not_good_forage = \
# /set nextaction butcher body %; butcher body
/def -waduergar -msimple -t"You don't think this is a good place to mine." aduergar_not_good_mine = /gdig
/def -waduergar -msimple -t"You can't seem to find anything worth digging up here." aduergar_cant_find_dig = /forage
/def -waduergar -msimple -t"You can't seem to find anything worth foraging around here." aduergar_cant_find_forage = /mine
/def -waduergar -msimple -t"You can't seem to find any game around here." aduergar_cant_find_game = /mine
/def -waduergar -msimple -t"You can't seem to find anything worth mining here." aduergar_cant_find_mine = /gdig
/def -waduergar -msimple -t"You don't have enough movement to do that. You are too tired." aduergar_no_mp = sleep
/def -waduergar -msimple -t"You need to stand up!" aduergar_need_to_stand = /stand
/def -waduergar -msimple -t"You stop yawning." aduergar_stopped_yawning = /wakenrest
/def -waduergar kill_opponent = /stand%; kill %{*}
/def -waduergar opponent_died = rest
/def -waduergar conditionals = \
/if /test %{wandertask} %;\
/then /def -waduergar -mregexp \
-t"You might try to the ([^ ]*)\.$$" aduergar_might_try_direction = say %%P1 %%; %%P1 %%; /nextaction %;\
/else \
/undef aduergar_might_try_direction %;\
/endif
/conditionals
################################ END OF Aduergar ###################################
~/tf/auto/aduergar: /load tf/aduergar
/def -waduergar nextmission = /gomining
/def -waduergar crafttask = wake %; score %; /nextaction
/def -waduergar -msimple -n1 -h"PROMPT Account name: " aduergar_account_prompt = Aduergar
/def -waduergar -msimple -n1 -h"PROMPT Command or Name (?): " aduergar_name_prompt = aduergar %; /gohome
#/def -waduergar -msimple -n1 -h"PROMPT Quit -- are you sure (y/N)?" aduergar_quit_sure = yes
/def -waduergar -msimple -n1 -t"(You are asleep)" aduergar_asleep = wake %; look
#/def -waduergar -msimple -n1 -t"West wing room. " aduergar_in_bedroom = /nextmission
/def -waduergar -msimple -t"It's too wet to light a torch here." aduergar_too_wet = /gohome
/def -waduergar -msimple -t"You are famished! Eat something!" aduergar_famished = /gohome
/def -waduergar -msimple -t"You are parched! Drink something!" aduergar_parched = /gohome
/def -waduergar bathe = /bathe1
/def -waduergar bathe1 = /def -waduergar -msimple -n1 -t"You bathe yourself." aduergar_bathed1 = /bathe2 %; bathe
/def -waduergar bathe2 = /def -waduergar -msimple -n1 -t"You bathe yourself." aduergar_bathed2 = /bathe3 %; bathe
/def -waduergar bathe3 = /def -waduergar -msimple -n1 -t"You bathe yourself." aduergar_bathed3 = /bathe4 %; bathe
/def -waduergar bathe4 = /def -waduergar -msimple -n1 -t"You bathe yourself." aduergar_bathed4 = /bathe5 %; bathe
/def -waduergar bathe5 = /def -waduergar -msimple -n1 -t"You bathe yourself." aduergar_bathed5 = /bathe6 %; bathe
/def -waduergar bathe6 = /def -waduergar -msimple -n1 -t"You bathe yourself." aduergar_bathed6 = /bathe7 %; bathe
/def -waduergar bathe7 = /def -waduergar -msimple -n1 -t"You bathe yourself." aduergar_bathed7 = /bathe8 %; bathe
/def -waduergar bathe8 = /def -waduergar -msimple -n1 -t"You bathe yourself." aduergar_bathed8 = /gotobed %; bathe
/def -waduergar chop = /def -waduergar nextaction = get all %%; /don bundle %%; /don bundle %%; /don bundle %%;\
/don pound %%;\ /don pound %%; /don pound %%; /don body %%; /don body %%; chop %%; score %; chop
/def -waduergar farm1 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed1 = /farm2 %;\
get all grapes %; drop grapes %; farm grapes
/def -waduergar farm2 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed2 = /farm3 %;\
w %; get all grapes %; drop grapes %; farm grapes
/def -waduergar farm3 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed3 = /farm4 %;\
w %; get all grapes %; drop grapes %; farm grapes
/def -waduergar farm4 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed4 = /farm5 %;\
w %; get all grapes %; drop grapes %; farm grapes
/def -waduergar farm5 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed5 = /farm6 %;\
w %; get all grapes %; drop grapes %; farm grapes
/def -waduergar farm6 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed6 = /farm7 %;\
w %; get all grapes %; drop grapes %; farm grapes
/def -waduergar farm7 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed7 = /farm8 %;\
w %; get all grapes %; drop grapes %; farm grapes
/def -waduergar farm8 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed8 = /farm9 %;\
w %; get all grapes %; drop grapes %; farm grapes
/def -waduergar farm9 = /def -waduergar -mglob -n1 -t"You are done planting Grapes." aduergar_farmed9 = /farm0 %;\
w %; get all grapes %; drop grapes %; farm grapes
/def -waduergar farm0 = /homefromfarm
#/def -waduergar forage = /def -waduergar nextaction = /don pound %%; /don pound %%; /don pound %%; /don pound %%;\
# /don pound %%; /don pound %%; /don pound %%; /don pound %%; /don pound %%; /don pound %%; /don pound %%;\
# forage %%; score %; forage
/def -waduergar forage = /def -waduergar nextaction = /forage %%; score %; forage %; score
/def -waduergar gdig = /def -waduergar nextaction = gdig %%; score %; gdig %; score
/def -waduergar getberries = e %; e %; u %; e %; e %; e %; e %; e %; e %; d %; s %; d %; get all berries %;\
u %; n %; u %; w %; w %; w %; w %; w %; w %; d %; w %; w %; drop all berries
/def -waduergar getlemons = e %; e %; u %; e %; e %; e %; e %; e %; e %; d %; s %; d %; get all lemons %;\
u %; n %; u %; w %; w %; w %; w %; w %; w %; d %; w %; w %; drop all lemons
/def -waduergar getolives = e %; e %; e %; e %; e %; e %; e %; e %; d %; s %; d %; get all olives %;\
u %; n %; u %; w %; w %; w %; w %; w %; w %; w %; w %; drop all olives
/def -waduergar getoranges = e %; e %; u %; e %; e %; e %; e %; e %; e %; d %; s %; d %; get all oranges %;\
u %; n %; u %; w %; w %; w %; w %; w %; w %; d %; w %; w %; drop all oranges
/def -waduergar go_manual = /def nextmission = /go_manual %; /undef aduergar_fatigued
/def -waduergar gochopping = /def -waduergar -msimple -n1 -t"You are fatigued." aduergar_fatigued = /gohome %;\
/set wandertask 1 %; /conditionals %; /stand %; hold torch %; /gotowoods %; /chop
/def -waduergar gofarming = /def -waduergar -msimple -n1 -t"You are fatigued." aduergar_fatigued = /homefromfarm %;\
/set wandertask 0 %; /conditionals %; /stand %; hold torch %; /gotofarm %; /farm1
/def -waduergar goforaging = /def -waduergar -msimple -n1 -t"You are fatigued." aduergar_fatigued = /gohome %;\
/set wandertask 0 %; /conditionals %; /stand %; /gotoforage %; /forage
/def -waduergar gohome = /def nextaction = rest %; w %; s %; sw %; /fbw %; /bathe
/def -waduergar gomakepreserves = /def -waduergar -msimple -n1 -t"You are fatigued." aduergar_fatigued = \
/def nextaction = /homefrompreserves %;\
s %; e %; n %; n %; n %; w %; w %; w %; d %; w %; w %;\
/getberries %; /getfruit %; /getlemons %; /getoranges %; /preserveberries
/def -waduergar gomining = /def -waduergar -msimple -n1 -t"You are fatigued." aduergar_fatigued = /gohome %;\
/gotomine %; /mine
/def -waduergar gopackaging = /def -waduergar -msimple -n1 -t"You are fatigued." aduergar_fatigued = /gohome %;\
/stand %; hold torch %; /gotoberries %; /packberries
/def -waduergar gopackberries = /def -waduergar nextmission = /gopackblackberries %;\
/set berrytopackage berries %; /gopackaging
/def -waduergar gopackblackberries = /def -waduergar nextmission = /gopackblueberries %;\
/set berrytopackage blackberries %; /gopackaging
/def -waduergar gopackblueberries = /def -waduergar nextmission = /gopackboysenberries %;\
/set berrytopackage blueberries %; /gopackaging
/def -waduergar gopackboysenberries = /def -waduergar nextmission = /gopackcranberries %;\
/set berrytopackage boysenberries %; /gopackaging
/def -waduergar gopackcranberries = /def -waduergar nextmission = /gopackraspberries %;\
/set berrytopackage cranberries %; /gopackaging
/def -waduergar gopackraspberries = /def -waduergar nextmission = /gopacksmurfberries %;\
/set berrytopackage raspberries %; /gopackaging
/def -waduergar gopacksmurfberries = /def -waduergar nextmission = /gopackstrawberries %;\
/set berrytopackage smurfberries %; /gopackaging
/def -waduergar gopackstrawberries = /def -waduergar nextmission = /gopackberries %;\
/set berrytopackage strawberries %; /gopackaging
/def -waduergar gotobed = /def -waduergar -msimple -t"You awake and stand up." aduergar_awakes = /nextmission %;\
stand %; ne %; drop all mushroom %; get 15 mushroom %; e %; sleep
/def gotoberries = s %; e %; n %; n %; n %; n %; n %; n %; n %; n %; e %; e %; s
/def -waduergar gotofarm = s %; e %; n %; n %; n %; e %; e %; e %; d %; s %; d %; get 9 grapes %;\
u %; n %; u %; w %; w %; w %; s %; s %; s %; s %; s %; s %; w %; w %; s %; s %; w %; w %; s %; s %;\
nw %; n %; n %; n
/def -waduergar gotoforage = /stand
/def -waduergar gotomine = /stand
/def -waduergar gotowoods = s %; e %; s %; s %; s %; w %; w %; n %; n %; n %; n
/def -waduergar homefromfarm = /stand %; cast clan home %; cast clan home %; cast clan home %;\
s %; e %; drop all torch %; get 25 torch %; w %; n %;\
n %; n %; n %; n %; e %; e %; e %; d %; s %; d %; drop all grape %; u %; n %; u %; w %; w %; w %;\
n %; n %; n %; n %; nw %; /bathe
/def -waduergar homefrompreserves = /def nextaction = rest %: e %; e %; u %; e %; e %; e %; n %; n %;\
/pol %; /hl %; n %; nw %; /bathe
/def -waduergar mine = /def -waduergar nextaction = mine %%; score %; mine %; score
/def -waduergar packberries = /def nextaction = /packageberries %%; score %; /packageberries %; score
/def -waduergar preserveberries = \
/def -waduergar -n1 -msimple -t"You are done making berry preserves." aduergar_preserve_berries_done = \
get all pot %%; put all burnt trash %%; e %%; e %%; open sw %%; sw %%; drop all preserves %%;\
ne %%; w %%; w %%; score %;\
/getberries %; empty pot %;\ get 15 berries %; put 15 berries pot %; foodprep pot
/def -waduergar preservelemons = \
/def -waduergar -n1 -msimple -t"You are done making lemon preserves." aduergar_preserve_lemons_done = \
get all pot %%; put all burnt trash %%; e %%; e %%; open sw %%; sw %%; drop all preserves %%;\
ne %%; w %%; w %% score %;\
/getlemons %; empty pot %; get 15 lemons %; put 15 lemons pot %; foodprep pot
/def -waduergar preserveoranges = \
/def -waduergar -n1 -msimple -t"You are done making orange preserves." aduergar_preserve_oranges_done = \
get all pot %%; put all burnt trash %%; e %%; e %%; open sw %%; sw %%; drop all preserves %%;\
ne %%; w %%; w %% score %;\
/getoranges %; empty pot %; get 15 oranges %; put 15 oranges pot %; foodprep pot
/def -waduergar sortoilflasks = drop all oil %; s %; get all oil bag %; e %; e %; e %; s %;\
drop all oil %; n %; w %; s %; s %; e %; get oil flask %; w %; n %; n %; w %; w %; n %;\
drop all oil %; get 8 oil
The command to start it up is "tf -ftf/auto/aduergar". If the version of coffeemud being run at the MUD isn't the latest one that broke some stuff by trying to add weird nonstandard ansi codes to support some client that is a real problem-client nowhere near as important as tinyfugue in the coffeemud developer's scheme of things, this automatically logs in and does stuff that earns experience and keeps the character fed and bathed and watered, provided you gave the character at least one "buffalo hide waterskin" up front it can fill at the lake and drink from when thirsty. The fact that the actual auto-logging-in currently is broken is actually in a way a feature not a bug, because an individual can easily just log in when they fire it up, whereas a botnet operator with thousands of zombies trying to do this now has thousands of zombies to log in to manually or has to hack up a patch to apply on each zombie with some kind of workaround for the login. Presumably being careful that it will still work as soon as the coffeemud developer reverts the crazy attempt to accomodate the neverending-source-of-trouble client he didn't really want to support anyway so that tinyfugue will work fine again as normal. This is a really simplistic pair of scripts, for a race and character-class that is so far seemingly the simplest to deal with. Doubtless scripts will get way more sophisticated over time, but this one is simplistic enough people likely wouldn't be too concerned about just giving it away to anyone because doubtless their own customised version would outperform it. Also it actually contains tons of pieces of script that it does not need, as examples, because it was made by being given a script by an elf who had a clanhouse to move around in with ovens and stoves and so on thus could make preserves and fun stuff like that. Those examples will come in handy for some duergar sometime who sculpts a stove, smiths some pots and pans and so on, and finds sources of fruit and so on. It could be stripped down a LOT by chopping out all the stuff the current generation of Duergar at the Duergar starting-spot don't actually use yet. The clanhouse is of a floorplan that one can buy ready-made, so actually if the Duergar manage to rack up enough capital they could in principle order such a clanhouse, or maybe even build one, put the oven etc in the same room of the kitchen area etc, and basically make a lot of those scripts work unaltered in a clanhouse of their own. Most likely a newbie would in effect "get a job", whereby they create a race and profession of character the "employer" wants to "hire", and run scripts provided by the "employer" that include taking stuff to the employer's merchant/shop to sell and maybe even buying food and water there too, so they can focus directly on just their "job". This particular group of Duergar that this individual Duergar is living with though are starting pretty much from scratch hoping to work their own way up to eventaully becoming ready to start "hiring". This whole approach to "CPU mining" is still in the startup / early-adopter stage; by the time it gets really sophisticated these early characters will be level 91 artisans, stinking rich, living in a large complex of caves of their own instead of at the racial starting-spot, and maybe "hiring" all the newbie Duergar at a nice profit to themselves. -MarkM- |
|
|
|
|
Well its not "really" mining, ultimately. It is just a way to let people use CPUs to rack up whatevers that determine how many coins you distribute to them, while also making what the CPU has to do multi-branched enough and adaptive enough that a botnet-operator would have a whole lot of pain trying to run thousands of machines doing it.
Though actually first step of all to discourage botnet operators is to charge a fee up front for an account, with the account only being able to have 10 characters with only 5 online at once. So a normal person, no problem, create five characters, run them all on scripts, have another five if you like for fun stuff scripts won't handle, so you can play for fun too when you want.
So basically make five artisans, as they get experience just doing chores like mining, chopping wood, digging for gems, drilling for oil or honey or whatever; run them 24/7 on scripts, then for fun maybe make a warrior or whatever to go exploring and hacking and so on to maybe make discoveries that could lead to finding some good things to add to your scripts. Log out one of the artisans whenever you want to play the warrior.
A botnet operator though, oh boy, world of hurt waiting. Even if you did manage to get thousands of accounts set up, even if you did get five artisans running on each, one warrior could maybe throw them off-script, or kill them over and over, or just loot or whatever. Though maybe you could try to get all the characters accepted into some safezone community or something where they'd be protected. But again that would take human interaction, each character chatting with others to arrange such things etc.
So its designed not only for CPU but also to want at least enough human operator intervention from time to time to make botnetting it impractical. At least until the scripts people develop get really really sophisticated, far beyond the point they have developed so far.
It is intended to bring back the being able to run unattended CPU programs to rake in money while also not being so totally lacking in need for a human to check it from time to time as to make botnetting it impractical. Since part of the fun of CPU mining when you are not some kind of server-farm operator or botnet is being there watching it, counting your coins as they come in and all that, having things the human operator can constantly fiddle with and optimise and so on is part of the appeal of the idea, at least that is the theory. People with oodles of money will likely figure heck with that I'll just buy it on exchanges. So hopefully it'd mostly be done by people who actually lack other sources of money enough to make it seem to them a great deal to just keep firing up more "miners" on their one little raspberry pi or laptop or desktop or whatever increasing their income day by day as they build up a larger and larger community of "miners" run by scripts on their machine. People with lots of time on their hands will run lots of "miners" on their machine, people with better things to do can just buy on exchanges from the people who have time to spend optimising such "miners".
-MarkM-
|
|
|
|
|
You forgot to mention starting difficulty. 300 blocks is how many seconds if starting difficulty is not set reasonably?
-MarkM-
|
|
|
|
|
Well if you are looking for coins an ETF type thing might like, forget scrypt until/unless ASICs are built for it. A startup wanting to do a real IPO or ETF or whatever based on scrypt would presumably be best served by first creating scrypt ASICs. Maybe to keep to itself even, but if that were the case then maybe implement itself as 5 or more seemingly completely separate companies so it won't seem like just one company/entity has all the ASICs. (Maybe make one manufacturer company and five "customer companies" who "buy" semi-exclusive access (exclusive to only five companies) to buying the ASICs once they are manufactured, or something.)
Without ASICs, all the scrypt blockchains are toys, sandcastles any "big bully" can kick over any time...
-MarkM-
|
|
|
|
Use the new concept of " CPU mining" developed specifically for distributing coins, not for securing blockchains! -MarkM- |
|
|
|
|
Show Posts
