But then I'm not sure still...maybe that is okay if consumers massively benefit from the reverse engineering, and thus overall utility is increased...! What do you think?
1,028 karma · joined May 2, 2011
http://timrogers.co.uk timrogers at github dot com
But then I'm not sure still...maybe that is okay if consumers massively benefit from the reverse engineering, and thus overall utility is increased...! What do you think?
Potentially using Twilio (http://www.twilio.com) you might be able to have an application which receives the two-factor request itself and handles it. It'd make the process async though, which wouldn't be ideal.
If you wanna chat at all about any of this stuff, drop me a line at me@timrogers.co.uk.
As I've said in other comments, I'd love RG to have a public API, but I can see why they don't.
It'd be cool to compare notes on parsing Rap Genius. Drop me an email if you have a moment, me@timrogers.co.uk.
You might find my response below (https://news.ycombinator.com/item?id=6229617) interesting, on that front. My guess is that for Rap Genius, the only API that will make real sense is one offered on a commercial basis.
- Embedding in personal blogs - this is probably best achieved by a simple embed code (which I'm planning to use my gem to build), rather than a full API
- Commercial use - for instance, Spotify (or competitor) might like to display rich lyrics in-app.
The situations which would demand a full-on API, I suspect, would be commercial use. Thus, I'd imagine that any API they build will be private and commercial, providing a (first?) revenue stream.
I tend to think that this kind of thing is okay for personal use, whereas it wouldn't be en masse - for instance, if you were using it to power and advantage a competing music site. Others' opinions may differ.
For instance, I've previously built scrapers for banking services (American Express [https://github.com/timrogers/amex] and Lloyds TSB [https://github.com/timrogers/lloydstsb]) and the UK's university application system, UCAS (https://github.com/timrogers/ucas) and none of these organisations seem to have had any problem with it, but the library has been really gratefully received by users.
If it's to thwart child pornography, that won't work because if you wanted to view it, you'd just toddle off to your ISP and opt out of the filters.
If it's to stop children looking at pornography in general, that will fail children/young people are smarter than people imagine at circumventing these things.
This sort of thing gets proposed because it makes people think the government is doing something to social problems, even if it is technically problematic and won't really achieve the stated aims. I'm actually all for discouraging the use of pornography because it is something of a scourge on society, but this is not the way to do it. Education is.
Of course, there's the possibility that its audience won't have the means to pay up, or that people will just go elsewhere.
A prompt from the browser would be the best option, but alternatively, I'd want the site to offer me an option as to how the external file should be handled. If the browser doesn't implement it, it says that the "Right click to save" nonsense could make sense.
[1] http://macwright.org/2013/02/14/the-law-is-public-domain.htm...
For our support documentation, we're using the Desk.com knowledge base. Although not ideal, it works pretty well for us and is at the very least easy to update.
We took steps like this with our blog (https://gocardless.com/blog) which we've now built using Jekyll. This is awesome because:
a) Anyone can write articles if they can write Markdown
b) Full text previews in our GitHub pull requests...with images (perfect for reviewing!)
We want to transfer these great advantages to our help documents. Jekyll really is a great tool for any (relatively) static site, not just for blogs.
That's what we recommend. It's super easy to sign up and integrate so it's absolutely worth signing up and just giving it a go. That way you can see whether it works for you and your customers.
Indeed. We'd love to open-source it, and I plan to get it to that stage in the long term. The challenge is updating it as so that it's useful for more people and not tied into our internal services and metrics platforms.
Watch this space.
At the moment, we still use Desk.com for our emails. Here, we were looking for a simple system for tagging our phone calls, but one which could be tightly integrated with our internal services and metrics. We found that the best way to do this was to build our on.
Twilio has been great, offering a huge amount of flexibility to build this how we want to.
We'll look into it for sure, and we'd definitely consider down the line releasing more general data about what our merchants' customers call us about. We think it's really important to help those using us to optimise their integrations.