Messages

Actually, it should be IMAP, port 143, and STARTTLS if you want security, and "normal password." Outgoing SMTP is port 25 (or 26 if your ISP blocks 25) also with STARTTLS and normal password.

If you go to Profile >> Forum Profile you should be able to upload an avatar picture there.

Here, or somewhere else? Because I don't think I've even seen the word "filters" anywhere in the forum config or admin sections, much less enabled any. There is a "censored words" option, but its list is completely empty. Generally speaking, I hate censorship, and especially automated censorship, so I tend to avoid restrictions as much as possible. If someone abuses that, then they get warned, kicked, or banned as appropriate, but by a live human (me) and not a piece of code, so don't worry about it too much, unless you know your users are going to TRY to be jackasses. :-)

I don't have any formal rules, beyond those that apply to xepher.net in general (on the info page at http://xepher.net/info.php ), or that aren't stated when people register for an account. Basically it comes down to "don't be a jackass." If you want more specific, basically the standard stuff... no spam, no porn, no copyright infringement, no illegal content, no hate speech, no harassment, etc.

Here ya go! http://xepher.net/forum/index.php?board=15.0 You should have moderation privileges for that board as well. Let me know if you have any questions or need anything else.

Yes actually, it's that simple. :-) Let me know what you'd like the section of forums to be titled, and I'll set it up.

There should be a way to delete the old host key. I'm not sure with fugu, but generally, there's a file in your home directory, inside the (hidden) .ssh folder called "known_hosts" You can basically just delete this, then it should treat it as a new server, not one that changed, and ask you to accept the new key the first time you connect.

Going camping up in Washington's Olympic National Park tomorrow. I'll be offline through Friday, so my apologies if there are any troubles or help needed during that time.

It looks like your scripts don't work with python3. You can change the shebang to run them with /usr/bin/python2 (which is 2.7) instead of just /usr/bin/python (which is now python 3.3).

As for the wiki... yeah, you should probably be okay with that. I doubt that even if it is compromised, that it's anything horribly malicious, or I probably would've had complaint about it by now.

As for the server name, heh. I always think of server names like code names, and Intel has a long running history of naming CPUs with "dale" in them. Wolfdale, Kentdale, Grantsdale, etc. Then I thought, the new server is a VM in the "cloud" and I should so something with that. Obviously, once that connection was made it was basically impossible NOT to call it "Cloudsdale." Not that I wouldn't probably have found some other way to wedge a pony reference into it if that one hadn't worked so easily. :-)

Good to know!

I don't have IP6 from my own ISP, so my motivation isn't huge on it right now. That said, I do plan to get it working for the server anyway, but it may be a little bit. Really busy for the next few weeks. Feel free to ping me here to remind me though.

The server does have IPv6 networking now. That said, I haven't had a chance to play around with it and experiment, and so DNS and other systems aren't yet set up for it.

Yes, you will see a new SSH server key (and warning about identification) but your private keys should still work. I considered migrating the old server key, but this is an entirely new system, and it was time to generate one of the fancy new elliptical-curve based ones anyway.

Move is complete... at least as far as I can tell. This was a completely new installation on a new, virtual server, with all data migrated by hand. I apologize for the two hours or so of interruptions overnight, but I think most things are working now. I'm sure I'll have overlooked something though, so please let me know if you run into any problems. Email was especially irksome, so it may be best if you post below, just in case it's still wonky.

With the new server, I noticed a lot of spam was being sent via automated wordpress and other things. Apparently at some point I upgraded something and forgot to lock the email back down as I had in the past. I've done that again now, so if you're having errors with your PHP scripts being unable to send mail, you may not have a properly configured .esmtprc file. See this post for details: http://xepher.net/forum/index.php?topic=626.msg6855#msg6855

Also, you will get warnings about the SSH server key having changed. This is expected as it's a new server. Likewise, the cert for SSL email (imap/smtp) and https has changed as well. This is self signed and will generate warnings. This is expected, but obviously don't trust my server with your credit card info and stuff. :-)

So it's been several years since the last server move. In that time, the current datacenter has been bought out twice. Originally, it was "The Planet" then "Softlayer" and now it belongs to IBM. In all that time, hosting prices have come down and bandwidth has gone up, so in the next few days or so, I'm planning to migrate to a new host. I think I can squeeze us into a Linode VPS that will save me $85/month. On paper it should be faster and better in all respects except disk space. I'm going to poke at it for a bit though, and see how it holds up.

When the migration finally happens, it should be "transparent" to end users. Site owners may find themselves locked out for a few hours while a final file sync is done, and MySQL will likely be put in read-only mode for the final few minutes of transfer. I'll try to do all this in off hours as much as possible of course.

I'll post another announcement when things are done, and then you can all yell at me about the things I screwed up or forgot. :-)