I tried to create new asset.
filled in SYN2 data, similar to previous ipo with only 1 difference

the time was only "1 minute" instead 1 minute from now
after hitting the create button an error msg appeared on top
and the form filled in data are gone, have to retype them

not a serious issue but usability suffered right now.

release 11/3/2012
low prio

I have no open buy order
my only previous buy order was filled
i still see "BTC reserved for orders:6.0"

in version updated on:11/MAR/2012

the only things i did before that was to try to screw the buy form with text where numbers were expected
and an IPO. can't tell if there were some variable debris from the previous buy that was not validated and created or just bug in the script.



slightly off topic, is a guide to 2.o available somewhere?
don't know why/how to switch between accounts and where the IPO stock would appear. would like to test trade more carefully but seems that only 1 asset managed to issue stocks and offer them for sale.

at least a quick cheat sheet how to schedule the IPO (1 minute from now did not work for me)

open your mind and learn this

the trust records (given/received ratings) are viewable over http / web
each user has a pgp keypair & has uploaded his public key to a key server so that other may find it easily
every web of trust user is registered also with the service and this is done in IRC (see first reply for a command that will show you a help message what to do on irc), there is a nice guide linked from bitcoin-otc, i think they have a wiki for this with a step by step guide.

so my buggy guide is:
- read the available guides
http://dylblog.com/2011/06/05/how-to-join-in-with-bitcoin-otc-the-easy-way-osx/ is my favourite, steps should be the same also for non mac os users; this guide is from the ofic source http://wiki.bitcoin-otc.com/wiki/OTC_Rating_System
- follow the guide (generate yourself a pgp keypair, register with irc/freenode, upload keys)
- get/give ratings

requires pgp/gpg & irc skills

by "I have plenty of those. " I ment I have both types and wondered if next rounds would be restrike of what I have already or something new (caro or other muster in the B). and I wondered if he still sits on a stock of the later type. I'm thinking about reopening bitcoin collectibles per mail and looked how's the availability if I sell of my rounds (i think i'm 40/60 now, won't count them)

is down for me
(glbse 1.0 prod)

POST
Variable    Value
blog    
""
company_name    
"ThumbUp"
contact_email    
"ne@nada.va"
contract_text    
"quick brown f ..."
link_to_accounts    
""
majority_percentage_change_contract    
"51"
majority_percentage_general_motion_pass    
"51"
majority_percentage_issue_shares    
"51"
proposal    
"please highlight this field, put it in a frame or something. I almost left it empty"
selling_shares    
"1000"
short_description    
"Thumb up your *"
ticker_symbol    
"TICK"
time    
"1 minute"
twitter    
""
website    
""

I get a ruby error page for the values above. I'd prefer the red warning stripe on top of page instead.
It also show the ruby err page if I fill in all fields. can't figure out what's wrong or how to workaround this.
Can't IPO, done with testing for now

u no want see tx id first?

I'd like to remind you that a day has 24 hours and if you cant finish your tasks during the day, work at night as well


I read this
as 2.0 is closed source, 1.0 is closed source but will be open sourced.

would you also indicate (at least) release date as datum somewhere on the dev.glbse site? for more accurate tracking of bugs and better knowing when new testing is due.

what will happen to getsatisfaction.com ? you point to that in your own forum

Seems he's mining @~600-700 MHash/s for 6-7 weeks. not good at this type of math but he may have the coins.

@Rubberduckie: the mood is bad here, lot of people try fishy things while offering btc for sale, be patient with us.
do you use web of trust with bitcoin-otc.com by any chance?

thumbs up for improvements on that (input validation), is badly needed

while whining over the soon to be gone design of the 1.0 web client I was thinking if the API would be powerful enough to allow custom clients and the reimplementation of the current design (or something of comparably elegant and simple) as I can't get used to the new look & feel. let's see what the dev version brings and post a handful of new bugs found (I know at leas one more dedicated user who's willing to sync and perform coordinated testing once you release something new).

would you mind to indicate & update the version already since software is in this pre-release state? it would help the guerrilla testers to better reference bugs' affect/fix versions and allow better focus on what needs to be retested between the site updates. without release notes it's hard to track versions of what is to be tested. it would also help to know where you version the code and maybe add some lyrics //comments to your code if it's going to be public. not volunteering developing but willing to help with the release mgmt folklore and QA in general.
either as a date/timestamp of the code that you install in glbse or incrementing in old fashioned way 2.01, 2.02 etc.

the uptime checking of glbse 1.0 would not be that difficult. I strongly humbly recommend using it as long as possible. because
1) i like it more
2) it has great record of security (not yet been compromised afaik, surely not only due to the epic downtimes but also because of the quality of the current code, and the use of webkeys -  should be pretty hard to brute force)
3) has only minor defects which do not affect functionality (create buy or sell that is paired immediately and it won't display list of tx that result from that closing; one has them the other not, not sure which one is which. history in web client is limited to 10 entries; the python client can browse full history. some history pages sort newest first, some sort the other way.)

they look fine. the source of light that is visible there is slightly shifting from ball to ball which is correct as the relative position of light source to the shiny surface is different for each ball. (my room mate used to teach 3D modelling at art school, my understanding of this topic is little bit better than average joe's)

the most innovative approach to monitor own site's uptime
one more reason to use glbse

depends which type you restrike. got both and wonder which is next. if I recall it well, type 2 is the dye that should be used. I have plenty of those. just was wondering why this thread did not refresh since 'ever' while it looked like you sit on a stash of those rounds

I'm surprised they did not sold out yet

actually transfers work fine, thus if user A can transfer to user B glbse is up
and we don't need the QA sathoshi valued asset and limitations around it
who can and who can't trade it : ) if test would be based on transfer use case

if we get asset with ask .0000002 and bid .00000001 total 1000 issues we could sell back and forth with any user even w/o additional code.
wait, someone could buy up all the stock and screw the test script ... it could work however if we behave and/or the test script would check if there is open sell order an release ~5 shares each hour for testing ... if we keep talking satoshi valued stock, should be no problem to fund such tests with real bitcoin and follow official rules. just maybe tweak the twitter stream not to publish this asset. anyway it would be probably a bit of working (and maybe twitter QA msgs would be appreciated if it's reasonable amount per day, like only make a trade if there was no activity last 60 minutes; assuming such a script would be run hourly)

thanks for the update.
looks like the most predictable earning available : )
... and I will do my homework and fetch at least one peace from each asset I watch

for the BTCSYN there was a short lived rumor to pay out an early dividend to celebrate ipo but otherwise they seem to stick to the by laws and monthly frequency (they're reasonable and might change that in the future but since they plan to keep 80% of income for new hw purchases, weekly dividend might look to small in comparison to MergedMining and other stock that prefers higher payout than reinvesting and more pays dividends more frequently)

let me speculate that there are 6000 shares now publicly trading.
the bitcoin held is constantly rising thus no purchase took place yet.
if I only bought 1 share yesterday to get the payout per share info ...

I liquidated my 5% share in MergedMining to hop on the syndicate IPO train.
thus i did not receive any dividends lately from this company.
I observe glbse since a month or so and noticed in the previous weeks that the MergedMining dividend was stable at .001 per share and rising payout means more and more shares reach circulation (public trading). not all of the 10.000 shares were sold initially. OgNasty sells them slowly to raise capital for new mining hardware and the only method to find out how many there are is to get the dividend payout data and do a little math.