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

Support templatizing the Inbox and Assets directories #133

Closed
2 tasks done
dekimsey opened this issue Dec 9, 2023 · 0 comments
Closed
2 tasks done

Support templatizing the Inbox and Assets directories #133

dekimsey opened this issue Dec 9, 2023 · 0 comments
Labels
type: enhancement New feature or request

Comments

@dekimsey
Copy link

dekimsey commented Dec 9, 2023

⚠️ Please check that this feature request hasn't been suggested before.

  • I searched previous Ideas in Discussions didn't find any similar feature requests.
  • I searched previous Issues didn't find any similar feature requests.

🔖 Feature description

I'd like to able to leverage ReadItLater for long-term retention of interesting articles. To do this, I'd like to have a bit more control regarding the paths used to define the Inbox Dir and Assets Dir settings.

✔️ Solution

The generated content (in particular, assets) would be written in a sub-path based on the resource I've downloaded.

This would probably be best as a limited set of filters to reduce escaping issues such as:

  • %date%
  • %method% (new: "mastodon", "lemmy", etc)
  • %title%

❓ Alternatives

I could mark items for ReadItLater and then manually move them out to another directory every-time I download new items.

📝 Additional Context

My real intention is to be able to use ReaditLater as an archiver. Many of my notes include references to third party URLs where I learned how to do X or Y. However, a few of them have died or are no longer available at that URL. I think ReadItLater is potentially well suited to be a very cool way (short of Archive.org) to take snapshots of references I find on the Internet.

To accomplish this I think there are two features missing:

  • Long-term storage of assets all being in the same directory (this issue)
  • Defining file properties to back-reference the source content

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants