[X] My Assistant

As for EDs, I'll consider adding some other sources for them, they just can't be farmable.

I guess replace the tokens from lotteries to EDs and put a exchange rate of 20 tokens = 1ED?

It seems that Tenboro has finally decided to stop supporting outdated browsers. This new code seems to be incompatible with the version of Firefox I use, and no, I do not plan to update it because I do not like the interface and high consumption of the new versions of Firefox.

Well, it's a shame but it seems that this is how far my fun goes, it's time to leave this page.

Enable menubar
browser.urlbar.formatting.enabled -> false
browser.urlbar.maxRichResults -> 0
keyword.enabled -> false
layout.spellcheckDefault -> 0

And then it's fine? What else about the UI is annoying you?
I start with tor browser, which is closer to my preferences, but I got rid of everything annoying in Firefox too.

Enable menubar
browser.urlbar.formatting.enabled -> false
browser.urlbar.maxRichResults -> 0
keyword.enabled -> false
layout.spellcheckDefault -> 0

And then it's fine? What else about the UI is annoying you?
I start with tor browser, which is closer to my preferences, but I got rid of everything annoying in Firefox too.

I prefer the Firefox 19 design when it had the orange button in the upper left corner, I like the element inspector of that version much more.

I also said that the new browsers consume too much power and overheat my computer, I have a laptop so excessive heat kills my batteries and I don't want to have to be buying new batteries because of something I can avoid.

Finally, the Hentaiverse code was working fine until version 89, so it seems somewhat irrational to change the code completely at this point.

Well, it doesn't matter, I just wanted to complain before leaving this site, as now I will no longer be able to earn the credits/gp needed to download doujins.

This post has been edited by Brian Alvarez: Apr 10 2023, 23:44

It's in the best interest of the web developer and their users to make sure that the website supports the latest browser to improve security and reduce the number of attack surfaces that hackers can exploit.

You do know that using an outdated web browser puts you at risk right? Asking a web developer to support obsolete software that doesn't meet modern standards is like asking them to intentionally put backdoors into their own system just so you can feel comfortable using an old Firefox UI.

This post has been edited by yetsun: Apr 11 2023, 05:25

I also have a laptop, and I don't have that problem.

I also have a laptop, and I don't have that problem.

Firefox 19 was released in 2013, so I'm assuming their laptop is quite old. But you're right, Firefox 19 and the current Firefox 111 seem to have the same system requirements on paper, aside from the fact that 111 no longer supports XP and Vista like 19 does. But who knows. Regardless, I agree it makes no sense for a developer to support such an old browser, especially when it's a security risk.

I also have a laptop, and I don't have that problem.

Then your laptop has a very good cooler.

Firefox 19 was released in 2013, so I'm assuming their laptop is quite old. But you're right, Firefox 19 and the current Firefox 111 seem to have the same system requirements on paper, aside from the fact that 111 no longer supports XP and Vista like 19 does. But who knows. Regardless, I agree it makes no sense for a developer to support such an old browser, especially when it's a security risk.

I got my laptop 10 years ago from school and I make enough money to keep me alive, so I can't afford a better one.

I'm also talking about machine power, new browsers require more power than old ones, add that to a very old laptop with a useless cooler and you get an overheated PC and a dying battery.

Finally, why in all these years using Firefox 19 I never had security problems? If you have these types of problems you should install a better antivirus.

Also who in the name of fuck would attack Hentaiverse's site, it's just a text-based game, not Bill Gates' bank account.

Then your laptop has a very good cooler.

The case is the heatsink, there's no fan, and it has four little feet that hold it above the desk for airflow underneath. Energy efficiency has improved in 10 years. I don't want to sound like a constant shill for Pine64, but you could get the laptop I'm using for $220. Batteries are $20 if you ever need one.

If you want a browser, that "feels" like old firefox, you could check out Pale Moon browser. Though I can't say anything about how demanding it is on hardware.

The case is the heatsink, there's no fan, and it has four little feet that hold it above the desk for airflow underneath. Energy efficiency has improved in 10 years. I don't want to sound like a constant shill for Pine64, but you could get the laptop I'm using for $220. Batteries are $20 if you ever need one.

I'm sorry, but I live in Argentina and if the economy here got worse, we'd be killing each other for some food, so $20 is too much for a battery, also when I said I make enough to stay alive, I really meant it.

If you want a browser, that "feels" like old firefox, you could check out Pale Moon browser. Though I can't say anything about how demanding it is on hardware.

I have already tried Pale Moon and the element inspector uses the new design instead of the old one, I am a web designer, so I need the speed of the old design. It also has the same demand for power that new browsers have when loading a page with modern javascript and ends up lagging.

Finally, the reason why this end of support is a problem is because now I and other people like me will not be able to get credits/gp to download galleries. I get some gp from the galleries I've uploaded, but it's not enough to download more than 3 doujins per day.

