Rather than put all my tiny suggestions into 1 thread and let them get only 1-3 votes each I am going to type everything into a big thread.
1. Preventing binary files from being opened
Files like database files, .jar files, compiled code,…etc. You might accidentally open these files and all of a sudden the editor freezes and you have do to all sorts of problem solving. To solve this the editor attempt to guess whenther(MIMEtype checking, test decoding first few bytes, …etc) the file is binary, then display a dialog saying “Are you sure you want to open a binary file?”, with Yes or No buttons. There can even be a “exclude from binary file checking list” option.
2. Multifile variable checking
3. Built in rate limiting
Simply whenever a user requests a glitch.me page we check if the user’s ip is already in the database. If not create a new entry. Then store the users time that they requested the page as part of that users data in unix time, epoch time, or something similar. Before storing the time data if the user has already visited this page check the difference between the current time and the last time they visited. If the difference is lower than 50ms or some other number stop the request otherwise allow it.
Essentially what I am saying is that glitch should calculate each users average request rate and try to limit that to protect projects like gogs from being DDoSed.
4. Loading Screen changes
The application startup screen should display a progress bar depending on which stage it is on. An even better way would be an animation of water filling up the window and the water rises each time a loading stage is completed.
I’ll be adding more so be sure to check from time to time