Pages:
Author

Topic: GLBSE - request for next features (Read 27744 times)

sr. member
Activity: 252
Merit: 250
October 07, 2012, 12:20:15 PM
Hmm, having a working site (or even, any news) would be a definite improvement over the current situation.

i liked the uncertainty more. but good catch, working service is much better than no service.

Perhaps it is time or Nefario to lock this thread? I don't think he needs suggestions anymore.

he did not write any public post since September 26 or 25


At least he visited the forum today. He didn't do even that for a few days, if I remember correctly.
sr. member
Activity: 462
Merit: 250
October 07, 2012, 10:38:58 AM
Hmm, having a working site (or even, any news) would be a definite improvement over the current situation.

i liked the uncertainty more. but good catch, working service is much better than no service.

Perhaps it is time or Nefario to lock this thread? I don't think he needs suggestions anymore.

he did not write any public post since September 26 or 25
hero member
Activity: 518
Merit: 500
October 07, 2012, 06:56:41 AM
Hmm, having a working site (or even, any news) would be a definite improvement over the current situation.

i liked the uncertainty more. but good catch, working service is much better than no service.

Perhaps it is time or Nefario to lock this thread? I don't think he needs suggestions anymore.
sr. member
Activity: 462
Merit: 250
October 06, 2012, 03:43:57 PM
Hmm, having a working site (or even, any news) would be a definite improvement over the current situation.

i liked the uncertainty more. but good catch, working service is much better than no service.
sr. member
Activity: 252
Merit: 250
October 04, 2012, 06:26:47 PM
Hmm, having a working site (or even, any news) would be a definite improvement over the current situation.
donator
Activity: 3108
Merit: 1166
October 03, 2012, 10:31:29 AM
Yubikeys have been added as a method of two factor authentication.

Currently supported are standard yubikeys (ordered from Yubico).

We will add support for MtGox Yubikeys once I get the key in the post.

Nefario.

I assume that it is safe to use the same Yubikey then on different sites & the key generates a code that is specific only to that site at that time rather than one that could say also be used to also access Mt. Gox if one had the password too, sry for my lack of knowing the tech for these & thanks for having implemented this - I much prefer Yubikeys to other 2FA as I don't have a smart phone.
legendary
Activity: 910
Merit: 1000
Quality Printing Services by Federal Reserve Bank
September 26, 2012, 10:17:56 AM
Please add a P/L (profit loss) statement for all the public investment portfolios that have sold it's shares to the public. 
1) Report has to show all the holding at the beginning of the period and at the end.
2) What has changed
3) Div's received
4) BTC in and out
5) Gain or loss from trades grouped by security and unrealized gain/loss for the period.
6) Share transfers in and out (swaps etc)
7) ... (feel free to update the list)

If this report is delayed by 24 h, it's OK by me. No need to show what happens in real time. Smiley
And please, make it mandatory to all investment "companies" or even mining co's, that have bought shares from GLBSE. 

Those whacky spreadsheets, with zero information on what has actually happened in the portfolio, have to go.
Those "reports" are useless and too easily manipulated by portfolio manager.
hero member
Activity: 602
Merit: 513
GLBSE Support [email protected]
September 26, 2012, 01:07:46 AM
Yubikeys have been added as a method of two factor authentication.

Currently supported are standard yubikeys (ordered from Yubico).

We will add support for MtGox Yubikeys once I get the key in the post.

Nefario.
member
Activity: 74
Merit: 10
September 25, 2012, 05:33:42 PM
is it possible to post a bid/ask via api?
hero member
Activity: 532
Merit: 500
September 24, 2012, 07:39:47 PM
It'd be nice to be able to fetch the history csv with the private API.
And dividends with the public API.

+1

I think dividend payments should have its own twitter feed or an API like cryptostock has where a user can request the latest trades of x number of days.  Right now if a user wants to get the latest dividend payments for the assets, he needs to call all the active listings and pull the dividend API, which gives the entire history of dividend payments.

The last dividend information was added to the public API last week.  I'm already generating automated statistics using them.

I was referring to more of a history of dividend payments but with the ability to limit the range that the API returns.
hero member
Activity: 532
Merit: 500
September 24, 2012, 07:36:50 PM
It'd be nice to be able to fetch the history csv with the private API.
And dividends with the public API.

+1

I think dividend payments should have its own twitter feed or an API like cryptostock has where a user can request the latest trades of x number of days.  Right now if a user wants to get the latest dividend payments for the assets, he needs to call all the active listings and pull the dividend API, which gives the entire history of dividend payments.

I thought you couldn't pull list of dividends assets paid.  Undecided

Produces a full history of dividends paid.

https://glbse.com/api/dividends/asset/GIGAMINING
donator
Activity: 4760
Merit: 4323
Leading Crypto Sports Betting & Casino Platform
September 24, 2012, 07:32:28 PM
It'd be nice to be able to fetch the history csv with the private API.
And dividends with the public API.

+1

I think dividend payments should have its own twitter feed or an API like cryptostock has where a user can request the latest trades of x number of days.  Right now if a user wants to get the latest dividend payments for the assets, he needs to call all the active listings and pull the dividend API, which gives the entire history of dividend payments.

