SoylentNews

Currently deep in working on getting the first rehash (MP2 slashcode) release put together. lithium got rebuilt and is now on the MP2 release. Since this upgrade is disruptive anyone, we decided to go full-in and put in a migration to MySQL cluster as well; which will require some code changes for Search, but otherwise was mostly a drop in upgrade.

I'm just going to leave this here ...

Server: Apache/2.2.29 (Unix) DAV/2 mod_apreq2-20090110/2.8.0 mod_perl/2.0.8 Perl/v5.20.1
X-Powered-By: slashcode 15.01
X-Fry: I'm never gonna get used to the thirty-first century. Caffeinated bacon?

and just say I'm a certifiable madman.

So, it appears we have quite a community of DF players here at SN, and enough I think to warrent getting a succession game going. For those who are unaware, succession games are when one plays for one year (Spring to Spring traditionally), then passes off the fort to the next player in line. Boatmurdered is perhaps the most famous of the succession games ever done, though there are others, such as Battlefailed, Failcannon, and .

I'm interested in doing this, especially since it requires relatively little in infrastructure to setup. I'd like to do it on SN itself, perhaps either with a shared account as journals, or just creating a new section on the site. Obviously I'm going to have to tweak the codebase to allow images, and it gives a way to help build our community out. So, if we do this, here's what we need to decide:

• What version of DF? 2012, or wait for the new release

• What type of biome?

• Any mods?

And probably some other stuff. I've been playing a fort which is at war with the elves, and I find its quite a bit of fun since you regularly get seiged, and requires that we have a badass military to survive (and there are ways, even in stock, to get military training to work and start churning out Lords and Masters relatively quickly.

I recommend we apply bugfixes to the raws such as elven treecap diplomacy, and human merchants, which seriously helps getting the supplies we need. I've had good look with Accelerated Modest Mod for bug fixes, and preventing FPS death even in crud hardware so its my vote if we just don't go vanilla. I also recommend we also use all the DFHack fixes (the patrol bug one is almost essential).

Post below if you're interested, turn list is first come, first serve, but you can sign up for a second turn after your first (likely necessary since I expect only 5-6 players). Regular updates, and timely turns are a must as well. Beyond that, the sky is the limit.

Managed to kick out the first draft of the bylaws, they're here on the wiki http://wiki.soylentnews.org/wiki/Incorporation/Bylaws for anyone who wishes to take a look. I need to fill out some more paperwork, then submit the entirity of the mess to a lawyer. I got a few recommendations, so mostly now is lawyer shopping.

I realize this is a bit of a longshot, and I don't want to run a QA on the site for this, but does anyone have a lead on a lawyer in New Hampshire to help me through incorporation? I'm also looking for a CPA, but those are relatively easiler to locate.

I've looked at various services such as Harbor Compliance, but they don't seem to be legal help, just document filing services ...

Wooo, that nearly killed me to finish it. It's going living at 20:00 UTC (4PM EST), which is the start of our peak hours. We'll be revising it based on community feedback and if other important points come up as time goes on.

Of course, words means only as much as the actions taken behind them, but I think we've been relatively consistent in meeting the goals I outlined. Here's a small sneak preview for those who read my journal til the whole thing goes live

Statement of Purpose

Our aim is to stand in stalwart opposition to these trends. We will be the best site for independent, not-for-profit journalism on the internet, where ideas and free discussion can take place without external needs overshadowing the community.

So ... I've recently gotten back into minecraft, and figured that perhaps there are other MC players here at SN, so I wanted to know if there was enough interest to setup a MC server in general. I'd probably use CraftBukkit, and I'm open to running mods if others are interesting. Leave a message below if you'd be interested.

Mods I'd like to run:
  * Traincraft
  * Railcraft
  * Mystcraft (useful for getting new ores without having to reset maps; age creation would be restricted to admins though; mystcraft is a server hog).

Leave your thoughts below.

Since we've got a fair number of complaints about us running too many site news articles, I'm going to condemn this to my journal, then link it next time we *do* post something about the site. For a large portion of today (4/16), SoylentNews users had issues with commenting, and moderation was completely hosed. This was due to a backend change; we shifted the site behind a loadbalancer in preparation of bringing up a new frontend and give us considerably more redundancy and latitude with working with the backend.

This change had been setup on dev for the last week with us testing it to see what (if anything) broken, and it was discussed and signed off by all of the staff. Last night, I flipped the nodebalancer to connect to production instead of dev, then changed the DNS A record for the site to point at the loadbalancer.

