I found some inconsistencies with the spelling of "Validator" and "validation" and also in Validator.php "Requireimage.php" was different than the actual filename

hello, this is awesome, so much like twitter. The likes, retweet and follow function are working great, but I've got a problem with Reply Tweet and Reply Comment, the view was stuck and didn't update the database

• When I login with the user/pass info from the SQL database there is an error. So I can only login after sign-up as a new account.

• After creating a couple of new user accounts and then login to verify authentication, I wanted to save my data. Where is all of that stored and where does the server save live data in a specific folder?

• So many bugs and because I noticed this is only a clone of the original. The problems were mostly fixed by updating links.

• Really awesome! Great work! Thanks!

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

I modified the database to hold 512 characters tweets and retweets, but I can't figure out how to modify the php or js code to allow for the larger amount of characters

unique_id() is timed to the current date and time. if someone else access the server at the same time and uploads, their image could be named the same as yours.

i programmed a work around using a hash256 of the image file contents, and a unique image record of the image file name with subdirectories t allow for millions of images.

in the process i moved all images to the images directory with subdirectories. I don't know how to post all that here4 but can send you my modfied files.

When I click on Notifications the above-attached error comes. The error stays on the right side of the screen. I was only able to get half of the error message in the screenshot.