Slashdot Mirror

All of the parallel programming paradigms we've seen so far just hurt my head in a 'but but that's not the Right Thing' kind of way. I'm not sure what the Right Thing to do is, but I'm sure multithreading ain't it, and even Haskell strikes me as overcomplicated for what ought to be a very simple solution if we just looked at it a little differently.

I think we need immutability and instruction-level parallelism at least, just to get halfway sane, and then a few new abstractions on top of that. The idea of 'views' is something that keeps circling around my head, and I'm trying to tease my brain into explaining what it means on my Livejournal - but as a first cut, I think Occam and Carl Hewitt's 'Ether' (and to a lesser extent, the Japanese Fifth Generation Project's KL-1) were heading toward the right track.

Of course, I don't have a formal CS background, so I may be just gibbering incoherently, but words are cheap and this stuff sure is fun to dream about.

There's status.livejournal.org but it's incredibly slow right now.

There's not a lot of social networking projects that are open source or free to the communities. Every single one seems to be some ad revenue money grubbing scheme anyway. You have PeopleAggregator and maybe NovaShare though the latter doesn't really support degrees of separation searching.

From the announcement:
STEP 1: Go to http://www.test.dev.livejournal.org/ . Make an account. Probably need to change it to paid so you can make styles/etc.
So to be able to help them test their security, you have to pay them? Or am I missing something?

You are not supposed to hack away on http://www.livejournal.com/

They provide a sandbox: http://www.test.dev.livejournal.org/

LiveJournal

Was created by Brad to help his family keep in touch, and at the same time be as user-friendly as possible. Has a bunch of GUI apps that allow posting without ever touching the Web interface.

"Friends" aggregators allows the users to read the stream of postings of the friends they choose to add, so no need to browse 15 journals at once to see whether they added anything new over the past few days.

E-mail notifications, commenting, pictures, etc.

And it's open source.

It's back up. Unless you're on Filet MIgnon or Madcow (like myself.)

LiveJournal's offsite status page is status.livejournal.org.

The code that runs LiveJournal is open source. It's not that much of a pain to deploy, and when it's working, it's the most powerful I've seen. Many stand alone clients for posting, all kinds of things. Set one up, use it as your own weblog, host your friends' weblogs.

b2evo This is what I would recommend people check out first.
BBlog (requires PHP version 4.1 or greater & MySQL version 3.23 or greater)
Bit 5 Blog
blosxom (only need ability to run CGI scripts)
drupal.org (mySQL or similar required)
LiveJournal.org
MyPHPblog/Simplog (seems to require MySQL would have to download to be sure.)
Nucleus (requires PHP version 4.0.6 or higher and access to a MySQL database version 3.23.38 or higher)
Pivot (only php required)
pLog (requires PHP 4.1.x or higher and MySQL 3.1.x or higher)
Scoop (requires Apache with mod_perl and mySQL)
TikiWiki (requires PHP 4.1+ and MySQL. Very powerful software.)
WordPress (requires PHP version 4.1 or greater and MySQL version 3.23.23 or greater.)

Livejournal.org hosts the codebase (GPL'd) used on Livejournal.com and other clone sites.

Problem #1: when people contribute, they do so on corporate sites. Epinions. Livejournal. Even Photo.net is a perfect example of the clustering that happens, as is mp3.com...

I agree with the premise but disagree with LiveJournal as an example of the problem - at any time I choose, I can slurp my journal in a number of different formats - HTML, RSS, plain text, etc.. All it takes is the motivation. The majority of the LiveJournal code is Licensed under the GPL and all of it is open for review (though the site specific enhancements can only be used on development servers). Anyone who feels the desire can download and install the code to set up their own journal site.

you can try it here: livejournal test server

You get the full privileges of a paid account to test out which is better than opening a free account on the main servers to test.

Only disadvantage with the test server is your account could be purged anytime but that shouldn't be a worry if you're just testing how things work.

enjoy :)

After all, LiveJournal is completely Open Source. Subscription only gives you added features, but the free version does not even have ad banners. The site is completely funded by subscriptions and donations. A few other sites have spun off thanks to the freely available code, including DeadJournal.

Here's an XML file detailing all of the clusters. It's a little hard to read, but it works.

In a fix to LiveJournal's HTML sanitizer, we can see that one of the developers perhaps wasn't happy with the standard of commenting used when another developer was forced to fill a regex with lots of \s* to make sure the sanitizer didn't let through anything which might cause IE's over-zealous parser to execute some JavaScript.

"god IE is a fucking piece of shit" might not be the most innocent comment in the world, but at least it puts the blame in the right place...

Check out the rest of the code for other sprinklings of code necessary due to the amazing flexibility IE offers. Oh yes.

In a fix to LiveJournal's HTML sanitizer, we can see that one of the developers perhaps wasn't happy with the standard of commenting used when another developer was forced to fill a regex with lots of \s* to make sure the sanitizer didn't let through anything which might cause IE's over-zealous parser to execute some JavaScript.

"god IE is a fucking piece of shit" might not be the most innocent comment in the world, but at least it puts the blame in the right place...

Check out the rest of the code for other sprinklings of code necessary due to the amazing flexibility IE offers. Oh yes.

In a fix to LiveJournal's HTML sanitizer, we can see that one of the developers perhaps wasn't happy with the standard of commenting used when another developer was forced to fill a regex with lots of \s* to make sure the sanitizer didn't let through anything which might cause IE's over-zealous parser to execute some JavaScript.

"god IE is a fucking piece of shit" might not be the most innocent comment in the world, but at least it puts the blame in the right place...

Check out the rest of the code for other sprinklings of code necessary due to the amazing flexibility IE offers. Oh yes.