Topic: blacklist not working on mobile

Posted under General

This is probably the most helpful bug report ever filed in the history of computing.

Updated by anonymous

KiwiPotato said:
Srsly the blacklist could not work more horribly' what the fuck is going on lol

mobile doesn't run the javascript engine, it is too advanced for many peoples piece of shit phones. That's the reason there is a mobile.

Updated by anonymous

null0010 said:
This is probably the most helpful bug report ever filed in the history of computing.

You're very far off on your sarcasm.

Updated by anonymous

Aurali said:
mobile doesn't run the javascript engine, it is too advanced for many peoples piece of shit phones. That's the reason there is a mobile.

I wonder if kiwipotato speaks of the mobile version of the site or just the site on a mobile phone...

Updated by anonymous

null0010 said:
This is probably the most helpful bug report ever filed in the history of computing.

I don't know how to be clearer than that.
There are posts that contain things I blacklisted. Most severe one I saw was guro.

Kclub said:
Blacklist works fine for me on my Android phone.

I have an andrioid too, devour.

Kimpumomo said:
I wonder if kiwipotato speaks of the mobile version of the site or just the site on a mobile phone...

sorry for not mentioning before, its the mobile version of site

Updated by anonymous

You mean the unofficial, unsupported by E621 mobile version of the site? You might want to talk to the guy who came up with it, because E621 staff don't have anything to do with it.

Updated by anonymous

ok, so I went to posts, clicked mobile and tried it.

blacklist not working.

I'm on an HTC sensation xe, using opera.

maybe this should be mentioned/fixed before letting people use this feature?

I still just use the normal site anyway, but still...

Updated by anonymous

Listen to what the lady raigonetta said; the blacklist is a java function and the mobile loads so fast because it doesn't use java

Updated by anonymous

Rainbow_Dash said:
Listen to what the lady raigonetta said; the blacklist is a java function and the mobile loads so fast because it doesn't use java

so the mobile function, as it is now, will not be compatible with blacklist?

or is there some way of incorporating it later on?

Updated by anonymous

KiwiPotato said:
I guess?

You guess? You don't know the address you're visiting for a mobile version of the site? It's kind of important, because if it's the one I linked, it's essentially a fan-made version of the site and not officially supported by the E621 staff, so complaining about the blacklist not working on here isn't going to do you any good, as you need to go to the developer to report it.

Updated by anonymous

It shouldn't even run on Java in the first place.

It also shouldn't be running via what it does run on, which is Javascript. There's a huge difference.

There is no reason why the blacklist can't be operated serverside and not via a script that could be blocked.

Updated by anonymous

GreyMaria said:
There is no reason why the blacklist can't be operated serverside and not via a script that could be blocked.

Yeah but that would make the server do that much more work, which is like a million times more than it already does

Updated by anonymous

Rainbow_Dash said:
Yeah but that would make the server do that much more work, which is like a million times more than it already does

How would it do very much more work? How hard is it to simply not print the thumbnail for an item if the query finds a tag combination? <.<;

Updated by anonymous

GreyMaria said:
How would it do very much more work? How hard is it to simply not print the thumbnail for an item if the query finds a tag combination? <.<;

Multiply that by the millions of accesses to pages on e6 (posts list, forum threads, comments list, user avatars, etc). Oh and because it's simpler in javascript, dunno how Ruby works, so I may be wrong :/

Updated by anonymous

Xch3l said:
Multiply that by the millions of accesses to pages on e6 (posts list, forum threads, comments list, user avatars, etc). Oh and because it's simpler in javascript, dunno how Ruby works, so I may be wrong :/

You could optimize things so that only browsers without JavaScript support are redirected to a page with the blacklist done server-side; just stick

<noscript>
	<meta http-equiv="refresh" content="0;url=http://e621.net/post/PageWithServerSideBlacklist">
</noscript>

at the top of the default page. Everything that can handle the blacklist locally will overlook the <noscript> tag and behave as usual. The only extra server load would come from the half-a-dozen people who actually need it.

Updated by anonymous

