Richard
(Richard Fairhurst)
9
I’m no expert on the server (if you want a more authoritative answer you should ask on the dev@ mailing list), but - they are already served with a higher priority. See http://trac.openstreetmap.org/browser/sites/rails_port/config/lighttpd.conf - all the ‘write’ operations are served by /dispatch.api, whereas more of the ‘read’ operations are served by /dispatch.bulkapi which has a lower priority.
There are still some problems - in particular, Potlatch’s write operations will sometimes be carried out but not return a success code to the Potlatch client. We have really good guys working on the server and the problems that have arisen with API 0.6 will be ironed out in time. But these are not simple things to fix.
Many of the problems have historically come from memory leaks in Rails and associated libraries (particularly the XML ones), and Rails is a. not our codebase and b. not that easy to debug! If you look through various mailing lists you will see our sysadmins are actively fixing bugs in other people’s code where necessary - e.g. http://www.mail-archive.com/libxml-devel@rubyforge.org/msg01330.html .
I hadn’t but I shall go and have a look now. 
No, but I can’t fix the code if no-one tells me about the error! There appears to be a bug in the Potlatch client at the moment that shows up sometimes when splitting ways; this causes the “node -3 not found in way” -type error. But thus far I can’t reproduce it. If you can find consistent steps to reproduce then that would be the single most helpful thing.
I’m afraid I don’t agree. If you make ways unlock automatically when they’re connected to another way, then people will start using that method to unlock ways - even if they didn’t want to create a connecting way in the first place. So you’ll get unnecessary ways created.
There is already a good method to unlock a way: click the padlock. That you didn’t realise this appears to be a mistake in the German documentation, not in Potlatch. But then, the next version of Potlatch will have greatly improved documentation built in, and if I can stop answering forum questions for five minutes I might have a chance to finish it this week. 
Thanks for the comments as ever.