If your browser is more than five years obsolete compared to the baseline of modern rendering engines (Chromium/Gecko) and something doesn't work on it, I'm not going to change it. If people want to put themselves at risk by going out to sea in a sieve, that's their business, but new browsers add new functionality that we eventually are going to start using regardless of the <1% who still use an ancient browser for whatever reason.

Not to mention that with HTTPS being used everywhere now, old browsers have a built-in expiration date after which they won't work anywhere anyway, due to expiring/added root certificates, and there's nothing websites can do to work around that.

If your browser is more than five years obsolete compared to the baseline of modern rendering engines (Chromium/Gecko) and something doesn't work on it, I'm not going to change it. If people want to put themselves at risk by going out to sea in a sieve, that's their business, but new browsers add new functionality that we eventually are going to start using regardless of the <1% who still use an ancient browser for whatever reason.

Not to mention that with HTTPS being used everywhere now, old browsers have a built-in expiration date after which they won't work anywhere anyway, due to expiring/added root certificates, and there's nothing websites can do to work around that.

Let me tell you in advance that I'm sorry for the wall of text, since you took your time to answer me, I wanted to take this opportunity and say everything I had to say, and although it's a shame that I can't continue playing this game, I don't hate you for the change you've made to it.

You're free to change your site all you want, but that doesn't explain why you had to change the code to a point where the game stopped working, as I said before, the code worked fine in update 89, so there should be a way to fix it if you tried to see what's causing the problem.

Also the risks you are talking about can be easily stopped with a good antivirus without using code that works only with modern browsers, it seems that you gave up programming and chose to take the easy way.

And in case you want to try it and fix it, I used the web console to see what's causing the problem and it looks like the script isn't loading the functions properly, it's your choice if you want to turn all my years playing Hentaiverse into a waste of time.

Finally, let me remind you that this is a text-based game we are talking about here, a game like this can even be made with primitive javascript, if your game used unique functions like those used in modern browsers, then it would be understandable to update your code in this way, but instead all this game does is get elements and replace their contents or send XMLHttpRequests, things that can be done even in my browser.

Anyway, thank you for making this game, it was so much fun to play it all these years, it's a shame to give up on it, but I will continue with my life, maybe one day I will find another game as good as this was. Good bye.

You're free to change your site all you want, but that doesn't explain why you had to change the code to a point where the game stopped working, as I said before, the code worked fine in update 89, so there should be a way to fix it if you tried to see what's causing the problem.

I don't change things just for the sake of changing them, but if I'm making something new I'm not going to write 2008-era code when some DOM/CSS functionality that was added to browsers in 2018 takes 10% of the work and works much more reliably in modern browsers and on mobile.

Also the risks you are talking about can be easily stopped with a good antivirus without using code that works only with modern browsers, it seems that you gave up programming and chose to take the easy way.

Uh, no, it can't. Antivirus is like a canary in a coal mine; it tells you that something is horribly wrong, it doesn't suck up all the toxic gas and makes it okay again. If something exploits a remote arbitrary code execution flaw in your browser, your antivirus isn't going to do jack shit.

But the vulnerabilities only affect the user (i.e. you), it's not relevant for the site, so it's like I said, if you don't care it's your business.

I don't change things just for the sake of changing them, but if I'm making something new I'm not going to write 2008-era code when some DOM/CSS functionality that was added to browsers in 2018 takes 10% of the work and works much more reliably in modern browsers and on mobile.

If that were true, 90% of the internet wouldn't work in modern browsers because almost all sites still use old javascript functions, I've been using this old browser all this time browsing smoothly, so I know that from experience. And I'm sorry, but I don't have a mobile, so I can't speak for people who do.

Also preferring to use features that only work in updated browsers because it makes it easier for you means you gave up programming to go the easy way. You chose simplicity over optimization.

Uh, no, it can't. Antivirus is like a canary in a coal mine; it tells you that something is horribly wrong, it doesn't suck up all the toxic gas and makes it okay again. If something exploits a remote arbitrary code execution flaw in your browser, your antivirus isn't going to do jack shit.

But the vulnerabilities only affect the user (i.e. you), it's not relevant for the site, so it's like I said, if you don't care it's your business.

If that's true, explain to me why in all these years using Firefox 19 and Windows 7, even after they stopped being supported, I never had a security issue.

What an antivirus actually does is stop a virus when it is detected, then the program proceeds to remove it before it causes any damage to your system. If you were right, then my PC should be dead right now.

Also, it's not your responsibility to handhold people so they don't end up in a dark alley with shady people, it's their responsibility to learn how to protect themselves against the dangers of the internet. If you keep protecting them, they will never learn and grow.

Anyway, because you seem to be too afraid to try to see and find the problem using an outdated browser I copied what the web console says, here you go:

CODE

[12:49:27.811] SyntaxError: invalid object initializer @ https://hentaiverse.org/z/090c/hvc.js:26
[12:49:27.891] ReferenceError: at_attach is not defined @ https://hentaiverse.org/:56
[12:49:27.963] ReferenceError: common is not defined @ https://hentaiverse.org/:180

Finally, let me tell you that I don't use new browsers because of their design, that's something I said because that's my preference, but the real reason I don't use them is because my situation makes me unable to use them, if I could use them I would use them, but not everyone is blessed enough to have a good job or to live in a good country with a good economy. That's it, I just wanted to make it clear.

I wish you a good day.

EDIT:

I have already found and fixed the problem, it seems that the "api_call" in the "Equips" function does not load properly, so I took your code, removed that part and made a userscript to use it with the GreasyMonkey addon, now the game works completely fine, except now I can't unlock equips, but at least now I can continue playing this game.

Here is the problem in case you want to fix it:

CODE

api_call(m,{type:"simple",method:"lockequip",uid,token:simple_token,eid:b,lock:"il"==k.className?0:1},function(){var t=api_response(m);if(0!=t&&void 0!=t.eid){k.className=t.locked?"il":"iu";var r=e("e"+b),q=r.getAttribute("data-locked");if(q){if("0"===q&&r.getAttribute("style")&&r.onclick)r.onclick();r.setAttribute("data-locked",t.locked)}}})

This post has been edited by Brian Alvarez: Apr 14 2023, 21:59

If that were true, 90% of the internet wouldn't work in modern browsers because almost all sites still use old javascript functions, I've been using this old browser all this time browsing smoothly, so I know that from experience. And I'm sorry, but I don't have a mobile, so I can't speak for people who do.

Are you intentionally misunderstanding me? Yes, old code works in new browsers. No, new code doesn't necessarily work in old browsers. If you are using Firefox 19 (Date Released: Jan 30, 2013), there is a long list of things we use that doesn't work/render correctly on it, simply because it didn't exist when it was released. Most likely it's the lack of ECMAScript 2019 support that completely breaks it, which would work in Firefox 64 and newer. More than anything, I'm surprised it was still working up until now, but it is no longer supported and will not be supported.

Are you intentionally misunderstanding me? Yes, old code works in new browsers. No, new code doesn't necessarily work in old browsers. If you are using Firefox 19 (Date Released: Jan 30, 2013), there is a long list of things we use that doesn't work/render correctly on it, simply because it didn't exist when it was released. Most likely it's the lack of ECMAScript 2019 support that completely breaks it, which would work in Firefox 64 and newer. More than anything, I'm surprised it was still working up until now, but it is no longer supported and will not be supported.

I have already fixed the problem with a userscript (see my edit above your comment), the code worked fine except for one part.

It seems that the "api_call" that locks/unlocks the equips did not work and that prevented the rest of the code from loading correctly, an advice from one programmer to another, try to use the "try()" function, which allows you to test a code without causing problems with the rest of the code.

Sorry if I was an ass while talking to you, I've been playing this game for years, so the thought of having to give it up was really affecting me, and I say it again, a game like this really can be made with simple javascript without needing all the new features that new browsers have, also there are better ways to protect a site from attacks.

I'm sorry for still being a nuisance, but I wanted to say that I've found the exact part in the code that's causing the problem.

I've found that changing one part in the "api_call" of the "Equips()" function solves everything.

You only have to replace:

CODE

{type:"simple",method:"lockequip",uid,token:simple_token,eid:b,lock:"il"==k.className?0:1}

For this:

CODE

{type:"simple",method:"lockequip",uid:uid,token:simple_token,eid:b,lock:k.className=="il"?0:1}

I will let you choose whether to take my help to fix this problem or not.

I'm sorry for still being a nuisance, but I wanted to say that I've found the exact part in the code that's causing the problem.

I've found that changing one part in the "api_call" of the "Equips()" function solves everything.

You only have to replace:

CODE

{type:"simple",method:"lockequip",uid,token:simple_token,eid:b,lock:"il"==k.className?0:1}

For this:

CODE

{type:"simple",method:"lockequip",uid:uid,token:simple_token,eid:b,lock:k.className=="il"?0:1}

I will let you choose whether to take my help to fix this problem or not.

Your browser can't understand this syntax? IIRC it's from 2015+ ish.

It might be worthwhile for the site to use Babel or some such thing to ensure support for older browsers.

I found a market bug. Scroll of absorption's current price in isekai is 10 credits, which is the minimum price allowed. At that point, the "Min Undercut:" text is replaced with "Min Ask Price: 10 C," but clicking it sets the price at 9 C instead.

At the other end of the spectrum, mana draught and spirit draught have no current sellers in the isekai market, and "Min Ask Price: 10 C" is shown. It would be a lot more helpful if it was "Max Ask Price: 4980 C."