Discourse links are now auto-formatting with | Natively at the end, ex: お隣の天使様にいつの間にか駄目人間にされていた件 S1 | L25 | Natively - which would normally end at L25
1 Like
Ok! @joreneereads @HopeWaterfall I think that language switching should be finished.
@Megumin @暁のルナ those discourse issues should be fixed now too, see:
Now onto all the other things 
7 Likes
Unfortunately, it’s still doing it:
お隣の天使様にいつの間にか駄目人間にされていた件 S1 | L25 | Natively is appearing as お隣の天使様にいつの間にか駄目人間にされていた件 S1 | L25 | Natively
2 Likes
Right, sorry should’ve clarified. For things linked in the last day or so, it will be stored by discourse (it doesn’t refetch that data). Nothing I can easily do about that without research.
All new things though should work 
2 Likes
Oh I see… it looks like it’s fixed then, ex:
However inline links like https://learnnatively.com/season/48e3a1fbb4/ or https://learnnatively.com/season/1a05d3831b/ are mostly not formatting. Fate/kaleid liner プリズマ☆イリヤ ドライ! ! 1 | L26 does for w/e reason though.
Anyway, feel free to prioritize other stuff, if you need to… manually formatting forum links for a bit isn’t the end of the world
2 Likes
Is there functionality to maybe… do a beta release of stuff like this for testers instead of something more widespread like this? Or is the backend too warped or that?
2 Likes
@nativelearner - fixed that datamanager
@暁のルナ @Biblio those tv episode issues are now fixed
Unfortunately it’s not something unfamiliar to you all … 
I will say, I do have hope this overhaul in the end will address some of those issues, as I think it’s mostly a loading speed problem that this will hopefully address. We’ll see.
Somewhat long response
It’s not really an issue of the ‘backend being warped’. It’s more just that it is complicated to do well and takes time to set up the infrastructure. It also only works well for certain types of features that don’t impact the general site functionality at large … and / or can be bucketed in some sort of way. You’re right though - this overhaul could’ve been bucketed that way.
I will admit that I haven’t had a lot of experience rolling out beta modes, so if someone does have that experience, i’m happy to hear your thoughts.
Generally though, there’s a tradeoff between moving fast vs having a bug free, exceptional experience. While I don’t view Natively in the alpha / beta phase anymore where users should expect bugs, I don’t think we’re at the point where users should be very surprised if they encounter a bug either… this is still a one man development show and i’m trying to move very fast. Natively still hasn’t figured out it’s market fit yet.
All that being said, I know this has been a buggier-than-normal release. If you all think I’m pushing too far on the ‘move fast’ end of that tradeoff, that’s a valid discussion to have. 
7 Likes
I think you’re doing great - especially considering this thread has been up for all of a day, and you’ve addressed many (most?) of the issues in it. Making infrastructure changes always has hickups - it’s just the nature of things…
But also in general, I think you strike a really impressive balance between new features (big and small), incorporating feedback, dealing with bugs, user requests, etc.
11 Likes
Sync button on book series page isn’t working: ケイヤクシマイ | L25 … seems to be either a CORS issue or something undefined
Uncaught TypeError: window.gs is undefined- has a wholeu onClick ae ao, etc list when you expand itCross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://o364332.ingest.us.sentry.io/api/4720961/envelope/?sentry_key=00782e3def4140dc84e6cd7cad6851ed&sentry_version=7&sentry_client=sentry.javascript.nextjs%2F7.104.0. (Reason: CORS request did not succeed). Status code: (null).
2 Likes
Ok! A host of new fixes:
@nativelearner @enbyboiwonder @iwannareadman
All your issues with updating book status / information / reviews and not seeing it reflected on the book page should now be fixed.
@nikoru fixed that checking gradings issue
@暁のルナ the book series sync is fixed. However, the cross origin issue (which is a bug with my error alerting service) still needs to be resolved, but that’s only a bug when bugs occur! 
The only outstanding bugs I know of:
- The anchor tag issue @nativelearner & others highlighted
- sometimes the dark mode & dark mode toggle icon gets out of sync
In other news, I also removed the loading spinner entirely on the new app pages, as it was causing flashing issues I think. Otherwise, the initial load seems to be working well as far as I can tell.
Aww, thanks! Really appreciate the kind words 
I must admit I feel like I’ve been shirking some of the more popular wants (i.e. rereads & crosslinking media items), so good to hear haha. We will get to those items in the next few months though… 
8 Likes
Blurb language is still defaulting to EN
3 Likes
Amazing - and good luck (I loathe solving CORS issues personally)
Maybe, but you’re also adding functionality for video games & web books - which are also pretty popular wants (I am looking forward to both of those when the time comes tho!)
Sorry to add, but…
Spoiler tags for reviews are still broken… the initial <Spoiler> tag is disappearing for some reason. This affects both previews and the actual reviews… it only seems to be on the book page, and not the individual review link. So:
https://learnnatively.com/book/1b9a2e8116/ (犬夜叉 24)- spoilers are not blurred
暁のルナ's review of 犬夜叉 24 | Natively - spoilers are blurred
Also, while not the biggest deal, when you load a book page, some of the state is not displayed properly for a bit (in an FOUC sorta way). I don’t think it was doing that before.
What it looks like initially (for about 1-2 seconds):
What it should look like (difference is in status & rating, on left):
4 Likes
The spoiler tag might be browser-specific. I’m on Safari on my phone and, on the review I left yesterday on 金色の羽でとべ at least, they’re working fine.
The strangest thing is, when I went to check, I scrolled down to the ratings and reviews while the page still wasn’t fully loaded, and my review was there. As soon as it finished, the review disappeared, though the other reader’s review-less rating was still there. I refreshed, and that time, it was there it was there while the page hadn’t full loaded again, but it only disappeared for a split second upon completion before reappearing again. That gave me a scare.
4 Likes
Yeah I just tried it with Firefox (has the spoiler tag issue) and Chrome (doesn’t have the issue). Good catch
2 Likes
Noted 
You’re right. Basically I’ve broken things up into a few requests pretty aggressively and I don’t show a spinner while we wait for all the info. The blank header is my default while we wait for the request. As for the wish list buttton, yeah, need a better default while we wait.
More tech details on my requests
Right now, when you hit a book page there are 4 requests:
- fetch initial app data (no-user info)
- fetch initial app user data
- fetch book page specific data (no-user info)
- fetch book page specific user data
The idea with breaking it up like this is so that the server can cache the non-user specific data and render that immediately for you and search engines.
I could show a spinner until I have all the info, but that’s a little sad… So I’m going to try and have reasonable defaults for the user specific regions, but it’s still a work in progress.
The header you noticed blinking requires the app user data. I don’t show the header until I have received that response. The button also requires the app user data… but I haven’t put in a good default yet, that’s a good call out.
Other things like the your full user review / stats require the book page user data, and I simply don’t show them until that comes in.
When I get more sophisticated at this, I will have ‘skeletons’ show… which are blank placeholders similar to the content about to be revealed, but obviously show they’re loading. Won’t do those until we’re fully migrated though.
Sorry about that! Yeah, showing your personal user review was broken until today… but showing other peoples reviews was not. So, you got that scary bug where it looks like it disappeared after the code figured out that it was your review and not someone elses
Yeah, this was bucketed in with the ‘non infrastructure bugs’ as it’s a little more complicated. Good to know that it’s browser specific and makes sense Firefox bugs out. Firefox seems to not like having raw html in that markdown widget I have… presumably for security concerns.
5 Likes
Unfortunately I still have the language fixing bug. It’s even happening on incognito mode as well.
really?? What url?
Apologies if it’s been mentioned before, Content tags do not seem to show up, even though they are there (when I try to add them again, it says they’re already there).
I’m on mobile with chrome.
3 Likes
Oof, well I guess I had not solved the issue at all. However, I think i’ve solved it now…
That book is now not toggling back to Japanese and I again, think I have it fixed this time!
… I completely missed mobile. And it seems the book series pages weren’t working either. Fixed up all those tags, good catch
@nativelearner and others I fixed up that issue with the broken tag in blurbs
5 Likes
