Are there plans to update this package to match readability.js v0.0.6?

[TijnvandenEijnde]

Thank you for the package!

Version 0.0.6 of readability.js has been released for some time now are there plans to update this package to match it?

[mislav]

Hi, I don't like to be that person who says "use this fork" as an answer to a question, but I've submitted a few PRs to this repository and received no acknowledgment from the maintainer in the last few months.

Until they have time to work on this project again, you may use my fork that brings Readability.js v0.6 compatibility plus a plethora of performance improvements https://codeberg.org/readeck/go-readability/src/branch/main/FORK.md

This fork is used in the read-it-later app Readeck, so it's been tested in a variety of real-world scenarios.

[fmartingr]

Hey folks, I have been focused on Shiori lately more than on the other repos on this org since I came to be the main guy here. For this one I only did some housekeeping from time to time to keep dependencies updated when needed and some required dependabot updates, but making upgrades wasn't on mi mind.

Would be happy if anyone would step up and maintain the library, that's the approach I took with Shiori.

We can discuss the best option to move forward in this issue so we can bring the best experience possible to everyone.

[mislav]

@fmartingr Hi, thanks for explaining! If it would help, I could take on maintaining go-readability by porting what I've done in my own fork to this repository. The changes I've made are listed in the document I've linked to, and on top of that I've recently published a v2 where I changed a few APIs to make the library perform faster and use even less memory.

Here are the results of my fork's performance on the article extraction benchmark, showing a small improvement over the version in this repository.

[TijnvandenEijnde]

Thanks for the response!

@mislav That would be awesome!

My situation is a little different. I am using the Flutter readability package, which wraps the Go library. Unfortunately, I am not able to help with maintaining go-readability directly because I do not program in Go.

I was simply curious whether the package is still being maintained so that the Flutter wrapper can be updated in the future.

[fmartingr]

@fmartingr Hi, thanks for explaining! If it would help, I could take on maintaining go-readability by porting what I've done in my own fork to this repository. The changes I've made are listed in the document I've linked to, and on top of that I've recently published a v2 where I changed a few APIs to make the library perform faster and use even less memory.

Here are the results of my fork's performance on the article extraction benchmark, showing a small improvement over the version in this repository.

Happy to either give you ownership of this repository or just archive it and point it to your fork, whatever you feel more confortable with. I'm good with both, as long as the library maintenance continues :)

[martinrotter]

I plan to bundle Go variant of readability algo into RSS Guard, very curious about outcome of this. Great job guys.

martinrotter/rssguard#1783

[mislav]

Happy to either give you ownership of this repository or just archive it and point it to your fork, whatever you feel more confortable with. I'm good with both, as long as the library maintenance continues :)

@fmartingr Thank you! In that case, I would prefer that this repository gets archived in favor of my fork over on Codeberg. My reasoning is:

• The default git branch of codeberg.org/readeck/go-readability is API-compatible with this repository
• My work on codeberg.org/readeck/go-readability is primarily motivated by its inclusion in Readeck
• Readeck is under active and heavy development, so it makes sense to keep go-readability on the same git forge as Readeck itself
• I have plenty more ideas for codeberg.org/readeck/go-readability and I intend to keep working on it and keeping it up to date with Mozilla Readability
• I will adjust the README for codeberg.org/readeck/go-readability to make sure that it's clear that it was a fork from a GitHub project and to make a note of the original author(s)

I would have one ask of you to help users of github.com/go-shiori/go-readability with the transition to the new repository: you could update your implementation to add a deprecation notice before archiving this repo https://go.dev/ref/mod#go-mod-file-module-deprecation. In theory, that deprecation notice should show up for people who will be including the now-archived module in their projects so that they should rename their imports.

[fmartingr]

Hey @mislav , that's ok by me. Unsure if @RadhiFadlillah wants to voice something here, since he's the original owner. I just want development to move forward, though to be honest it's kinda sad seeing the libraries move along to different places instead of we all joining forces, but that's just the nature of open source.

That said, I'm currently travelling and don't have access to my personal laptop, so would you mind making a PR for the deprecation notice in go.mod and the README? I can approve it from the phone. We can wait some days for Radhi and proceed if we don't get any feedback.

[RadhiFadlillah]

Hi everyone, sorry for the late response.

This year I've been busy with job promotion and a new baby, so I haven't got much time to work on any of my open source projects. With that said, I'm glad to see there is an interest to maintain this library, so that's an OK from me as well.

[mislav]

@RadhiFadlillah Thank you for your work on this project so far, and congratulations on the job promotion and your baby 🎉