timcraft

@pRdm More a question of priorities than time, currently working on refactoring everything for v5 so things like this are easier to implement. Which API do you want to use...

@pRdm Appreciate that's confusing if you try to copy and paste the code. That should be resolved by making the key and secret optional in #92.

@mheap Any idea on when v4 of the Media API will be available?

@Ch4s3 @henrebotha I'm seeing the same issue with my data and can reproduce with this script: ```ruby require 'classifier-reborn' lsi = ClassifierReborn::LSI.new # Without gsl this raises NoMethodError # /classifier-reborn-2.0.4/lib/classifier-reborn/lsi.rb:143:...

@Ch4s3 Yep, it appears to be loaded ok. I added this at the top of the script (matrix code from gsl-2.1.0.2/examples/linalg/SV.rb which uses SV_decomp): ```ruby puts "Using GSL/#{GSL::VERSION} RubyGSL/#{GSL::RUBY_GSL_VERSION}" a...

Thanks! Hope you find it useful. Both of these features would be good to have, I use those flags with outdated. The main difference is outdated typically reports on multiple...

Version option added in 4b2619c (available in v1.1.0)

> Doesn't Rack already support this if the name ends with `[]`? Yes but that's a Rails invention, not part of the spec. > My advice would be to use...

> Then you don't want the [custom, built-atop-the-underlying-protocol] Rack nested params parsing algorithm; you want raw access to the parameters as supplied. That's something Rack provides at a couple of...

@jeremyevans @tenderlove Looks like `Rack::Multipart.parse_multipart(env, Rack::Multipart::ParamList)` works nicely, as long as that's officially supported I can depend on that once it's available so no need to add a new API....