Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved support for response-type websites #22

Open
Jdogzz opened this issue Jun 29, 2020 · 0 comments
Open

Improved support for response-type websites #22

Jdogzz opened this issue Jun 29, 2020 · 0 comments

Comments

@Jdogzz
Copy link

Jdogzz commented Jun 29, 2020

I've noticed that while webpages from websites like stackexchange, reddit, etc, the obtained copy doesn't have all the info from responses (sometimes sub-responses aren't loaded, and sometimes additional pages of responses are made). It would perhaps be a nice enhancement to org-board to use the website's API, if available, for building a page-specific repository of the threads that develop. The flow could go something like this:

  • User sets an option in the config file to do extra processing like this for a given domain (probably per-site functionality will have to be made)
  • org-board-new is run on a URL
  • The raw website is retrieved with wget as usual
  • Something like an mbox file is made and the website's API is accessed to populate the file with the threaded conversation intact
  • Later, when the user runs org-board-open, the user can have the option of opening the raw website as usual or using a mail reader to open the mbox file

As a potential further option, though this may conflict with the way org-board treats website updates, the user can request the mbox file be updated with new or altered responses on the webpage since the original retrieval.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant