[ANN] GLBSE has a new look! | Bitcointalksearch.org

The00Dustin

hero member

Activity: 807

Merit: 500

Quote from: MrTeal on May 02, 2012, 10:28:04 AM

Quote from: stochastic on May 01, 2012, 10:45:27 PM

Quote from: bitfoo on May 01, 2012, 10:44:24 PM

The new look is great, API is appreciated too (haven't looked into it yet, but will do soon).

I've almost made a wrong trade twice due to the following mixup:

I see "ASK 0.622" and instinctively go to put my own ASK there, type in the qty and price, and then realize that the button next to it is labeled "BUY", which is not exactly what I wanted to do. Maybe removing the words "ASK" and "BID" or making them much smaller than "BUY" and "SELL" would help? On Bitcoinica, for example, the BUY and SELL buttons are big enough that they draw attention first and there's no confusion.

I did the same thing.

As did I.

glad to see I'm notalone here...

REF

hero member

Activity: 529

Merit: 500

Quote from: Nefario on May 06, 2012, 10:51:32 PM

Quote from: teek on May 06, 2012, 04:01:07 PM

@Nefario - I read somewhere that there was no fee to issue a sub-asset, but I just issued some new assets and was charged a fee for the sub assets? Has this changed? I don't see a link to the fee schedule anywhere on the site? (I could be blind.. lol)

teek

Hi Teek,
All you're fees can be seen here https://us.glbse.com/portfolio/fees after logging in.
That link shows from the asset page when logged in.

Regarding fees for sub-assets there has always been fees for them, and we've never said any different.

It also shows you the fee you will be charged right above the "Create" button when creating an asset.

Quote

Fee

You will be charged 8.0BTC to create this security, this charge is not refundable.

tested us.glbse. i live in the US. it is a little fast the biggest improvement if that there are no large spikes.

pings to glbse.com

Code:

C:\Documents and Settings\LaptopXP>ping -t glbse.com

Pinging glbse.com [67.222.146.58] with 32 bytes of data:

Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=56ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
[color=red]Reply from 67.222.146.58: bytes=32 time=160ms TTL=248[/color]
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=57ms TTL=248
Reply from 67.222.146.58: bytes=32 time=56ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
[color=red]Reply from 67.222.146.58: bytes=32 time=281ms TTL=248[/color]
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=49ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=49ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
[color=red]Reply from 67.222.146.58: bytes=32 time=258ms TTL=248[/color]
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=61ms TTL=248
Reply from 67.222.146.58: bytes=32 time=56ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=65ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
[color=red]Reply from 67.222.146.58: bytes=32 time=285ms TTL=248[/color]
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=49ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248

Ping statistics for 67.222.146.58:
Packets: Sent = 87, Received = 87, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 285ms, Average = 61ms
Control-C
^C

to us.glbse.com

Code:

C:\Documents and Settings\LaptopXP>ping -t us.glbse.com

Pinging us.glbse.com [67.222.146.58] with 32 bytes of data:

Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=49ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=57ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=57ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=55ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=54ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=61ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=50ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248
Reply from 67.222.146.58: bytes=32 time=51ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=53ms TTL=248
Reply from 67.222.146.58: bytes=32 time=52ms TTL=248

Ping statistics for 67.222.146.58:
Packets: Sent = 77, Received = 77, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 61ms, Average = 51ms
Control-C
^C

Nefario

hero member

Activity: 602

Merit: 512

GLBSE Support [email protected]

Quote from: gabbynot on May 08, 2012, 09:28:32 AM

Quote from: Nefario on May 04, 2012, 01:41:24 AM

For users on the American continent there is now https://us.glbse.com

If you're based in the US this will be about 3-5 times faster than glbse.com

The servers are located in the US?

The proxy server is located in the US.

gabbynot

sr. member

Activity: 341

Merit: 250

Quote from: Nefario on May 04, 2012, 01:41:24 AM

For users on the American continent there is now https://us.glbse.com

If you're based in the US this will be about 3-5 times faster than glbse.com

The servers are located in the US?

teek

hero member

Activity: 667

Merit: 500

Quote from: Nefario on May 06, 2012, 10:51:32 PM

Regarding fees for sub-assets there has always been fees for them, and we've never said any different.

I must have been thinking of something else. Thanks!

Nefario

hero member

Activity: 602

Merit: 512

GLBSE Support [email protected]

Quote from: teek on May 06, 2012, 04:01:07 PM

@Nefario - I read somewhere that there was no fee to issue a sub-asset, but I just issued some new assets and was charged a fee for the sub assets? Has this changed? I don't see a link to the fee schedule anywhere on the site? (I could be blind.. lol)

teek

Hi Teek,
All you're fees can be seen here https://us.glbse.com/portfolio/fees after logging in.
That link shows from the asset page when logged in.

Regarding fees for sub-assets there has always been fees for them, and we've never said any different.

It also shows you the fee you will be charged right above the "Create" button when creating an asset.

Quote

Fee

You will be charged 8.0BTC to create this security, this charge is not refundable.

teek

hero member

Activity: 667

Merit: 500

@Nefario - I read somewhere that there was no fee to issue a sub-asset, but I just issued some new assets and was charged a fee for the sub assets? Has this changed? I don't see a link to the fee schedule anywhere on the site? (I could be blind.. lol)

teek

BinaryMage

hero member

Activity: 560

Merit: 500

Ad astra.

Quote from: Nefario on May 04, 2012, 01:41:24 AM

For users on the American continent there is now https://us.glbse.com

If you're based in the US this will be about 3-5 times faster than glbse.com

Thank you. Quite an improvement, let me say.

Nefario

hero member

Activity: 602

Merit: 512

GLBSE Support [email protected]

For users on the American continent there is now https://us.glbse.com

If you're based in the US this will be about 3-5 times faster than glbse.com

OgNasty

donator

Activity: 4760

Merit: 4323

Leading Crypto Sports Betting & Casino Platform

Looks good Nefario. I'm looking forward to having some time to check out the API one of these days.

Nefario

hero member

Activity: 602

Merit: 512

GLBSE Support [email protected]

Quote from: ?? on ??

Re-posting from the other 2.1 thread ...

So ... at the risk of being perceived an insistant bloke ... whare's mah .csv history download ?

More seriously: this would be a *really* useful feature: my /portfolio page is
very long by now and is getting close to impossible to process by eyballs.

Another - probably simpler to implement - equivalent feature would be to have
the portfolio API call return *everything* that is visible in the /portfolio page.

Right now it only returns current stuff, not the whole history, whereas the
/portfolio page returns everything.

Maybe with an option ... something like:

https://glbse.com/api/portfolio/ID/KEY?opt=all

Right now, I am reduced to perl-parse the HTML output
of the /portfolio page ... giant PITA.

Thanks for considering the suggestions.

Hey znort987, I'll be adding csv for account details (buys/sells/deposits/withdrawals/transfers etc).

What would you think would be the best way to have this? By the month?

For the API we'll add a history function, where you can pull all your histories.

Nefario

hero member

Activity: 602

Merit: 512

GLBSE Support [email protected]

Trading fees have returned, currently only buy fee at 0.5%

MrTeal

legendary

Activity: 1274

Merit: 1004

Quote from: stochastic on May 01, 2012, 10:45:27 PM

Quote from: bitfoo on May 01, 2012, 10:44:24 PM

The new look is great, API is appreciated too (haven't looked into it yet, but will do soon).

I've almost made a wrong trade twice due to the following mixup:

I see "ASK 0.622" and instinctively go to put my own ASK there, type in the qty and price, and then realize that the button next to it is labeled "BUY", which is not exactly what I wanted to do. Maybe removing the words "ASK" and "BID" or making them much smaller than "BUY" and "SELL" would help? On Bitcoinica, for example, the BUY and SELL buttons are big enough that they draw attention first and there's no confusion.

I did the same thing.

As did I.

Nefario

hero member

Activity: 602

Merit: 512

GLBSE Support [email protected]

I'm working on speeding up the site.

Expect significant improvements in the next few days.

BinaryMage

hero member

Activity: 560

Merit: 500

Ad astra.

Quote from: Nefario on May 01, 2012, 11:15:30 PM

That's not really going to happen, they SHOULD be done but who's going to bother (unless there is money in it), so until then we'll try our best to do so.

GLBSE has a fairly well documented and easy to use API now, documentation here:
https://glbse.com/info/api

It covers live streaming, buy/sell, poprtfolio and market data.

You think buy/sell would be improved by sizing down the bid/ask text? I was wondering on how to reduce confusion on this.

Hmm.

Code:

curl -kG https://glbse.com/api/BFLS/TICKER

gets me a "Not Found".

Code:

curl -kG https://glbse.com/api/asset/BFLS

gets me "could not connect to host". Am I using the wrong URL?

EDIT: Ah, second one works now. Must have just timed out that once.

Nefario

hero member

Activity: 602

Merit: 512

GLBSE Support [email protected]

Quote from: stochastic on May 01, 2012, 09:48:44 PM

Quote from: gabbynot on May 01, 2012, 09:21:49 PM

Long-term, it'd be great for users to have their own "favorites" stocks they like to track, which could be set up through their preference settings. When GLBSE gets to be 300-400 stocks large, you want a way for users to visually pare that back a bit to just assets they're interested in.

A real-time streaming ticker would be awesome at some point, but that might be asking too much at this stage.

IMO all of these suggestions should be done by 3rd parties and not GLBSE. Does anyone go to nyse.com to track the stocks they are interested?

That's not really going to happen, they SHOULD be done but who's going to bother (unless there is money in it), so until then we'll try our best to do so.

GLBSE has a fairly well documented and easy to use API now, documentation here:
https://glbse.com/info/api

It covers live streaming, buy/sell, poprtfolio and market data.

You think buy/sell would be improved by sizing down the bid/ask text? I was wondering on how to reduce confusion on this.

stochastic

hero member

Activity: 532

Merit: 500

Quote from: bitfoo on May 01, 2012, 10:44:24 PM

The new look is great, API is appreciated too (haven't looked into it yet, but will do soon).

I've almost made a wrong trade twice due to the following mixup:

I see "ASK 0.622" and instinctively go to put my own ASK there, type in the qty and price, and then realize that the button next to it is labeled "BUY", which is not exactly what I wanted to do. Maybe removing the words "ASK" and "BID" or making them much smaller than "BUY" and "SELL" would help? On Bitcoinica, for example, the BUY and SELL buttons are big enough that they draw attention first and there's no confusion.

I did the same thing.

bitfoo

donator

Activity: 289

Merit: 250

The new look is great, API is appreciated too (haven't looked into it yet, but will do soon).

I've almost made a wrong trade twice due to the following mixup:

I see "ASK 0.622" and instinctively go to put my own ASK there, type in the qty and price, and then realize that the button next to it is labeled "BUY", which is not exactly what I wanted to do. Maybe removing the words "ASK" and "BID" or making them much smaller than "BUY" and "SELL" would help? On Bitcoinica, for example, the BUY and SELL buttons are big enough that they draw attention first and there's no confusion.

stochastic

hero member

Activity: 532

Merit: 500

Quote from: gabbynot on May 01, 2012, 10:23:45 PM

Quote from: Stochastic

Quote

Does anyone go to nyse.com to track the stocks they are interested?

No, but the NYSE isn't the custodian of everybody's assets, either.

A yahoo/google finance style site would be better considering there is more than one (and hopefully more) bitcoin denominated security exchange.

gabbynot

sr. member

Activity: 341

Merit: 250

Quote

Does anyone go to nyse.com to track the stocks they are interested?

No, but the NYSE isn't the custodian of everybody's assets, either.

Topic: [ANN] GLBSE has a new look! (Read 5351 times)