/kemono/ - kemono.party

yeah

imports stopped again. don't know what's going on. either it's the new site interface or also a problem with the adblockers.

>>49456
> crappy post loading
On which page?
> many scripts for tampermonkey broke
That's the problem of tampermonkey scripts, report to the repos of respective owners.
> Scrapping softwares couldn't function properly
That's the problem of scraping software, report to the repos of respective owners.
> frequent error notifications
They are more "frequent" because it opts into crashing instead of redirecting to `/artists`.

>49951
>on which page?
ofc on the posts page u fkin nigger
>"That's the problem of tampermonkey.."
yeah it is but why change the site UI when so many irregularities occur simultaneously
>"That's the problem of scraping .."
its the site that changed it UI without adding any possible useful features and also causing new problems.
>"They are more "frequent" because.."
stating the cause doesn't change the fact that it is frequent you retarded wannabe smart mf
I just told all the problems the new update is causing to someone who can listen to it and not some brainless dumbfuck like you to spread useless knowledge.

Someone in charge didn't get the 'If it aint broke, don't fix it' memo

>>49529
> ofc on the posts page u fkin nigger
There are at least 3 "posts" pages, you inbred mongoloid.
> yeah it is but why change the site UI when so many irregularities occur simultaneously
How does it have to do with anything?
> its the site that changed it UI without adding any possible useful features and also causing new problems
No, it's a problem of third-parties relying on specifics of markup rendering. That's always a problem of logic relying on scraping. Instead of bitching about the site go help fix/test those scripts/scrapers (which are all open source, as far as I know).
> stating the cause doesn't change the fact that it is frequent you retarded wannabe smart mf
You are an absolute fucking retard if you think hiding an error has anything to do with frequency of errors. No one give a shit about them before so they were swept under the rug. I do care which error was caused on which page, so shut the fuck up and post it in the issues thread when you encounter it. Error messages also happen to include the URL of the page, so that just skips at least 2-3 back-and-forths (like in this thread) of trying to figure which page any given retard talks about.
>>49560
If you think this "ain't" broke then you have no idea.

>>49571
I meant it wasn't broke before they updated it.
Now that they've updated it, it's all kinda of screwed up.

>>49456
The interface update wasn't even needed, nobody asked for it. It was fine before.

All people wanted was working importers. If it works don't break it.

>>49730
> The interface update wasn't even needed, nobody asked for it. It was fine before.
The "nobody asked for it" crowd didn't give a shit in the first place. There were apparently 2 bugs present for at least 1 year and not a single soul bothered to report it. And those were quite in your face too, so the average user is not only retarded, but also quite blind.

> All people wanted was working importers. If it works don't break it.
Good, you can contact the admin with your portfolio and help working on importer then. Be the change people needed!
Also the site code and the importer code barely interact with each other, not sure why you are conflating the state of importers with the state of the site.

>>49456
Does anyone have any ideas for new updates or new features?

>>50094
Everyone does, but no one wants to spend time implementing them.

>>50094
To break the site even harder?