News for hackers. Stuff that matters.
Re:Why it’s hard to kill the Bloomberg terminal (2019) by lordnacho on Monday July 20, 2020 @04:11PM (#23901404)
Surely not? You can decide what exchanges you want to pay for.

FICC prices are also not quite that easy, there's a number there but what it means varies according to how you're configured. Things like the closing time and what sources go into the rate make a difference.

I spent a lot of time talking to bbg about what all the settings were.

Re:Why it’s hard to kill the Bloomberg terminal (2019) by londev on Monday July 20, 2020 @05:51PM (#23902280)
As an example of what exchanges charge for licensing the data (not including a feed for the data, just a licence to use it) I have to pay £18k/year just for a London Stock Exchange licence. Then I have to pay for the feed.

Charging for access to the data feed seems fair enough, but licensing the data? For a company that has a monopoly over what I consider public data £18k is outrageous.

Re:Why it’s hard to kill the Bloomberg terminal (2019) by cm2187 on Monday July 20, 2020 @04:18PM (#23901454)
yeah you can pay for some additional feeds. But my point is that the base terminal that costs $20,000 a year doesn't come with the sort of live equity feeds that you find for free on google or yahoo finance.
Re:Why it’s hard to kill the Bloomberg terminal (2019) by lordnacho on Monday July 20, 2020 @04:36PM (#23901632)
The exchanges make huge amounts of money off live price feeds. Wrongly IMO, but that's another tangent.

Basically there's no way they would let a player like Bloomberg forward that kind of data to their users without getting paid a lot. In fact if you work in HFT you might have heard of something called a non-display fee which is a kind of ransom money they make that kind of firm pay.

Consumers like the ones who look at finance websites are probably not people they care to market to. Hence someone like investing.com can cut a deal to show live prices. They're not depth and pretty slow in any case.

But basically Bloomberg do not own the equity prices, the exchanges do.

Re:Why it’s hard to kill the Bloomberg terminal (2019) by clausok on Monday July 20, 2020 @05:27PM (#23902109)
I've been waiting 15 years for litigation in this arena. If prices, like player statistics from an NHL game, are historical facts which can not be copyrighted, why don't we have better and cheaper public market data API's by now? How have the exchanges been able to maintain a stranglehold over distribution of historical facts?
Re:Why it’s hard to kill the Bloomberg terminal (2019) by lokar on Monday July 20, 2020 @07:23PM (#23902925)
Their regulator(s) support them selling it. And they can easily cut anyone off for re-distributing it (in addition to any legal remedy they may attempt).
Re:Why it’s hard to kill the Bloomberg terminal (2019) by gruez on Monday July 20, 2020 @08:03PM (#23903150)
> And they can easily cut anyone off for re-distributing it (in addition to any legal remedy they may attempt).

AFAIK that's what grsecurity does. They distribute linux patches, which aren't copyrightable because they're GPL. To prevent anyone from distributing their patches openly (and putting them out of business), they have a clause in their contracts saying that if you distribute their patches, they'll terminate your subscription.

Re:Why it’s hard to kill the Bloomberg terminal (2019) by thebean11 on Monday July 20, 2020 @04:59PM (#23901849)
Are the feeds on Yahoo and Google actually up to date? I was pretty sure Google was on a long (like >1m) delay.
Re:Why it’s hard to kill the Bloomberg terminal (2019) by ivalm on Monday July 20, 2020 @10:12PM (#23903764)
Investing.com is live. But also most (all?) of retail brokerages are live.
Re:Why it’s hard to kill the Bloomberg terminal (2019) by isatty on Tuesday July 21, 2020 @01:51AM (#23904605)
Looks like my retail brokerage didn’t get the memo. I get 15 minutes delayed data unless I subscribe to the exchange AND OPRA on top of my trading and holding fee.