Live data from Hacker News

Show HN: Investorsexchange.jl – parse trade-level stock market data in Julia

github.com

41–50 of 71 posts

Re: Show HN: Investorsexchange.jl – parse trade-level stock market data in Julia

#41
post #8

When you say they give out the raw data for free, does this mean you can download a batch of it? Or are you referring to the free API for the 5 years/30 day data on the bèage you linked?

Referring to these gzipped daily (two formats) dumps I think: https://iextrading.com/trading/market-data/

API only needed for live (incl. past day) and more convenient granular access/computations it seems.

Re: Show HN: Investorsexchange.jl – parse trade-level stock market data in Julia

#42

Earlier quoted context omitted.

Not just the old internet! Ever considered visiting the Sierra Nevadas? Well there's a wonderful, outdoorsy place in California that's just waiting to welcome you: Lake Tahoe! Visit, uh, gotahoe.com, and keep in mind that the Nevada border, where certain things unrelated to outdoor sports are entirely legal, is right there.

https://wikipedia.org/wiki/Scunthorpe_problem

Sort of? "Tahoe" isn't the problem. Sure, "hoe" is a substring of "tahoe" but it's pretty clear that "tahoe" is a placename in a string like "visitlaketahoe.com". IMO they absolutely knew what "gotahoe.com" would be parsed as, it's very clever. It'd be a Scunthorpe if the site was getting flagged for "hoe", but it's a parsing problem at the user layer, not censorship elsewhere.

Re: Show HN: Investorsexchange.jl – parse trade-level stock market data in Julia

#44

Earlier quoted context omitted.

I entered this post knowing I would upvote this comment.

I too am here for this reason also. I would change the name. It is an issue. Put a dash in it or an underscore... just something.

You would be surprised by just how many investors are looking for this type of surgery...many many people.

Re: Show HN: Investorsexchange.jl – parse trade-level stock market data in Julia

#45

Earlier quoted context omitted.

https://wikipedia.org/wiki/Scunthorpe_problem

Sort of? "Tahoe" isn't the problem. Sure, "hoe" is a substring of "tahoe" but it's pretty clear that "tahoe" is a placename in a string like "visitlaketahoe.com". IMO they absolutely knew what "gotahoe.com" would be parsed as, it's very clever. It'd be a Scunthorpe if the site was getting flagged for "hoe", but it's a parsing problem at the user layer, not censorship elsewhere.

Yeah, it's more a "CU in the NT" https://ntunofficial.com

Re: Show HN: Investorsexchange.jl – parse trade-level stock market data in Julia

#46

Earlier quoted context omitted.

My employer did some work early in Dotcom for a company that owned the domain name "manufacturersexchange", when I pointed out that was a terrible name for a business they said "no business person would notice that". Business never got off the ground.

I mean even with a dash it's really not a very good name for a business. What does the company even do? Mind you, self-descriptive company names and domains are more useful for local small businesses; big ones like Google start to get their own meaning. ycombinator? What?

Some businesses really can benefit from a good or memorable domain name.

But that market is much, much smaller than it used to be, and most businesses can live or die no matter what their domain name is.

Re: Show HN: Investorsexchange.jl – parse trade-level stock market data in Julia

#47

Earlier quoted context omitted.

https://wikipedia.org/wiki/Scunthorpe_problem

Sort of? "Tahoe" isn't the problem. Sure, "hoe" is a substring of "tahoe" but it's pretty clear that "tahoe" is a placename in a string like "visitlaketahoe.com". IMO they absolutely knew what "gotahoe.com" would be parsed as, it's very clever. It'd be a Scunthorpe if the site was getting flagged for "hoe", but it's a parsing problem at the user layer, not censorship elsewhere.

[deleted]

Re: Show HN: Investorsexchange.jl – parse trade-level stock market data in Julia

#49

Earlier quoted context omitted.

https://wikipedia.org/wiki/Scunthorpe_problem

Sort of? "Tahoe" isn't the problem. Sure, "hoe" is a substring of "tahoe" but it's pretty clear that "tahoe" is a placename in a string like "visitlaketahoe.com". IMO they absolutely knew what "gotahoe.com" would be parsed as, it's very clever. It'd be a Scunthorpe if the site was getting flagged for "hoe", but it's a parsing problem at the user layer, not censorship elsewhere.

> they absolutely knew what "gotahoe.com" would be parsed as, it's very clever

I'm not so sure :) goblah.com is one of the most popular tourism domain configurations that exist.

Post reply on HN