Hacker Newsnew | past | comments | ask | show | jobs | submit | kalli's commentslogin

Feels like the right thread to shamelessly plug my app that lets you do these types of walks/runs virtually: https://www.inthelongrun.app


Reflections on my great-grandparents time in New York.


Flashcards to help you train your shell keyboard shortcut muscle memory


It's based on popularity on Resident Advisor / RA (those are the clubs that had the most "followers" among their userbase)


This is a classic example of data sourcing bias.

RA is primarily used by independent promoters in the States, which tend to be much smaller and have smaller or less frequent events.

Large promoters who regularly throw events or have the budget for larger events would use their own promotion mechanisms and general population ad networks instead of listing on RA.


> Large promoters who regularly throw events or have the budget for larger events would use their own promotion mechanisms

No (at least in the US) - it’s because of exclusive contracts with the ticketing platforms.

Whereas you can list on RA and other platforms too, the biggest clubs and venues get lucrative deals with eg AXS to only list tickets on their platform.


That's ticketing. There's plenty of listings on RA that don't use RA's ticketing service.

Large promoters that use or have exclusivity deals with AXS or Ticketmaster/LiveNation or Dice still advertise/promote on platforms like Facebook/Instagram, EDM Train, Radiate, etc alongside the ticketing platform's promotion platforms.


RA is the biggest site for electronic subculture since forever, and it's an excellent resource to find out the cool stuff that happens in your city. I don't know why you consider it small, maybe it's a US thing? In Europe, RA is the best resource to find about parties and electronic music in general.


In case you didn’t know America’s music industry is run by cartels… I mean “unregulated monopolies”


What are you talking about ? RA is relevant for the UK at best, outside of that it seems a bit dead. In France everyone use Shotgun.


Author here, this is good to know.! I tried to spotcheck the regions and countries, but wasn't familiar with all of them so didn't want to make assumptions (and didn't make time to research them thoroughly). Not sure if/how I could try to correct that.

> This is the kind of "lore" that's impossible to catch from raw data.

Agreed this project definitely banged up against those sorts of walls a few times. Still think it's worth trying, hopefully the information offered one can find outweighs any distortions it introduces. Maybe something that should have been explicitly acknowledged in the piece.

> I like the Essential Mix visualisation even more! It's such a shame most of the other ones appear dead due to API changes.

Thanks, happy to hear that. I keep meaning to go back to the essential mix one, get new data and apply some of the stuff I've learned since!


If you click a club its region and country should be in its detail panel underneath their logo. The region and country filters should show you just the clubs in the given region/country.

Demographic analysis would have been interesting I agree, but I didn't know of a good data source for that and it's hard to parse from line up data (especially in places one isn't familiar with)


The technical details of a visualisation built around the lineups and programming at the world's most popular nightclubs.


D3 is the only charting library that I've loved.


Famously bearded philosopher Hannah Arendt? There's an Arendt/aren't joke in there somewhere.


This looks interesting. Longtime user of the Vscode-restclient, but have been moving over to httpyac lately for the scripting and cli use. Will take a look to see if hurl is a good fit.

One annoying thing I've found in testing these tools is that a standard hasn't emerged for using the results of one request as input for another in the syntax of `.http` files. These three tools for instance have three different ways of doing it:

* hurl uses `[Captures]`

* Vscode-restclient does it by referencing request names in a variable declaration (like: `@token = {{loginAPI.response.body.token}}`).

* While httpyac uses `@ref` syntax.

From a quick round of testing it seems like using the syntax for one might break the other tools.

[1]: https://hurl.dev/docs/capturing-response.html

[2]: https://github.com/Huachao/vscode-restclient

[3]: https://httpyac.github.io/guide/metaData.html#ref-and-forcer...


Guilty to have created yet-another-format for HTTP client! To "mitigate" this issue, you can use `hurlfmt` (distributed along `hurl`) that would allow you to export a Hurl file to JSON. You could then go from this JSON to another... It's not magic but it can help if you're going to change from Hurl to another thing.


No worries, it's also interesting to see different peoples approaches to the best syntax for this. Exporters/importers do make life a bit easier I suppose.

I don't know what the mechanism/incentive for getting a standard would be either. Probably most likely would be if there was one clear "winner" that everyone else felt the need mirror.

In any case, appreciate the reply and the tool. Good luck with it.


What's really special is that Visual Studio Code and Visual Studio both have .HTTP files... which are incompatible with each other.

Conway's Law in action, ladies and gentlemen.


Brave seems to remove these parameters from links. Discussion (and links to examples/docs): https://github.com/brave/brave-browser/issues/35094


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: