search

OurchiveIO / ourchive

An easily installable fiction, audio, and image archive package.
GNU General Public License v3.0
8 stars 6 forks source link

AO3 Work Import #49

Closed ladyofthelog closed 8 months ago

ladyofthelog commented 1 year ago

Currently, there is no import feature available. This will be a barrier for some users to migrating to ourchive instances.

AO3 downloader is one option. My fork of ao3 scraper might also have some helpful code to glean, including for comment scraping.

Locked works may not be able to be imported by the import tool. Workaround: ask users to mass or individually unlock and re-lock works if needed.

Candleja commented 1 year ago

wait, locked works are only archive-locked, not private the way bookmarks or friendslocked livejournal entries are. any registered account can see them.

new workaround proposal: a config option that lets the instance owner embed credentials (cookie or password, whatever) for an ao3 account

the import feature should just log in as the configured ao3 account owned by the ourchive owner and get access like that

(and by "ao3 account owned by the ourchive owner" i mean "they would just make a new empty account to be exclusively used by the ourchive instance, not reuse their existing human-owned one")

Candleja commented 1 year ago

Also, this is silly but the way video game guilds work online for one-time identity verification of a user between Website A and Website B is:

"Put this token into your profile on Website A to prove that you're person A"

So that's something that could be included as a "make it slightly harder to bulk import someone else's works into your account" guardrail, if desired, but I don't really think it's important for MVP (or at all?) since if someone actually wanted to impersonate or plagiarize someone else they could just do it by hand, and either way the solution would end up being "a human moderator looks at you and says 'lol you cant do that get out'"

I don't think it'd actually matter from a practical standpoint, but I guess it could make users feel more secure if they have to "do something" to allow an import, in the same way that putting a picture of the visa logo on a checkout page makes users feel more secure.

ladyofthelog commented 1 year ago

I like the "use configured account" idea, maybe with an option to omit this step with the flag that this will only import public works.