You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's me again! I Established an instance of this site and have made some improvements that I will upload to GitHub soon. One thing I couldn't solve was a sudden spike and sustained high levels of processor usage when clicking on the comment or entering the quote tweet views, from the home feed. This causes mobile browsers to kill the site, and severely stresses the speeds of the site on desktops and laptops. I think it has something to do with the CSS or rendering of the popup somehow, because as soon as I click off the tab, the usage drops. It is also possible it has something to do with the javascript, I am not sure. Regardless, I cut out a bunch of CSS code that didn't need to be there, and I got the usage down by 10%- but it still won't function properly on mobile browsers. I can confirm however, that invoking the reply and quote popups from the status page (after clicking on a tweet in the timeline) functions as expected. I tested this on a fresh instance, and same issues. Website crashed on iPhone 8 running Safari on iOS 16, as well as a Macbook Pro running Monterey, and was slow on my trusty Thinkpad T500 running Debian and Firefox.
because you are trying to upload thousands of tweets at the same time 😂 of course it will crash.
for this you need to list tweets, you need to limit it by pagination or load.
It has nothing to do with css or js.
It's me again! I Established an instance of this site and have made some improvements that I will upload to GitHub soon. One thing I couldn't solve was a sudden spike and sustained high levels of processor usage when clicking on the comment or entering the quote tweet views, from the home feed. This causes mobile browsers to kill the site, and severely stresses the speeds of the site on desktops and laptops. I think it has something to do with the CSS or rendering of the popup somehow, because as soon as I click off the tab, the usage drops. It is also possible it has something to do with the javascript, I am not sure. Regardless, I cut out a bunch of CSS code that didn't need to be there, and I got the usage down by 10%- but it still won't function properly on mobile browsers. I can confirm however, that invoking the reply and quote popups from the status page (after clicking on a tweet in the timeline) functions as expected. I tested this on a fresh instance, and same issues. Website crashed on iPhone 8 running Safari on iOS 16, as well as a Macbook Pro running Monterey, and was slow on my trusty Thinkpad T500 running Debian and Firefox.
Link to my site, which I discovered the problem on, and the fresh instance (respectively)
https://spitter.loophole.site
https://spitter.loophole.site/spitter-project-master
The text was updated successfully, but these errors were encountered: