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

[BUG] StorySeedling - Jumbled/empty text on passages #8

Open
noaione opened this issue Oct 23, 2024 · 2 comments
Open

[BUG] StorySeedling - Jumbled/empty text on passages #8

noaione opened this issue Oct 23, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@noaione
Copy link
Owner

noaione commented Oct 23, 2024

For tracking purpose, they change some stuff around so text might become jumbled messes or will return error.

Please report any additional issues here.

Latest extension version: 2.1.7


Some discoveries:

  • Text are ROT13 Text are shifted codepoint
    • Rendered using custom font based on Inter (already violates SIL OFL they've renamed it to Vagre so it doesn't violate the license anymore)
  • Contains "Copyrighted material" text (lol, lmao even)
  • Contains padding text which is hidden when rendered in HTML
  • Request need to send captcha if needed and nonce
    • They introduce CF turnstile/captcha when reading (this is on top of standard CF security check)
    • This one is a bit annoying, I wish there is a webview button on chapter :(
@noaione noaione added the bug Something isn't working label Oct 23, 2024
@noaione noaione changed the title [BUG] StorySeedling - Jumbled text on passages [BUG] StorySeedling - Jumbled/empty text on passages Oct 23, 2024
@noaione
Copy link
Owner Author

noaione commented Oct 24, 2024

New issue:

  • Some line got some of their spaces removed after punctuation, I'm guessing this is because the bad way I'm handling the ROT13

@noaione
Copy link
Owner Author

noaione commented Oct 27, 2024

New issue (also fixed):

  • They change from ROT13 to adding 12027 for lowercase and 12033 for uppercase. A bit harder to solve in lua since they don't have native utf8 support until Lua5.4 I think?
  • Some text are not corrected, this is because my text handling which should be fixed by 2.1.7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant