HN user

efishnc

46 karma
Posts4
Comments16
View on HN

As @mplewis said, because it uses the SV API - however, I've since found a way to reduce that cost to practically 0. See https://loichovon.com/posts/streetview-scraper-v2.html

As you say though, another way to go about this would be to scrape the public SV site, which I have not attempted to do. @xnx linked this project in another comment, which seems to do just that: https://tllabs.io/google-street-view-hyperlapse-youtube-vide...

I don't know if/how they evade captchas.

Ahh I see, those hyperlapses look very cool!!

Going back to your first comment, I originally made this as part of an app with an interactive streetview component. I reused the initialization code I had as the base for this. Re-using that code also makes sure the screenshots taken would be close as what you'd see using the embedded streetview (In our project we had a bunch of remote locations without a lot of SV images, so depending on the search radius used when querying for a panorama, we could end up in vastly different places).

However, I realize that I never even considered scraping the public site, which would allow for hiding your identity by not needing an API key. I'll think about this.

What could be nice is the developer providing some unit tests, and Second using those to ensure the PR is functional, re-generating if not.

Given a set of tests, I guess you could try to generate the code as well, though I could imagine it might overfit on the given tests and create a "hack" solution.

I actually find that I'm more awkward online/in chats than IRL.

The fact that you have longer to think about your messages and modify them before publishing, that you have to think carefully so as not to multi-text (which seems desperate), that you don't have access to non-verbal cues for context, can't smile etc. all contribute to this.

Maybe that's the problem.

We're trying to train a full composer AI without allowing to learn about different instrument sections independently at first. The human composer will have a good idea of the different parts and know how to merge them in harmony.

I think we might get better results training separate AI systems on percussions, strings, vocals etc. then somehow create connections between them so they learn together. A band AI if you will.

We could try a BERT for each, with the generator learning to output logical sequences of sounds instead of words.