On 12.02.2011 23:38, tagnaq wrote: > I'd like to edit the torservers wiki [1]. > Currently it does not offer https but requires login to edit pages. > Please configure it to support https (I guess you have to move it to > another server/IP to do that properly). > You might also want to upgrade to mediawiki to the latest version [2] You caught me here. The wiredwings wiki was never meant to be anything but temporary. I'm setting up a proper wiki right now. I'll let you know when it's done so you can help migrate the information from the old wiki. You're right, I need to move it someplace else for HTTPS. Does anyone run a well connected server, ideally where we can serve the website as hidden service as well? A VPS would be good because for the planned multilanguage features I need to be able torestart the webserver from time to time (gettext caching...). > It would be sad if that information gets lost or is simply not > documented (even if they don't reply, or if the answer is negative). Very true! The main reason for Torservers is that stuff like this is heavily underdocumented. I can definitely use some help. We need a bug tracker, too. :-) I was hesitant to put my ISP research into the temporary wiki. I have tried to update Torproject's GoodBadISPs log too. The thing is that many ISPs will probably be good enough to host a small Tor exit. If you use the limited exit policy on a low traffic node (and by low I mean less than 5TB a month) it might work quite well even when you receive some complaints from time to time. Most ISPs stop "working" at >15TB, and I try to nail them down quite a bit. -- Moritz Bartl http://www.torservers.net/