[ / / / / / / / / / / / / / ] [ dir / random / 93 / biohzrd / hkacade / hkpnd / tct / utd / uy / yebalnia ]

/jim/ - Jim

Jim
Email
Comment *
File
Password (Randomized for file and post deletion; you may also set your own.)
Archive
* = required field[▶Show post options & limits]
Confused? See the FAQ.
Embed
(replaces files and can be used instead)
Oekaki
Show oekaki applet
(replaces files and can be used instead)
Options

Allowed file types:jpg, jpeg, gif, png, webp,webm, mp4, mov
Max filesize is16 MB.
Max image dimensions are15000 x15000.
You may upload5 per post.



File: 1458228222973.j⋯.jpg (74.79 KB,640x360,16:9,pepe irl.jpg)

c5550d No.2061

>Back pages are disabled to save on I/O write. Use the catalog to find threads on pages greater than 3.

Any chance of this getting fixed?

____________________________
Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

7e9284 No.2062

File: 1458291381222-0⋯.jpg (2.36 MB,2576x1932,4:3,20160314_103315.jpg)

File: 1458291381334-1⋯.jpg (2.04 MB,3264x2448,4:3,20160316_193455.jpg)

Probably a good chance of that being fixed soon. I am meeting with HW tomorrow to discuss upgrades, and things that need to be fixed. We will try to get a list of gigs and start working them off.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

1fca0b No.2063

File: 1458291688542-0⋯.jpg (2.62 MB,3264x2448,4:3,20160310_071112.jpg)

File: 1458291688542-1⋯.jpg (2.44 MB,2576x1932,4:3,20160312_133223.jpg)

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

40fb37 No.2071

>>2062

Awesome. Thank You based Jim. I use the Exodus app and can only see 3 pages back, so I would highly appreciate it.

Not the OP

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

b38b1f No.2072

It'd be pretty cool if banners were able to be edited again. I'm worried. Is everything okay?

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

27580f No.2078

Don't fix the site jim, it adds flavor to the site. The 8chan experience.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

f33c6f No.2079

Sorry if my post asking if you were okay was unwelcome.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

9b38bd No.2080

>>2061

>Any chance of this getting fixed?

Become a mod.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

a10089 No.2180

>>2061

It has been fixed yesterday. Just bump a thread from beyond page 5 and you are golden.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

aeeb5b No.2628

Hey Jim, could you please have Ron redirect e0001 pages to their proper "sys." URLs?

There are maybe hundreds if not thousands of threads and boards completely broken with an "e0001" error that can be fixed by simply inserting "sys." into the URLs. This can be fixed with a simple script. See >>/sudo/7876 for a working javascript hack.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

b2699c No.2629

>>2628

>>>/sudo/7876

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

38780f No.2630

File: a71ac1f7f3c3d7a⋯.jpg (482.43 KB,1382x2000,691:1000,qatar.jpg)

>>2628

No, that is not the fix. The BO needs to login and make a post from the mod.php that will fix the individual boards. Actually anyone could do that from mod.php.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

600282 No.2631

File: daeac33718b50e4⋯.jpg (240.77 KB,1288x900,322:225,maga family.jpg)

>>2630

That fixes the front page of boards but not individual threads. This is a new, major problem where many individual pages and threads return the error e0001 as if they have been deleted, when in fact they've been moved to the sys domain. Unlike before where it is just boards returning the error, it is now dozens of individual pages and threads within the boards that return e0001. As you can imagine with 8chan currently hosting 11,143 boards as of now, it adds up to a staggering amount and people are freaking out that their threads have been deleted when in fact they haven't.

Would it be possible for you to make e0001 errors automatically redirect to the working sys URL? This can be done through HTTP redirection which is a frankly easy-to-do workaround. I don't mean that condescendingly, I just know that it should take a tiny fraction of the time Ron spent to write his Alacrity caching system to implement this as a temporary workaround (so that people stop complaining about e0001).

For example:

see http://8ch.net/dbz/res/515.html

and http://sys.8ch.net/dbz/res/515.html

If you try to access >>>/dbz/515 it returns e0001 (as of now). But if you simply add "sys." preceding the URL, then it works. Nobody is aware of the sys domain which is why I'm urging your team, whenever they have the time, to work on making 8chan redirect e0001 errors automatically to the working sys URLs.

Thanks.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

e590ac No.2632

>>2631

These are good points. Please bring them up on

>>>sudo/

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

b373cd No.2633

>>2631

Nobody has posted on this thread since May of last year.

http://8ch.net/jim/res/380.html

It is not 404. This really is an edge case scenario.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

acf7e3 No.2634

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

4b1482 No.2635

File: 72aa5419e1704ed⋯.jpg (61.19 KB,486x640,243:320,image.jpg)

>>2633

It's not edge case scenario if you are judging by last post date. People are complaining about a much more severe problem.

Just from the first two pages of /lit/:

>>>/lit/11384 Last post 4 days ago

>>>/lit/11383 Last post 4 days ago

>>>/lit/11380 Last post 4 days ago

>>>/lit/11373 Last post 5 days ago

>>>/lit/11353 Last post 10 days ago

>>>/lit/11339 Last post 14 days ago

>>>/lit/11334 Last post 16 days ago

>>>/lit/11358 Last post 11 days ago

I could go on an on as this is just the first 2 pages of /lit/ which has 15 pages total.

Since 8 threads in the first 2 pages are broken with e0001, you can estimate that /lit/ has 60 broken threads in total.

And this is just /lit/. Every board on 8chan has been affected by this problem. Some more so, some less so. Again, this new problem is very severe unlike before, where it was just the front page of a board that didn't work.

To drive the point further, here's another random board I chose: the first two pages of /fighters/

>>>/fighters/8427 Last post 9 days ago

>>>/fighters/8426 Last post 9 days ago

>>>/fighters/8416 Last post 10 days ago

>>>/fighters/8409 Last post 19 days ago

>>>/fighters/8402 Last post 29 days ago

>>>/fighters/8316 Last post 32 days ago

Again, it would be really great if you could add automatic HTTP redirection whenever a thread returns e0001 since all these links work if you add "sys." to the beginning.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

cbd46f No.2636

>>2635

Actually that is not the solution. I fixed the dragon ball z board the way I told you.

I used my trip when I did it so you can see how.

The sys server is not real time. That is not the one to use.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

6ed112 No.2637

>>2636

It didn't fix the board, just the front page and the couple individual threads that you posted in.

There are still a bunch of e0001 threads on /dbz/ that were working fine until October 17, 2016 when this site-wide problem happened where a bunch of threads and board assets were moved to and stuck on the sys server.

These are not edge case scenarios, these are all on the 1 and 2nd pages of /dbz/:

>>>/dbz/592

>>>/dbz/547

>>>/dbz/540

>>>/dbz/507

I know that sys is not real-time, but sys is the only way to view the threads and post on them in the first place to fix them. I am not saying all threads should be redirected to sys, what I am saying is that only e0001 threads should redirect to their corresponding sys links as a workaround to this major problem.

The problem is not that one individual thread or one individual board's front page is not working. If that were the problem, then I agree that your mod.php solution is probably good enough. What we are witnessing is tens of thousands of threads all of a sudden vanishing on October 17, and the only way to view or bring them back is to go to their sys URLs or use a mod.php account. I think you would agree that it would be crazy to have to post in these tens of thousands of threads individually with your mod.php solution just to have them viewable again. Hence why we would like auto-redirection to sys, only for e0001 threads, to deal with this problem all in one go.

Whether you post using mod.php or post on their sys URL, the effect is the same. The sys solution is more convenient because it does not require login. To reiterate, what we would like is for the sys redirection to be automatic whenever you see a blank page with the error e0001.

Notice if you go to:

http://8ch.net/dbz/res/547.html

It displays e0001.

Now if you go to:

http://sys.8ch.net/dbz/res/547.html

You can see the thread and you can post in it. If you post in that thread, it fixes the thread and no longer displays e0001. That is why we want it to automatically redirect to that sys URL as a convenient workaround to this problem.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

4cdbce No.2638

>>2636

better to have non-real time than nothing at all…

half of the threads on my board now display e0001 and its a pain in the ass to post in every single one of them just so people can view them as theres 25 pages total

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.

1513b6 No.2640

>>2638

Well the hardware had failed and was replace. It is good that the data is still there. Go to your catalog and post on the farthest back one you can. It should recreate the board. I was able to do it that way.

Disclaimer: this post and the subject matter and contents thereof - text, media, or otherwise - do not necessarily reflect the views of the 8kun administration.



[Return][Go to top][Catalog][Nerve Center][Random][Post a Reply]
[]
[ / / / / / / / / / / / / / ] [ dir / random / 93 / biohzrd / hkacade / hkpnd / tct / utd / uy / yebalnia ]