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

OneDrive Proxy #20

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from
Open

OneDrive Proxy #20

wants to merge 5 commits into from

Conversation

BrutuZ
Copy link
Contributor

@BrutuZ BrutuZ commented May 8, 2023

Prototype parser proxy for OneDrive folders via shared links.

Included disclaimer to address PII concerns on #19
Tested Series and Chapter pages on both Reader and API endpoints

Closes #19

@BrutuZ BrutuZ mentioned this pull request Jun 1, 2023
@funkyhippo
Copy link
Collaborator

Do you have an example share for me to test with? I don't use OneDrive.

<p>Currently it supports imgur, OneDrive, nhentai and custom appropriately-formatted JSON hosted on GitHub Gists. This is an advanced feature and will be explained in detail below.</p>

<h2>Disclaimer regarding OneDrive shares</h2>
<p>OneDrive links provide user information (look for the "More Details" pane on the "Info" tab).<br>Keep that in mind if you intend to share Cubari links from that source.<br>We can't opt-out of receiving that information, so the best we can do is pinky-swear we don't even read it.</p>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have a little fud about burying this in our "about" page wall of text when we're not the only ones that can read this information. The share URL should have a "source" button that reveals the original resource:

image

That original URL should in some way reveal the original source, which would also reveal the drive's owner.

I've seen gist owners not realizing that their GitHub accounts are publicly visible so I'm still a bit wary about this.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried hijacking the function to add a new pop-up element exclusively for this disclaimer, but my frontend-fu wasn't strong enough. IIRC I managed to make it show up but broke the close button 😅.

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

Successfully merging this pull request may close these issues.

2 participants