(New) App Feedback
-
Now that I'm back home, I can confirm that the app fails to load stuff when using data. It gives this message on the release tab: "Failed loading releases: No response received from server - SocketExpection: Read failed (OS Error: Connection reset by peer, errno = 104), address = labs.j-novel.club,port = 52286"
And a similar message on the series tab. The account tab just says "Failed loading user data from server" -
@masterofbeings
OK.
Now there should be enough info for the JNC Support guys to have a clue.Well, verifying terminology just to be sure, since I'm an old fart and late adapter in regard to mobile computing of the non-PC/Laptop type...
When you say 'data', this is your phone's cell connection, yes?
I suppose in this day and age info in regard to what cell transmission type (4G, 5G, etc.) would become relevant to the situation if it is a 'timing out' problem.
Just had a thought; this is the feedback topic.
I have a vague recollection of there being a Support topic concerning the app as well, and that's probably the one the support chaps monitor...Gathering together all the info from our various posts here and summarizing that in the proper support topic might be an idea.
Or at least checking to see if my memory isn't faulty this time around. -
@masterofbeings This sounds to me like your cellphone internet provider isn't letting you access
labs.j-novel.club:52286for some reason. The only workaround I can think of, short of changing providers or shouting at them, would be for JNC to update the app to use port 80/443 for this. I'm sure they have their reasons for using a different port, however. I'm just one more person speculating here, so I don't know. -
@nosgoroth said in (New) App Feedback:
@masterofbeings This sounds to me like your cellphone internet provider isn't letting you access
labs.j-novel.club:52286for some reason. The only workaround I can think of, short of changing providers or shouting at them, would be for JNC to update the app to use port 80/443 for this. I'm sure they have their reasons for using a different port, however. I'm just one more person speculating here, so I don't know.I hadn't considered that WiFi would link through their 'traditional' ISP while Data would link through their Cell Provider, adding the possibility that the Cell Provider might be 'doing something weird' distinct from anything related to the individual's device and J-Novel Club. My realizing there would be a different rate of data transmission has nothing to do with this.
That's an aspect of things I've no background knowledge concerning, no real grasp of the possibilities for said third party 'futzing things up'.
-
@weasalopes It wouldn't be the first time I see mobile ISPs running connections through weird proxies and messing up perfectly valid requests. At work we had to deal with an issue that only happened to users with a particular phone company, and all we could do was throw our hands up and wait for them to fix it.
The main reason I think the mobile ISP might be the issue is that, if I'm interpreting that error message correctly, this request is using a weird port. Now, that doesn't mean there's anything bad about it, but it's something that can cause problems sometimes, like when a public university wifi blocks nonstandard ports for extra security (standard ports being 80 for HTTP, 443 for HTTPS, 20-22 for FTP...), so if the error only happens in a particular network...
Just a load of speculation, though.
-
Small UX thing, the part drop down list includes parts i don't have access to. This is the drop down when clicking the header while reading a part. If I select one of them, I get an access denied error (as I would expect).
Side note, any thoughts on open sourcing the app? The app itself isn't j novel clubs key differentiator (that's the novels and prepub access), and is expect the main app users are the kinds of rabid fans that might contribute.
-
@nosgoroth That is sort of incorrect, the port you're seeing in that message is the outgoing port from the device. The requests being made are using HTTP/2 over TLS on port 443 (HTTPS).
-
@cpitman I think it would be more confusing not to include all parts in the TOC. I do definitely plan on replacing the vague "access denied" message though, to make it more clear that you need to be a subscriber to read them once certain other prerequisites are ready.
Unfortunately the app cannot be open-sourced because as you may already know, original publishers require DRM for manga. The amount of work needed to detach the DRM from the app would be substantial due to the way it is implemented, and I don't have to time do that. Is there a specific reason why you want the app to be open-source?
-
Could you possibly add a link for the app on the homepage? There's actually 2 J-novel club apps in the play store. I don't want to get the wrong one. Sadly my second-hand iPad only has up to iOS 9 making it incompatible with the new update... Android doesn't seem to open the manga series for me.
-
On an iPad (iOS 15, iPad Air 3) the official app does not work that well https://imgur.com/a/dtd9zpL. It hard to read even after I tried to adjust the borders.
In landscape on the iPad it would much nicer & readable to have two columns.
The web app that someone made https://forums.j-novel.club/topic/3353/yet-another-pwa-jnc-client/75 supports an iPad much better, see the below pictures
-
Can we get the beta back? I was finally forced to switch the full release version and it’s a downgrade. The 0.8 version was better than this. I’m not asked to resume where I left off. Whenever I bring up the menu in vertical reading the text moves. There’s an issue in paginated view where if the page ends at the end of a paragraph the following paragraph isn’t indented on the next page.
-
Can we get the Alegreya font back on the new app, that has become a really comfortable fort to read in and it’s nostalgic. Pardon if this has been brought up already.
-
@doomerx said in (New) App Feedback:
Can we get the beta back?
Wouldn't fixing the regressions be sufficient? :-) I'd rather not lose the stuff they did fix between 0.8 and 1.0.
As far as the Ask to resume bit goes, I know that was asking when it shouldn't have been pretty frequently in 0.8 (like when everything was completed and there was nothing to resume, it asked anyway, and went somewhere random), and no longer asks me in those errant situations in 1.0. Maybe whatever they did to fix it overdid it?
-
There's weird behavior on the new app when it loses connection;
Even when you reconnect to the internet it becomes unable to fetch any info and you have to close and reopen the app.
Edit: Also, I don't know if there's a way to star series that I missed, but as it is it's kind of irksome to bounce between the current releases and the old releases, I have to go search through the library each time.
-
Would it be possible to add an option to lock the rotation of the app to vertical/horizontal. Don't want to have to change phone settings every time.
-
Sometimes certain parts are marked unread/white again even though I've read them. Even when I go mark it read/green again, it won't stay that way when I open the app later and reverts back to white/unread.
-
Please can we get the old site reader back. I don't want to use the new site's version because the reader is to be frank dog**** and I want to keep using the old one.
-
Bonjour, si a défaut de pouvoir remettre l'ancien lecteur, serait il possible d'intégrer un traducteur dans l'application ?
Sinon je ne pourrais plus garder mon abonnement, il ne servira à rien -
Can some of you list off the things you don't like about the new reader instead of just saying it's crap? It's going to be really hard for them to fix the new reader to be usable for you if they don't know why you think it's crap. Tell them specifically what they could fix to make it not crap for you.
-
I know for me personally it's a pain that the single page mode ends up being one page that the same width at the two column mode. That leaves the reader too wide to read, so ideally some way to make the reader shrink down to a similar width as the previous reader would be ideal.
I dislike the way the overlay keeps popping in and out whenever I move my mouse over the reader as I read, a way to force it on in place and not overlaid on the reader's reading space would be nice, but I consider that to be a quality of life fix rather than minimum use functionality.
For a number of our foreign and some of our other English readers users the primary concern appears that the new reader doesn't work with language translation software or text to speech software, it sounds like the old reader had the ability for these software applications to do their thing. Since the alternate PWC reader appears to support both of these, it seems like this is more to do with how the reader itself works to prevent text copying.
However since this is a topic specifically for the new app, unless the reader in the new app and the web site are actually the same thing, perhaps we should fork this conversation into it's own topic devoted to feedback for the new web reader. I know the new web site feedback thread (that's locked) was the original place to offer up feedback about things people want, but I don't think a specific topic was ever set up after the new site topic was locked down (I could be wrong about this and just haven't seen said topic though).