I stayed up for several hours at this point to ensure nothing odd was going on, and satisfied that the world would keep spinning, I went to bed. What I found though was I broke the formkeys system. Slash knows about the X-Forwarded-By header, a mechanism for when a site is behind a proxy on how to relay client IP information (this mechanism was already used by both varnish and nginx), however, for security reasons, we strip out the XFF header from inbound connections unless its on a specific whitelist. On both dev and production, we had whitelisted the nodebalancer to pass this header in properly.

Or so we thought. Linode's documentation doesn't mention, but the IP address listed in the admin interface is *not* the IP used to connect to the site; instead it uses a special internal IP address which isn't listed or documented anywhere. Our security precautions stripped out the X-Forwarded-By header, and made it appear that all inbound users were coming from the same IP. This wasn't noticed on dev as slash ignores the formkeys system for admins, and the few of us beating on it with non-admin accounts weren't able to do enough abuse to trigger the formkey limiters.

Our peak hours are generally evenings EDT, which means the low traffic at night wasn't enough to trip it either (or at least no one on IRC poked me about it, nor were there any bugs on it on our github page. However, once traffic started picking up, users began to clobber each other, commenting broke, and the site went to straight to hell. When I got up, debugging efforts were underway, but it took considerable time to understand the cause of the breakage; simply reverting LBing wasn't an easy fix since we'd still have to wait for DNS to propagate and we needed the load balancer anyway. After a eureka moment, we were able to locate the correct internal IPs, and whitelist them, which got the site partially functional again. (we have informed Linode about this, and they said our comments are on its way to the appropriate teams; hopefully no other site will ever have this same problem).

The last remaining item was SSL; we had originally opted out of terminating SSL on the loadbalancer, prefering to do it on the nginx instance, so Port 443 was set to TCP loadbalancing. This had the same effect as there is no way for us to see the inbound IP (I had assumed it would do something like NAT to make connections appear like they were coming from the same place). The fix was utlimately installing the SSL certificate on the load balancer, then modifying varnish to look for the X-Forwarded-Proto header to know if a connection was SSL or not. I'm not hugely happy about this as it means wiretapping would be possible between the load balancer and the node, but until we have a better system for handling SSL, there isn't a lot we can do about it.

As always, leave comments below, and I'll leave my two cents.

Now that I've had some time to clear my head, I want to expand on my original feelings. I'm pissed off about this, and my temper flared through on the original post. I'm leaving it as is because I'm not going to edit it to make myself look better, and because it sums up my feelings pretty succinctly. How would you feel if something you worked on under the promise of building the best site for a community was regularly and routinely causing corporate firewalls and IDS systems to go off like crazy?

You'd be pissed. Had we known about this behaviour in advance, it would have been disabled at golive or in a point release, and a minor note would have gone up about it. Instead, I found out because we were tripping a user's firewall causing the site to get autoblocked. I realize some people feel this is acceptable behaviour, but a website should *never* trigger IDS or appear malicious in any way. Given the current state of NSA/GCHQ wiretapping and such, it means that anything tripping these types of systems is going to be looked at suspiciously to say the least. I'm not inherently against such a feature (IRC networks check for proxying for instance), but its clearly detailed in the MOTD of basically every network that does it.

There wasn't a single thing in the FAQ that suggested it, and a Google search against the other site didn't pop something up that dedicated what was being done; just a small note that some proxies were being blocked. Had the stock FAQ file, or documentation, or anything detailed this behaviour, while I might still have thought it wrong, at least I wouldn't have gotten upset about it. I knew that there was proxy scanning code in slashcode, but all the vars in the database were set to off; as I discovered, they're ignored leading me to write a master off switch in the underlying scanning function.

Perhaps in total, this isn't a big deal, but it felt like a slap in the face. I know I have a temper, and I've been working to keep it under wraps (something easier said than done, but nothing worthwhile is ever easy). CmdrTaco himself commented on this on hackernews and I've written a reply to him about it. Slashdot did what they felt was necessary to stop spam on their site, and by 2008, slashcode only really existed for slashdot itself; other slash sites run on their own branches of older code. Right or wrong, such behaviour should be clearly documented, as its not something you expect, and can (and has) caused issues to users and concerns due to lack of communication. Transparency isn't easy, but I have found its the only way to have a truly healthy community. Perhaps you disagree. I'll respond to any comments or criticisms left below.

We're testing a new configuration between the site and the database. There may be unexpected issues with the site while we're testing. Keep calm and carry on.