Just two points: isn't the blacklist stored locally to begin with (not sure, which is why I'm asking)? And even so, creating a whole new set of server side scripts just for "half-a-dozen people" is a significantly inefficient use of manpower.

Updated by anonymous

Lyokira said:
Just two points: isn't the blacklist stored locally to begin with (not sure, which is why I'm asking)? And even so, creating a whole new set of server side scripts just for "half-a-dozen people" is a significantly inefficient use of manpower.

I'm not sure about RoR, but in PHP a couple style="display:none" attributes does not require a whole new set of server side scripts.

Updated by anonymous

As far as I know, the blacklist is stored on the server, as God and Obama intended it. I was rather interested by the report that was generated once upon a time of the most-blacklisted tags.

Also, it's Javascript, not Java. Sorry, that matters to me for irrational reasons.

Thoughts about technical feasibility

TL;DR Blah blah blah it seems possible, I don't really know, and I could be more insightful if I weren't a lazy fuck-all.

Hypothetically, the server-side code could apply a person's blacklist and return a page that, by default, includes only the non-blacklisted images.

I don't recall and can't be arsed to check right now whether the Javascript blacklister inserts code (Dynamic HTML for the... something) or just replaces the image sources. Or both. Anyways, if it replaces the images sources without having to do extensive code-generation for the image list, then there's hope that this is technically feasible without extensive code changes.

I presume the script already gets the proper image sources through some array provided by the server, else it couldn't un-do blacklisting an image when someone un-filters part of the results client-side. If that's also true, the blacklister might be able just be allowed to run normally without any code changes at all. It would be redundant effort at that point until someone un-filters a blacklist entry from the result set, but nobody cares because the blacklister takes zero time from the user's perspective.

But then, since I can't be arsed to even look at the Javascript right now this is all basically talking out of my frosted butts.

Thoughts about performance

I don't think applying the blacklists server-side would be incredibly onerous for the server, but I also don't know what the server's current CPU load is like. There was just a significant amount of work done to improve server performance because of issues. Then again, in my line of work that usually translates into "Okay, now let's piss away those gains as quick as we can before anyone notices!"

Personally, I like well-oiled websites. I wouldn't want to trade away performance for a feature that only exists because some mobile phone's browser can't handle the Javascript.

Then again, why are we insisting on using mobile browsers to browse the site's image collection, again? Can you seriously not wait until you get home for your porn fix? Or are you a minor and trying to hide your naughty habits from your parents?

Updated by anonymous

ikdind said:
Or are you a minor and trying to hide your naughty habits from your parents?

The owner of the contract may request the browsing history of any person under that contract.

Updated by anonymous

ikdind said:
Then again, why are we insisting on using mobile browsers to browse the site's image collection, again? Can you seriously not wait until you get home for your porn fix? Or are you a minor and trying to hide your naughty habits from your parents?

This. Not that I do this, nuh-uh, never, jamás. I wait like a 20-year normal person to get his smut on a computer, at home.

Updated by anonymous

I think It's mostly a matter of principals.

If a service is provided, it should work as intended, and if not, as expected.

This could all be fixed temporarily by telling mobile site users that their blacklist will not apply at this moment and why.

sounds good enough?

Updated by anonymous

reporting that the blacklist is doing its job 100% on this end

Updated by anonymous

Kimpumomo said:
I think It's mostly a matter of principals.

If a service is provided, it should work as intended, and if not, as expected.

This could all be fixed temporarily by telling mobile site users that their blacklist will not apply at this moment and why.

sounds good enough?

It does, but I can't understand why his blacklist doesn't work. I'm at mobile right now and my blacklist works pretty well

Updated by anonymous

Xch3l said:
It does, but I can't understand why his blacklist doesn't work. I'm at mobile right now and my blacklist works pretty well

mine doesn't either.

are you on the regular site or the mobile version?

Updated by anonymous

Kimpumomo said:
mine doesn't either.

are you on the regular site or the mobile version?

no caffeine regular version

Edit: Nope, blacklist does not work there *shudders*

Updated by anonymous

  • 1