Noise Board

also make IRE not require login thx.

Grady, that's a massive job. Security's built into the whole thing and taking it away is a huge amount of work.

8[

i know this is the meta board (as of today, basically), but should this have maybe been posted on noize?

Sure, by all means post a link to it.

also if noize is separated in such a way that it doesn't harm the rest of ilx with its hostile javascript (and i have no idea what this entails) couldn't it just run olde ilx code? noize-specific traffic is surely way smaller than ile/ilx or would that not make a difference?

Well, it is a question of load - google hitting it and so on, all load continually growing; it might cope now, it might not tomorrow. This is less of a problem if it's isolated and would only affect the noise board, but it would affect all of ILX, even if the new code has no problems at all. In database traffic alone, the old code ran 250x as many database queries as the current code does, so it's a significant increase even without noise accounting for the majority of ILX.

Also, you'd need to either ignore the last few months, or write code to convert from the current database schema to the old schema.

In addition, I dunno what Graham's position is on using it - I wasn't paying attention at the time, but I read something along the lines of being licensed to use it as was, but not for anything else. I'm not sure about this, though.

ok, thanks for the quick answers. i don't really know what i'm talking about so you probably don't need to listen to me.

(ps can i pls be idiot thread repository mod)

Don't ask me! Pash is your man for admins.

I've noticed you're proposing a rewrite of ILX. I'd like to politely ask that you stick to the condition Andrew agreed to when I left ILX and let him continue using my code:

http://ilx.wh3rd.net/thread.php?msgid=3711185#3715181

"but not to make anything derived from it public or install it anywhere else"

^^^ graham

If the nb was going to run somewhere else, could we get a db dump of it? (at least 5th time I'm asking this; ignored before)

I wasn't really suggesting it need to run somewhere else, physically, if you know what I mean. I've no objection to you getting a copy of the database (as long as it's cleaned of email addresses), but I dunno what others think.

I mean, other than email addresses, you've got access to the database anyway, were you to screen scrape ILX, so I don't see what the harm would be.

i woudl not mind option 2. i keep boards open in diff tabs anyway and you already have to relogin so it wouldn't be that big a deal to relogin twice.

I have nothing constructive to add to this debate but the first few posts on that thread Tombot linked to are still classic.

I'd like NB to stay a part of ILX as much as possible, it's part of what makes it ILX. What we're really talking about here is just putting in domain-level security for the rest of the boards from it. Either of the options above are based on this -- noise might have a new domain, or a subdomain of ilx (like noise.ilxor.com, f'rinstance), but it'll still run on this server.

As far as option 1 goes, I'm open to anything. If someone does want to write an ILX-like NB, we can run just about anything on this server. We've got Tomcat for java on port 80, and Apache for everything else on 8080. The limiting factor here is performance. I looked into just using the old code for this, but it really isn't up to the job, licence issues aside. That's not to dump on it too much -- it does plenty of smart things, like cacheing new answers (which is vital on a query that can take up to 2 minutes!) -- just to say that I can't see it and real ILX co-existing very well.

how hard would it be if the noise bord were living elsewhere (even if it is on the same server) to tweak the current code to give us what we want? i mean is the problem that everything you do effects the entire site or what?

jhøshea, that's what I'm suggesting! Option 2!

ha duh me

omg that thread with its attendant hissyfit, lol

eagerly awaiting blueski's input on this thread.

aka Cheetos© fingers aka Dorito© breath.

just get rid of admin powers

google hitting it and so on

taking this comment out of context, and I'm not sure what jon thinks, but nb should be excluded from google indexing. se spiders are for gue55 p4pers and o1nkt invite threads.

also there is an nb enemy list and these people should not be nb admins. please refer to thread with mantiger image for details.

lastly thanks in advance for providing the inmates with keys to a wing of this fine asylum.

i have nothing to add except Keith and Stet many thanks for being concerned about this.

it's really great that you'd consider doing this.

on the other hand, it could be opening up a collosal can of worms.

if you do #2, which is feeling more likely... you're going to need a second database instance. totally separation from top to bottom. different connection pools. separated sessions. separated cookies. (paths could help you there possibly.)

you could easily deploy the same code base for both. it'd be relatively easy to move the nb specific data over i'm thinking right?

i would just factor out the html stripping code to where you could apply different implementors. even if you open the nb up some, i'm thinking we'll still want some protection. maybe the others will disagree but let's face it, much worse things are possible than anything that might've been done in the past. do we really want it totally wide open to all html?

also, as far as user accounts go, it's not everybody as admins, but anybody... so iow, make some of the main regs admins and then from there they can grant as appropriate. meanwhile, the separate db keeps admin privileges strictly on the nb site because there are no shared accounts, etc.

i really know little of the architecture, but... maybe there's some half-sense in what i wrote.
m.

"Frito Lay R&D"? weak

i like NB for Leonardo and CIO so would be sorry to see it go

msp: you're entirely right, and all that's exactly what I am considering doing. Except for the bit about protection against some HTML - as I don't want to get into having two separate code bases (all this is if option 2 is what's wanted), because that will just become a management nightmare, unless it were to be clear that they were two completely separate sites on different evolutionary paths (hence option 1). I think paths will be enough to prevent one site accessing another's cookies. If someone knows different, please let me know.

as long as the noize board can keep up the comedic genius that is the "rejected beardo techno song titles" thread, all right with the world.

do we really want it totally wide open to all html?

Well what if this kind of configuration were programatic:

$allowedposttags = array ('address' => array (), 'a' => array ('href' => array (), 'title' => array (), 'rel' => array (), 'rev' => array (), 'name' => array ()), 'abbr' => array ('title' => array ()), 'acronym' => array ('title' => array ()), 'b' => array (), 'big' => array (), 'blockquote' => array ('cite' => array ()), 'br' => array (), 'button' => array ('disabled' => array (), 'name' => array (), 'type' => array (), 'value' => array ()), 'caption' => array ('align' => array ()), 'code' => array (), 'col' => array ('align' => array (), 'char' => array (), 'charoff' => array (), 'span' => array (), 'valign' => array (), 'width' => array ()), 'del' => array ('datetime' => array ()), 'dd' => array (), 'div' => array ('align' => array ()), 'dl' => array (), 'dt' => array (), 'em' => array (), 'fieldset' => array (), 'font' => array ('color' => array (), 'face' => array (), 'size' => array ()), 'form' => array ('action' => array (), 'accept' => array (), 'accept-charset' => array (), 'enctype' => array (), 'method' => array (), 'name' => array (), 'target' => array ()), 'h1' => array ('align' => array ()), 'h2' => array ('align' => array ()), 'h3' => array ('align' => array ()), 'h4' => array ('align' => array ()), 'h5' => array ('align' => array ()), 'h6' => array ('align' => array ()), 'hr' => array ('align' => array (), 'noshade' => array (), 'size' => array (), 'width' => array ()), 'i' => array (), 'img' => array ('alt' => array (), 'align' => array (), 'border' => array (), 'height' => array (), 'hspace' => array (), 'longdesc' => array (), 'vspace' => array (), 'src' => array (), 'width' => array ()), 'ins' => array ('datetime' => array (), 'cite' => array ()), 'kbd' => array (), 'label' => array ('for' => array ()), 'legend' => array ('align' => array ()), 'li' => array (), 'p' => array ('align' => array ()), 'pre' => array ('width' => array ()), 'q' => array ('cite' => array ()), 's' => array (), 'strike' => array (), 'strong' => array (), 'sub' => array (), 'sup' => array (), 'table' => array ('align' => array (), 'bgcolor' => array (), 'border' => array (), 'cellpadding' => array (), 'cellspacing' => array (), 'rules' => array (), 'summary' => array (), 'width' => array ()), 'tbody' => array ('align' => array (), 'char' => array (), 'charoff' => array (), 'valign' => array ()), 'td' => array ('abbr' => array (), 'align' => array (), 'axis' => array (), 'bgcolor' => array (), 'char' => array (), 'charoff' => array (), 'colspan' => array (), 'headers' => array (), 'height' => array (), 'nowrap' => array (), 'rowspan' => array (), 'scope' => array (), 'valign' => array (), 'width' => array ()), 'textarea' => array ('cols' => array (), 'rows' => array (), 'disabled' => array (), 'name' => array (), 'readonly' => array ()), 'tfoot' => array ('align' => array (), 'char' => array (), 'charoff' => array (), 'valign' => array ()), 'th' => array ('abbr' => array (), 'align' => array (), 'axis' => array (), 'bgcolor' => array (), 'char' => array (), 'charoff' => array (), 'colspan' => array (), 'headers' => array (), 'height' => array (), 'nowrap' => array (), 'rowspan' => array (), 'scope' => array (), 'valign' => array (), 'width' => array ()), 'thead' => array ('align' => array (), 'char' => array (), 'charoff' => array (), 'valign' => array ()), 'title' => array (), 'tr' => array ('align' => array (), 'bgcolor' => array (), 'char' => array (), 'charoff' => array (), 'valign' => array ()), 'tt' => array (), 'u' => array (), 'ul' => array (), 'ol' => array (), 'var' => array () );
$allowedtags = array ('a' => array ('href' => array (), 'title' => array ()), 'abbr' => array ('title' => array ()), 'acronym' => array ('title' => array ()), 'b' => array (), 'blockquote' => array ('cite' => array ()),
// 'br' => array(),
'code' => array (),
// 'del' => array('datetime' => array()),
// 'dd' => array(),
// 'dl' => array(),
// 'dt' => array(),
'em' => array (), 'i' => array (),
// 'ins' => array('datetime' => array(), 'cite' => array()),
// 'li' => array(),
// 'ol' => array(),
// 'p' => array(),
// 'q' => array(),

etc

so there's a different set of allowed html

I was just wandering around the town there, thinking that if it were possible, I could put an hook in that allows you to write something in some sort of scripting language to intercept and process input, so for a noise version, I could turn off the escaping of HTML and site admins could edit the processing script. It's fairly easy to do, but what language it could be in is dependent on what's available in Java, and I don't think a Perl interpreter is. A Python one definitely is, though. Much better language too.

However, this is a long way down the line.

jruby yum yum

I wouldn't be getting too excited about a scripting language that lets you write one function and one function only! Looking like:

public String processInput(String input)

public Fun addFun(Fun input)

10 PRINT "HAI GUISE"
20 PRINT "THANKING U"
30 GOTO 10

Jon, I don't know whether you're asking for the database so as you can code against it or not, but it seems to be caught up in a mess of people not sure about the copyright status of stuff, right now.

If it's coding against you're looking for, then all you need is the schema, with tables and associated indices, which has no such six-month-long discussion attached to it. I built this to let me build ILX2. The data itself came right at the end. If it is your intention to write a board, can you let us know, as it obviously affects this discussion.

ILX2 Database Schema

Obviously, I may make changes to this schema in time, so if you are going to use it, let me know and I'll keep you up to date with the changes.

i like NB for Leonardo and CIO so would be sorry to see it go

-- blueski, Tuesday, June 12, 2007 11:59 PM (Yesterday) Bookmark Link

*takes notes*

Jon, I don't know whether you're asking for the database so as you can code against it or not, but it seems to be caught up in a mess of people not sure about the copyright status of stuff, right now.

Well how is this any different than you taking it over from Andrew?

If I was going to code against something, I'd want to be hosting it myself :/

is it really wise to let aspie jon have any power at all?

maybe we can install a button for "Convert Simple Social Cues to ASPIEcode"

can we have embeds?

THEY AINT GIVIN U SHIT

because ASK CHAKI is really where it's at!

sonned by Ask Chaki

nah they aint givin me shit either