Live data from Hacker News

GitHub Audio

github.audio

41–50 of 133 posts

Re: GitHub Audio

#41
post #10

For some reason, this is the fifth posting of this site in the past two days, and the only one to make it to the front page.

It seems that HN is encouraging people to post the same Show HN projects multiple times until they get traction. I have been restraining myself from doing that with my own projects because I care a little about this community, but since moderators and the majority of users don't, I will not restrain myself anymore.

Re: GitHub Audio

#42

Earlier quoted context omitted.

I don't have time for that every time I encounter a new domain.

This functionality could be automated with a browser extension, or even as a built-in feature where there isn't an EV cert.

Then your whois provider gets to see all the domains you are visiting in real-time.

Re: GitHub Audio

#45
post #41
post #10

For some reason, this is the fifth posting of this site in the past two days, and the only one to make it to the front page.

It seems that HN is encouraging people to post the same Show HN projects multiple times until they get traction. I have been restraining myself from doing that with my own projects because I care a little about this community, but since moderators and the majority of users don't, I will not restrain myself anymore.

To be fair, unless it's sockpuppet accounts the author only posted it twice (potentially in error, the second one got flagged). Can't really stop other people from resubmitting your Show HN.

Re: GitHub Audio

#46
post #24

Earlier quoted context omitted.

That would be very very cool, but good luck with trying to version .logicx or .cpr I think popular software vendors should seriously reconsider their file formats in the 21st century, including graphical and audio ones.

Why wouldn't it be possible to version control in the same way we version control other random files? Just treat it as a stream of arbitrary data.

Yes, but more tantalizing would be some kind of wavelet-based semantic versioning. This might allow merging.

Re: GitHub Audio

#47
post #12

This would actually be pretty rad if I could narrow down the events to include only those from Github organizations that I care about.

The code is open source, so you (or any reader) could do that.

Either replace

https://github.com/debugger22/github-audio/blob/e1170daa3a64...

with

https://developer.github.com/v3/activity/events/#list-events...

Or, do some filtering on

https://github.com/debugger22/github-audio/blob/e1170daa3a64...

Re: GitHub Audio

#48
post #8

This is an interesting example where the new expanded set of TLDs can get confusing. My brain interpreted the URL as something semantically like "audio.github.com". Put another way, I thought the site was actually GitHub-made at first glance at its domain. Of course, this was possible in various ways before expanding TLDs, but I think the problem, and thus the ease of phishing, is greater now.

I think the name "GitHub Audio" is confusing and probably a trademark violation. When I read "GitHub Audio", I figured it was a new service by GitHub for musicians to version control their music.

Me too - I was so excited at first..

Re: GitHub Audio

#49
post #24

Earlier quoted context omitted.

That would be very very cool, but good luck with trying to version .logicx or .cpr I think popular software vendors should seriously reconsider their file formats in the 21st century, including graphical and audio ones.

Why wouldn't it be possible to version control in the same way we version control other random files? Just treat it as a stream of arbitrary data.

You'd miss out on all the goodies of version control like seeing what has changed. Ideally, version control for musicians would have the ability to show "change panning of guitar a to 0.3 and volume to 0.1" similarly to a code diff. Otherwise all you've got is just a bunch of backups, possibly with semi-informative commit messages if you really put a lot of effort into it.

Re: GitHub Audio

#50

Earlier quoted context omitted.

This functionality could be automated with a browser extension, or even as a built-in feature where there isn't an EV cert.

Then your whois provider gets to see all the domains you are visiting in real-time.

Good point. Even though your ISP/DNS provider can see this too (including HTTPS connections) it's prudent to limit data leakage as much as possible. Perhaps the lookup could require a single click (only needed when you are unsure of the owner).
Post reply on HN