Just a heads up, some parsing in Readability doesn't work for iOS 11 and Swift 4. If you'd like, I can take a look into these issues and commit some changes to another branch?

In one of my project i was in need to add date support in your Kit. So i worked on it and finally got it working . Now i want to help others who needs date support in your library.Please review my changes. Thank you for your Great work.Its been great working with your kit.It will be great if you add me in contributors Best Regards Jawad Ali

Ji.swift and JiNode.swift are both broken in swift 3. Can't figure out how to fix them with things like "openlass", "fileprifilevate", opeoppened" etc.

Commit: 84cadfc2c659d0ce442e9349174f9b890bf77c70 Author: @lfarah

It isn't enough to copy ReadabilityKit.swift into your project since we have third-party dependency to XML parser Ji.

Try to load articles "http://www.jobsnhire.com/articles/35030/20160214/need-know-cvs-health.htm" "http://www.bbc.com/news/world-asia-china-37081013"
"http://www.bbc.com/culture/story/20160805-when-shocking-images-must-be-covered-up" "http://football.ua/germany/311510-podolski-zavershil-kareru-v-sbornojj.html"

using code let sURL = "http://football.ua/germany/311510-podolski-zavershil-kareru-v-sbornojj.html" let articleUrl = NSURL(string: sURL)

    let parser = Readability(url: articleUrl!)

    let title = parser.title()
    let description = parser.description()
    let keywords = parser.keywords()
    let imageUrl = parser.topImage()
    let videoUrl = parser.topVideo()

For all this articles parser.description() returns only their first paragraph.

" https://economictimes.indiatimes.com/tech/hardware/the-iphone-se-is-in-india-heres-all-we-know/not-a-flagship/slideshow/76280131.cms "

I have implemented this pod in my project. But it seems to not parse the url's that end with ".cms".

In iOS 10, Apple has promised to turn off ATS for developers who want to submit to the App Store. In this scenario, what are the plans to support this?

I would suggest that this code excise its use of dispatch semaphores to make the fundamentally asynchronous NSURLSession behave synchronously. Apple made this asynchronous for a reason.

If a user accidentally called this from the main thread, you'd block the main thread, which results in behaviors ranging from a poor UX to an app possibly getting killed by the watchdog process. Worse, if a user called this from within their own NSURLSession completion handler (e.g. http://stackoverflow.com/q/39253599/1271826), this will deadlock their code.

I'd also suggest that you not initiate the asynchronous method from within the init method. By convention, one should generally configure the object from within init, and then have a separate method to start the process.

first time image loads, user scrolls down and get back to a certain cell he/she saw previously. it get latest images first an the it updates to actual depending upon the content in URL

Some URLS are not parsed? It's either that or the URLSession request takes quite long to parse the data. Is there a way to improve its speed/performance?

Hi,

In the initial testing of this Kit, I found out that it is unable to find parse the any data from the following,

• Twitter

• Youtube

Any ideas, as to what would be causing this issue, would be helpful. Thanks.