Today I made a new osm account cause I moved back to my home country and wanted a fresh start, yada yada, I started mapping details of my neighborhood in josm and I was going on and on, it was fun. It’s a bad habit of mine to let changesets grow. It was a 1000 and a hundred or so objects to upload, it said it will upload them in two requests. Seems like just the first request (first 1000) kinda worked and the 100 didn’t, some error showed up, something about rate limit, thought it meant my slow internet connection and I’ll just try again in a while. Meanwhile I wanted to check out the already uploaded changes and I saw all this mess that I don’t know why it happened. I realized that the rate limit must have been something about a new user uploading too much too soon, but aren’t you just blocked to a later time or flagged for review when you exceed the limit? In a panic I tried reverting it with the josm reverting plug-in but nothing has changed (map data still shows scrambled in incognito tab).
Did you move the nodes of the affected buildings? Looks like some of the node movement edits got blocked by the server due to the rate limit and only some nodes of the buildings got moved.
Leave josm open and try again in an hour.
Your revert changeset never actually happened
https://www.openstreetmap.org/user/codywindrose/history
Having chunking turned on (in your case max 1000 changes per changeset) is a recipe for near guaranteed disaster on a new account*.
As @Woazboat pointed out the 2nd upload likely was refused due to the rate limiting. The problem is that the individual ‘chunks’/uploads are in themselves not referentially complete (no editor I know of does this). So you will have had mostly nodes in the first upload and mostly ways in the 2nd, and when the 2nd upload failed you were likely left with a bunch of untagged way nodes without the ways (or way modifications).
You can recover from this (aka save at least what was completely uploaded) but it is a pain, you might just simply want to get somebody to revert the changeset.
See also SimonPoole's Diary | Handling failed uploads properly | OpenStreetMap particularly the Now for the tricky bits section.
* as the editing app however can know that it is a new(ish) account, chunking should probably be disabled, or a warning displayed in this situation.
no, just that specific edit is blocked
no, it is limit applied to new accounts
it seems that it was done by someone else now
@cyberutilia Can you disable it for now? If you have a valid reason for new account, then make for now more smaller edits until your rate limit allowance grows?
… and open a JOSM ticket? (josm.openstreetmap.de)
A very helpful link, thanks also to the others for linking to more resources. The failed changeset has been reverted by someone else (uh, maybe my revert attempts didn’t work also cause it was a completely new account?). I had saved the edits on my computer before I tried that fateful upload, so using a lot of the replace-geometry tool in josm, I got back most of the edits and by now I’ve mapped the area much further 
To be safe, I’m getting used to uploading in smaller portions, around 500 or so objects. That also means that the changeset comments can be more granular, instead of writing one comment for the upload of thousands of objects. Checking more often how big the current edit count is and adding a fitting comment more often does add friction but it is what it is.
I’d actually suggest fewer than that, at least until your new account has got more edits under its belt…
revert is also an edit, so if you were rate limited then attempted revert also got rate limited (stopped) if you did it immediately, before quota was refilled