Feedback Technical Grievances

  • 🔧 Site instability resolved. You can report double-posts and broken attachments. For bigger issues, use the Technical Grievances thread.
    🇵🇦 Nuestro primer dominio localizado está en español en kiwifarms.pa. Our first localized domain is on Spanish on kiwifarms.pa.
  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Destacado
Did you move away from using invidious as the default because it kept shitting bricks on everyone or what happened with YouTube videos embedding to invidious? Asking because I actually liked the invidious embeds.
 
This isn't much of a technical grievance, more of a question I'm curious about. So we noticed bots coming from a splinter site which I won't name. Can you track the IP of those bots or are they switching up IPs?

Apologies if this isn't the right thread for this question, if it was answered already I didn't see it.
 
Hey, This might be a stupid question I was hang out in some threads and some of the posted Youtube videos would say they are unavailable but others will work just fine. Is it my web browser or Youtube itself I use Fire Fox as my browser,
 
XenForo has a bizarre design where if you update almost anything in the ACP, it will invalidate cache records and attempt to build them in the request cycle. In modern development, the cache record should serve stale (outdated) records until the new record is built. The new record would be built by either another thread, or on a CRON job for PHP.

XenForo does this differently. Instead, it immediately deletes the old record and every single request made to the forum for any page anywhere tries to rebuild record. On Kiwi Farms, this will happen approximately 500 times before the MySQL database starts refusing new requests, causing Error 502 (even if this limitation were lifted, it would not render the page, only add more people trying to rebuild the same record until the new limit is reached, or the database crashes). Depending on the record, this can be resource intensive. There is no way to stop it from doing this. If I update the sidebar, it breaks the site for 10 minutes.
 
Null dijo:
XenForo has a bizarre design where if you update almost anything in the ACP, it will invalidate cache records and attempt to build them in the request cycle. In modern development, the cache record should serve stale (outdated) records until the new record is built. The new record would be built by either another thread, or on a CRON job for PHP.

XenForo does this differently. Instead, it immediately deletes the old record and every single request made to the forum for any page anywhere tries to rebuild record. Depending on the record, this can be resource intensive. There is no way to stop it from doing this. If I update the sidebar, it breaks the site for 10 minutes.
Presiona para expandir...
So you're saying we essentially ddos'd ourselves by checking to see if it was still up for the past hour?
 
Null dijo:
There is no way to stop it from doing this.
Presiona para expandir...
Out of curiosity, why can't it be stopped?

In the long long ago, I remember fixing binaries by inverting the logic of the problem branch.

Often by changing the x86 instruction from like jne (jump if not equal) to je (jump if equal).. 0x75 to 0x74 in a hex editor of the binary.

What's the problem with Xenforo?
 
Destacado
Debes iniciar sesión o registrarte para responder aquí.
Atrás
Top Abajo