I started programming at 7, learning BASIC on my mom's classroom computer. Aside from a brief stint as a designer in college and a few dark years caused by Perl, I've been programming ever since. Also my the way I've picked up ample devops and UX knowledge.
I've been working with Rails for 3 years, with a focus on applying UX concepts to API design. I'm looking for a startup that can use my skills and help me develop new ones like native app dev or more thorough functional testing.
I actually regret not switching to Spark sooner, since it has support for more email providers than Mailbox ever had. I do wish it would take some cues from Inbox and add the Action support, though.
I've not used AniDB much, but I once half-finished an API wrapper for Node.js so I guess I'm about as qualified as we're gonna get.
In my experience, AniDB is effectively unmaintained code. They have developers, the developers just don't know the codebase well and they don't mess with old stuff. I've heard this is because it's a behemoth Perl script, but I don't know for sure.
But to cover your main point of "an API checking file hashes/fingerprints against episodes to add to your list", I just wanna say that this is kind of a silly system: you can easily extract that data from a filename.
For example, the desktop app Taiga has an open-source parser which extracts lots of data effectively (https://github.com/erengy/anitomy) and I myself wrote a simple regex-based one for my own client. Both are capable of extracting at least the episode number, subber, and series title.
So why would Hummingbird want to store hundreds of thousands of MD5 checksums when there's better options?
I think the fact that normal TV/Movie sites lack information on Anime led to the schism more than anything. The same things the Anime community has developed could be equally applicable to normal TV, especially in the age of DVRs and streaming: Anime fans were watching things asynchronously long before anyone else
Hummingbird already offers an API through Mashape, which is infinitely more thorough than any competitor's.
Additionally, MAL has lots of minor bugs, and how can you trust a site that hasn't been maintained in 5 years to store your password correctly? 2009 was a scary place.
This is pure speculation, but I wouldn't be surprised if MAL is storing passwords as MD5+salt. They do just email it to you in plaintext when you register.
And recovery is a 6 digit pin, which is totally plenty of entropy.
I'm making light of the fact that we repeated the same thing that happened in history. When people started getting attacked, they formed larger groups to defend themselves. and now we're doing that on the internet with things like CloudFlare.
Everybody is always under attack. The internet is falling to pieces because of botnets, and people forming clans for protection (by which I mean CloudFlare, they're forming CloudFlare)
I hope that this will at least light a fire under the asses of Rails devs everywhere, and get them to adopt HTTPS. Nothing is safe against Firesheep without HTTPS. All of these issues would be solved with HTTPS.
Also, doesn't cryptographically signing (or fully encrypting, in Rails 4) the cookie just add more time to processing than using a database? I always assumed cryptography is slower than IO
In Web 2.0 the turnover rate wasn't too high and most "services" were toys made in the spare time as a mashup of other services. To think it was a bubble, even at the time, is nonsense.
Today I see a different case: shady accounting practices, lots of companies going from zero to public with little market validation, high customer acquisition costs, and high employee turnover rates (at some companies).
Today I think we're in a bubble, but nobody can say for sure until we see it pop. But if you're smart, it doesn't really matter whether we're in a bubble or not.
Just don't be an idiot and get solid funding now so you have money to float above the failures.
To be fair, the tech stack can break a service (though it can't make it) - whether by slowing down iteration or crashing constantly. Putting out fires is not a positive thing.
Remote: Temporarily, not long-term
Willing to relocate: Yes
Technologies: Ruby/Rails, HTML/CSS/SCSS/etc., ES6, Docker, EmberJS (intermediate), ReactJS (intermediate), Elixir (beginner), Swift (beginner)
Resume: http://careers.stackoverflow.com/nuck
Email: [email protected]
---
I started programming at 7, learning BASIC on my mom's classroom computer. Aside from a brief stint as a designer in college and a few dark years caused by Perl, I've been programming ever since. Also my the way I've picked up ample devops and UX knowledge.
I help maintain a few gems right now (Hooloo https://github.com/NuckChorris/hooloo , doorkeeper-grants_assertion https://github.com/doorkeeper-gem/doorkeeper-grants_assertio... , sidekiq-debounce https://github.com/NuckChorris/sidekiq-debounce), with a few more in the process of being extracted from the existing codebase of hummingbird.me (namely, libraries for interfacing with MyAnimeList and AnimeNewsNetwork, as well as JSONAPI::Resources integrations with Chewy and Pundit).
I've been working with Rails for 3 years, with a focus on applying UX concepts to API design. I'm looking for a startup that can use my skills and help me develop new ones like native app dev or more thorough functional testing.