GitHub Audio
21–30 of 133 posts
Re: GitHub Audio
#22It’s crazy that there’s 3k+ people currently listening to events from github’s system. So much #nerd
Re: GitHub Audio
#23Re: GitHub Audio
#24This 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.
I think popular software vendors should seriously reconsider their file formats in the 21st century, including graphical and audio ones.
Re: GitHub Audio
#25This is what I don't understand about Android. I have sounds set to "Alarms only" yet this webpage still plays it's tones.
You have to check all three of these to be sure. I have mine set to only "Alarms" and occasionnally allow "Media" when listening to music or podcasts, but after listening you have to reset "Media" to zero. (I don't have any kind of notifications alerts, sound or vibration)
Re: GitHub Audio
#26This is what I don't understand about Android. I have sounds set to "Alarms only" yet this webpage still plays it's tones.
Re: GitHub Audio
#27From there you can get the URLs for the audio files used. Uses Howler for audio, web sockets to talk to the server, SVG to render the animations.
The above is all easy enough to get from the source, but it might save someone else some time.
Re: GitHub Audio
#28Re: GitHub Audio
#29This 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.