The last dividend information was added to the public API last week.  I'm already generating automated statistics using them.
member
Activity: 74
Merit: 10
September 24, 2012, 07:31:41 PM
It'd be nice to be able to fetch the history csv with the private API.
And dividends with the public API.

+1

I think dividend payments should have its own twitter feed or an API like cryptostock has where a user can request the latest trades of x number of days.  Right now if a user wants to get the latest dividend payments for the assets, he needs to call all the active listings and pull the dividend API, which gives the entire history of dividend payments.

I thought you couldn't pull list of dividends assets paid.  Undecided
hero member
Activity: 532
Merit: 500
September 24, 2012, 07:07:06 PM
It'd be nice to be able to fetch the history csv with the private API.
And dividends with the public API.

+1

I think dividend payments should have its own twitter feed or an API like cryptostock has where a user can request the latest trades of x number of days.  Right now if a user wants to get the latest dividend payments for the assets, he needs to call all the active listings and pull the dividend API, which gives the entire history of dividend payments.
sr. member
Activity: 252
Merit: 250
September 24, 2012, 07:05:50 PM
Allowing people to place multiple bids with the same BTC results in lots of what I see as spam orders, it's happened every time I've allowed it.
What's wrong with spam orders? Just the graph? That's been useless forever. Other than spam orders that already mess up the graph, there's nothing wrong with them. They'll either get auto-removed or filled by a seller, which makes them real orders.

Just think about what information all those orders are giving.

Imagine I have 1 btc in my account. I go to my favorite asset and place 100 bids of 1 btc for that asset. Now when anybody looks at the order book they see that asset has 100 btc of liquidity at 1 btc. They then make decisions based on that information, perhaps they decide to buy some since the price has so much support. Then as soon as anybody sells one of those assets to me, even though I only spent 1 btc that 100 btc of support disappears. Essentially, it distorts the information available to the market, resulting in phantom support.

Not so bad. People will know that support means less.

Maybe we could provide a "weighted support" separate info, where coins used n times are weighted 1/n?

Now the support could equally disappear overnight, just because the owner decided to rather place an order somewhere else.

Does liquidity mean so little these are real problems? It would be quite an improvement in my view.
member
Activity: 74
Merit: 10
September 24, 2012, 06:52:16 PM
It'd be nice to be able to fetch the history csv with the private API.
And dividends with the public API.

+1
hero member
Activity: 518
Merit: 500
September 23, 2012, 12:01:23 PM
Allowing people to place multiple bids with the same BTC results in lots of what I see as spam orders, it's happened every time I've allowed it.
What's wrong with spam orders? Just the graph? That's been useless forever. Other than spam orders that already mess up the graph, there's nothing wrong with them. They'll either get auto-removed or filled by a seller, which makes them real orders.

Just think about what information all those orders are giving.

Imagine I have 1 btc in my account. I go to my favorite asset and place 100 bids of 1 btc for that asset. Now when anybody looks at the order book they see that asset has 100 btc of liquidity at 1 btc. They then make decisions based on that information, perhaps they decide to buy some since the price has so much support. Then as soon as anybody sells one of those assets to me, even though I only spent 1 btc that 100 btc of support disappears. Essentially, it distorts the information available to the market, resulting in phantom support.
hero member
Activity: 784
Merit: 1000
0xFB0D8D1534241423
September 22, 2012, 08:06:00 PM
Allowing people to place multiple bids with the same BTC results in lots of what I see as spam orders, it's happened every time I've allowed it.
What's wrong with spam orders? Just the graph? That's been useless forever. Other than spam orders that already mess up the graph, there's nothing wrong with them. They'll either get auto-removed or filled by a seller, which makes them real orders.
legendary
Activity: 2940
Merit: 1090
September 22, 2012, 06:45:02 PM
The way Open Transactions handles multiple offers made with the same assets is to check the offer when someone clicks on it, to see if the person offering still has enough balance to execute the offer.

That way a person with for example 100 bitcoins could make 100 bitcoin offer on every market of every asset, but as soon as one of them is taken up the rest become vapourware that will vanish as soon as someone clicks on one to see if it is still good.

This is kind of a compromise between allowing people to express an interest in "whichever I can get first out of all these possibilities any one of which I will accept" and allowing those who care whether an offer they see in the orderbook is real or not to be able to check by forcing it to go look whether it still has funds enough behind it to make it real.

Since it is in any case extremely inefficient to have people constantly polling the server asking what offers exist most likely a ticker will be added so that offers can all be published somewhere other than the server's own API to take the polling load off of the server, whereupon the concept of "depth" will in any case become moot since it can be expected that most offers that would otherwise be on the books will instead be out in the wild watching the ticker ready to respond to any offers that appear on the ticker that they like.

-MarkM-
hero member
Activity: 686
Merit: 500
Wat
September 22, 2012, 06:23:31 PM
Allowing people to place multiple bids with the same BTC results in lots of what I see as spam orders, it's happened every time I've allowed it.

The only way to improve liquidity is to have more BTC on there, either in the form of peoples own BTC or margin.

Actually, at the bitcoin conference Meni was telling me that margin also performs the same functionality more or less as options. I didn't quite understand it at the time (I was pretty tired) but this is one of Meni's strengths.

Margin trading would definitely increase liquidity since you could place more orders on the same btc balance.
Pages:
Jump to: