.

[piotr_n]

What happens when the lag changes?

I don't think a few seconds, this or that way, really matters, since (from what I saw) it still takes at least 20 seconds for the GLBSE engine to process all the transaction, after all.

[1714953444]

1714953444

[imsaguy]

or he can just get the buy button ready, watch his computer tick, and click.

Wasn't it stated earlier that missing a bus because it is late is worse than waiting a for a late bus?

Are you naive enough to think that just because its scripted its going to magically happen on :00?  

[rdponticelli]

The option to place an order at a given, precise time, should be in the trading platform itself. That's the only way of doing it right. Anybody has asked Nefario if he plans to implement it?

[stochastic]

or he can just get the buy button ready, watch his computer tick, and click.

Wasn't it stated earlier that missing a bus because it is late is worse than waiting a for a late bus?

Are you naive enough to think that just because its scripted its going to magically happen on :00?  

It will if it is written correctly.

[imsaguy]

The option to place an order at a given, precise time, should be in the trading platform itself. That's the only way of doing it right. Anybody has asked Nefario if he plans to implement it?

That we have asked for.  I've not heard when it will be done.

[imsaguy]

or he can just get the buy button ready, watch his computer tick, and click.

Wasn't it stated earlier that missing a bus because it is late is worse than waiting a for a late bus?

Are you naive enough to think that just because its scripted its going to magically happen on :00?  

It will if it is written correctly.

The very things that can happen with humans can happen with computers.  Part of the reason things haven't fired correctly in the past is because GLBSE is choking.  A script won't fix that.

[PatrickHarnett]

What happens when the lag changes?

I don't think a few seconds, this or that way, really matters, since (from what I saw) it still takes at least 20 seconds for the GLBSE engine to process all the transaction, after all.

That's an important point - having the exchange rattle through the transactions takes time.  

Also, as a bus, I only have one stop to make.

(and now I'm going to have to look up "Git" install thing)

[rdponticelli]

The option to place an order at a given, precise time, should be in the trading platform itself. That's the only way of doing it right. Anybody has asked Nefario if he plans to implement it?

That we have asked for.  I've not heard when it will be done.

Well, in the meantime, a guy pushing a button or a computer firing some simple script is almost equally imprecise...

[Sukrim]

Nef was asked multiple times for:
* Placing buy/sell orders at certain times in advance
* Paying dividends at certain times in advance
* Calling back bonds at certain times in advance

I think he knows and I think he's swamped in work + support questions atm. Hopefully he finds some time to do some development work on GLBSE, the recent API for outstanding shares was a great start!


You don't need git, it was just used as an example. Simply google "curl" and your preferred platform (windows, linux, os-x, freeBSD...) and you'll find an executable.

I bet my GLBSE bot is more precise than anyone pushing buttons...

[stochastic]

or he can just get the buy button ready, watch his computer tick, and click.

Wasn't it stated earlier that missing a bus because it is late is worse than waiting a for a late bus?

Are you naive enough to think that just because its scripted its going to magically happen on :00?  

It will if it is written correctly.

The very things that can happen with humans can happen with computers.  Part of the reason things haven't fired correctly in the past is because GLBSE is choking.  A script won't fix that.

The script won't fix the time it takes in GLBSE to process the orders, but it will remove human error from the time it takes to manually click the sell button.

[imsaguy]

The option to place an order at a given, precise time, should be in the trading platform itself. That's the only way of doing it right. Anybody has asked Nefario if he plans to implement it?

That we have asked for.  I've not heard when it will be done.

Well, in the meantime, a guy pushing a button or a computer firing some simple script is almost equally imprecise...

Exactly.  Leave as is and wait the 2 weeks or whatever it will take until he's got the real solution.  It'd be nice if after x time, trading was locked so even if his script take 30 seconds to execute, someone's not slipping another order in.

[piotr_n]

Nef was asked multiple times for:
* Placing buy/sell orders at certain times in advance
* Paying dividends at certain times in advance
* Calling back bonds at certain times in advance

GLBSE 2.0 is just what it it.
It deals with our assets, it requires good security practices, so you cannot just add features on daily basis.
I completely understand the guy that he doesn't want to change the code every day - its just dangerous.
Bitcoinica did chnage the code too often - and look what happened.

But the API they gave for buying and selling - it's brilliant. Very easy to use!
So just use it, scheduling the simple scripts at your own PC.

Though, sometimes it happens that there are connection errors, or the site is just down, or something - and then a single shot of a curl command may fail, and you need to repeat...
So please keep that in mind while getting on the bus

[stochastic]

...It'd be nice if after x time, trading was locked so even if his script take 30 seconds to execute, someone's not slipping another order in.

That does not sound good.  Single bonds are being auctioned off starting at a certain time.  If I came into the room and offerred more than the next person, then by auction rules I am entitled to receive that bond.

[PatrickHarnett]

I bet my GLBSE bot is more precise than anyone pushing buttons...

oh, but then there wouldn't be that lovely stochastic process involved - a bit of chaos is good for those precise bots

I think, back on topic, UTC 2:00:ish tomorrow there will be 3000 bonds placed as a sell order by a human.  The contract says the sale takes place at 2, but does not specify a time precision.  

(having a nice scheduled batch file or process might be good to play with - maybe I'll get my rasberryPi to do it)

[piotr_n]

I bet my GLBSE bot is more precise than anyone pushing buttons...

oh, but then there wouldn't be that lovely stochastic process involved - a bit of chaos is good for those precise bots

I think, back on topic, UTC 2:00:ish tomorrow there will be 3000 bonds placed as a sell order by a human.  The contract says the sale takes place at 2, but does not specify a time precision. 

(having a nice scheduled batch file or process might be good to play with - maybe I'll get my rasberryPi to do it)

I'm pretty sure rasberryPi does have curl on board by default.
though I've never put my hand on one so far, so cannot confirm

[imsaguy]

...It'd be nice if after x time, trading was locked so even if his script take 30 seconds to execute, someone's not slipping another order in.

That does not sound good.  Single bonds are being auctioned off starting at a certain time.  If I came into the room and offerred more than the next person, then by auction rules I am entitled to receive that bond.

Perhaps, but the whole point of having it scripted is that it happens near instant.  Taking 20 seconds means that even if the process to script it is automated, people can still game it... which then leads to why so much pressure to script the start if its just going to be gamed anyway?  Right?

[The00Dustin]

Perhaps, but the whole point of having it scripted is that it happens near instant.  Taking 20 seconds means that even if the process to script it is automated, people can still game it... which then leads to why so much pressure to script the start if its just going to be gamed anyway?  Right?

I'm not sure why people are sweating the seconds, the only way the seconds can be dealt with is at the server.  I'm also not sure why everyone is suddenly assuming that you can get a buy order in while the sale is processing.  One sale order is entered and it is then processed, who is to say the server isn't processing it completely before trying to process the next buy order?  I could see it working either way, but I thought someone posted about placing a buy order that didn't get filled even though orders lower than it got filled after it was placed.  This would have been several weeks ago, and I haven't been able to find it, but I have seen even less to indicate the opposite.  Regardless, if the opposite was true, then a human hitting the button 5 seconds early would be fine.

[stochastic]

...It'd be nice if after x time, trading was locked so even if his script take 30 seconds to execute, someone's not slipping another order in.

That does not sound good.  Single bonds are being auctioned off starting at a certain time.  If I came into the room and offerred more than the next person, then by auction rules I am entitled to receive that bond.

Perhaps, but the whole point of having it scripted is that it happens near instant.  Taking 20 seconds means that even if the process to script it is automated, people can still game it... which then leads to why so much pressure to script the start if its just going to be gamed anyway?  Right?

The point of having it scripted is that if PPT.A is to start selling at 01:00:00, for example, then it should start selling at 01:00:00.  The process it takes to finish the selling is a whole other topic.  Otherwise you are allowing bids and the auction to be done before 01:00:00 and then ending the auction at 01:00:00.

[PatrickHarnett]

I'm pretty sure rasberryPi does have curl on board by default.
though I've never put my hand on one so far, so cannot confirm

Well, I've loaded a Debian install on it (so I get to play with that too), and after I pick up a spare HDMI cable, playing with it should fill in time until I hit the sell button.

Could be an interesting week as there will be 7680 BTC paid out prior to the PPT.D auction.

[MrTeal]

It's going to be interesting to see what kind of average selling price we'll see on tomorrow's auction. There's going to be 7680 shares payed out and only 3000 up for auction, so it might push prices higher than the last couple auctions. There's good prices on other PPT issues though, so that might help absorb some demand. There's 800 shares of PPT.C at or below 1.11 right now, and 1.28/1.11 is a 15.3% return for 3 weeks. That's basically the same weekly return as a PPT.D selling for 1.06. I actually snagged a few shares of PPT.A overnight for 1.16, which is a 10.3% return for over 9 days. Both PPT.A and PPT.C are really undervalued right now, IMO. The last sale price of PPT.A is only 0.01BTC more than PPT.B.

I'm going to make a wild guess here and predict an ASP of 1.07.