Skip to content

Developers: Requested Rippers up-for-grabs (meta-issue) #43

@metaprime

Description

@metaprime

Issue by metaprime
Tuesday Apr 25, 2017 at 07:45 GMT
Originally opened as 4pr0n/ripme#510


Note: assume all links are NSFW

If you would like to develop a ripper which has been requested, please open an issue (to function as a work item) indicating that you've claimed a ripper and you're working on an implementation. Please link back to this issue (and 4pr0n#502 as an FYI) so that GitHub makes a link to the issue (work item) appear in this thread and 4pr0n#502.

I'm locking this conversation to ensure requests and general comments stay on 4pr0n#502. (It looks like link-backs won't appear on a locked issue, so I won't be able to lock this issue.)

To keep this issue focused, I will delete requests and non-dev-related comments (please use 4pr0n#502 for these).

Below is a list of rippers and functionality requested via 4pr0n#502 and 4pr0n#8 (this list is a work in progress -- I'm posting a thumbs-up reaction on any requests I have added to this list). Please assume all links are NSFW.

High priority (existing rippers: broken or missing functionality)

Everything else:

Pending sites + examples (from 4pr0n#8)

Enhancement requests (list from 4pr0n#8):

Acknowledged but defunct requests:

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions