The urinal's are missing the class Victorian joke: the bee emoji ("apis", natch).

This is so true...

Programming without the internet was tough. I remember my early years of programming in ASM and C/C++. The only internet access was via BBSes and Trumpet Winsock. Your only source of real help was from Usenet groups and questionable help files. There was no such thing as Intelli-sense (as we know it now) or auto-complete; you pretty much had to memorize the parameters for all Win32 API calls and the STL for C++ was brutal to use. Programming nowadays is relatively easy in comparison - pretty much anyone can code thanks to the internet and fantastic online resources. Heck, my 7 yr old daughter is learning to write code using a Scratch-derived visual programming language and Cosmo (look it up, it's awesome). I started "coding" at 8 by typing out programs from an adventure game programming book, in BASIC (think old Infocom games, like Wishbringer/Zork, etc).

The challenge in today's programming environment is the rapid pace of change. It's so f'n hard to keep up with every new toolkit, platform, library, programming language enhancements, etc.

I got a 4mb Voodoo 1 passthrough card when they first came out and to this day still think it was the most "holy shit!" game changer I have ever seen. 800x600 using Glide was unreal. I also had a GF 256 and while it certainly smoked the Voodoos in performance, the difference between software rendering and the Glide API was mindblowing.

I hate Digg's video api; just wanted to vent that

Not that I have the source code, but I do see from the include directives he's using Twilio. It's an API and service that allows you to automate phone calls and SMS messages. I haven't actually used it, but researched it for another project; still it seems pretty interesting all the things it's capable of.

It wouldn't be hard to throw together a simple flooder, but also not free.

https://www.twilio.com/voice

*imnotdeadyet outdated youtube flash API used. Needs a new embedded code.

edit: After some clicky on the overlay text I got it to disappear and work. Any reason why were using this instead of the current embed? it is still on youtube right?

Go fuck yourself API *promote

Vimeo must have changed their API... Actually, yeah, I recall seeing something about them locking it down and making it really hard compared to the way it used to be.

I'll have to look into it whenever I have some time, but if anyone else is able to do the research, it'll help.

No worries TBH I looked at the google reference doco last night and found it... unclear. This morning I treated it like a work problem and googled! Third result is http://stackoverflow.com/questions/15596753/youtube-api-v3-how-to-get-video-durations and bingo.

I remember when you used to actually have to know stuff...

Thanks for the pp's

The actual API call isn't that bad, it's just https://www.googleapis.com/youtube/v3/videos?part=contentDetails&id=$UbyKywWvlCE&key=(your API key)

I couldn't test it though, I haven't registered for API access... is that the bullshit you were referring to? I just get keyInvalid

Ugh. Wish I somehow was privy to information like that... Thanks for finding that, eric.

Fuck their API bullshit. I'm just scraping the YT video page for the duration now.

Fixed.

YouTube is definitely returning a duration of 236 seconds for all videos. Example: https://gdata.youtube.com/feeds/api/videos/UbyKywWvlCE?v=2 (search for yt:duration).

I am

@lucky760 I think @eric3579 has got it in one.

The video they return when you use a Data API v2 video call happens to be length 3:56 too.

That suggests that without action, every yt vid will get length 3:56 until late May when they will get no length.

@lucky760 Im no computer guy but this update seems to have come out about the time the time stamp problem started, and it mentions API.
http://youtube-eng.blogspot.com/

Nothing's changed on our end of things, so perhaps YouTube's API has a bug. I'll look into it.

Thanks!