If you are seeing this message, you are using MemeStreams on the new server.

Enjoy! Let us know if you spot any problems.

MemeStreams will be moved to a new server sometime tonight. The exact time is in flux. I'll post an update when we fixate the time.

Be sure to take time today to embrace the slowness of the site. Tomorrow it will no longer be an issue.. hopefully.

Update: This has been pushed back until later in the week.

Against my objections, Nick proceeded. At the time he believed, for some reason, that we were going to make more money than we were going to make. We concluded that we would not book the revenue until we actually received money from Google. In some respects it was an experiment - how much would this bring in? As I predicted, it brought in next to nothing. After several years we have not generated enough revenue to reach the minimum amount that prompts Google to cut you a check.

This is a lie. We current have $784.78 owed to us by Google. We have the adsense account configured not to send us payments and hold the money. There is currently no legitimate way to take the revenue since Industrial Memetics isn't setup properly.

It is true that the current level of ad revenue is not enough to fully cover the current operational costs of the site. However, we current have enough money sitting there to cover over a year of the site's operation. We are over-paying for the server and bandwidth that the site is currently running (slowly) on.

This morning I've been working on getting a copy of MemeStreams running on a $38/mo slicehost VM. It's running faster than this one at a third the operational costs.

It's currently available for testing on the memestreams.org domain. Poke at it if you like.. It still needs some work before being ready to move the site to it.

RE: Decius and Rattle have reached an impass

Short and sweet...

Tom is refusing to legitimize operations of this site and the organization that claims to own it. The Industrial Memetics C Corp is basically a shell corporation that has never been setup or managed properly. All efforts I have made to correct this have been met with resistance or refusal. Everything related to MemeStreams is in Tom Cross's personal name. Tom has been paying all expenses out of his own pocket. I have been insisting for several years now that we legitimize Industrial Memetics, create a bank account to pay expenses out of, and keep records of expenses.

Basically, the house has been run improperly... Whenever the topic of "why don't you pay expenses?" has come up, the answer has been the same.. Legitimize operations and I (share expense|inject capital).

After an argument on the street in downtown Bethesda, where I presented Tom with several options for handling this issue, it came down to "take it all over or I'm shutting it down". I refuse to let this site die.

As per our shouted agreement, I'm going to take over the site's operations starting Monday. I don't expect this to be a problem, assuming that Decius doesn't create one. Domain ownership transfer and database sync'ing, etc..

I intend to form a new organization to care for the site as a 501.(c)3 and open source the code.

I know I have not been posting often recently. There are multiple reasons for this. I assure you none of them involve a lack of care for this community and what we've created together. Tom and I have our differences, but he is and always will be central to the soul of this community.... Unless he intends to run away from it.

The social network section of the site had not been updating properly for about two months. It's fixed now.

The display problems with MemeStreams in Firefox 3.0b5 have been resolved.

Firefox 3 is so standards compliant that the non-standard HTML we use over at Industrial Memetics broke it. Someday we will get some standards.

It's been tested so far with Firefox 3, Firefox 2, Safari 3, and IE7. Let me know anyone experiences any further display problems.

You can now preview your posts before submitting them. Please let us know if you run into any problems with this.

Preview added to MemeStreams!

More on the recent search update from the man who implemented it..

Tom posted some quick enhancements I made to Memestreams today. If you are running IE 7 or Firefox 2+ you you might notice your search bar is glowing while browsing Memestreams. You can install MemeStreams as a search provider with one click now in both those browsers as shown below:
Firefox

Internet Explorer

Of course, those of you who regularly search MemeStreams may have a complaint or two about the performance. We're fixing that soon. Its entirely a disk I/O problem and we'll be buying a new server with better storage performance when the new machine comes online in February.

Memestreams supports Firefox/IE's Search bar

I've posted two updates to the site tonight that Acidus wrote a few weeks ago. I'm sorry they didn't make it out sooner but I've been busy with the Christmas holidays and the like.

The first is an updated set of MemeStreams Bookmarklets. You do not have to upgrade to these if you don't want to, but good testers who report problems are always valuable to us. They should work a bit better than the old ones, particularly when selecting text on a page with a bunch of iframes, and we're now back to one peice of cross browser javascript code, which is nice.

The second is that if you're running IE or Safari you might notice your search bar is glowing. You can install MemeStreams as a search provider with one click now in both those browsers.

Of course, those of you who regularly search MemeStreams may have a complaint or two about the performance. We're fixing that soon. Its entirely a disk I/O problem and we'll be buying a new server with better storage performance in a few weeks. Unfortunately I am going out of the country for two weeks so I won't be able to get that done until I return, but the new machine should be online sometime in February.

Thanks Acidus for the nice bits of code!

Yeah! Thanks Billy!

MemeStreams Update: Acidus Badassness

In some circumstance, dates were being broken into multiple lines when viewed with Safari. This problem has been fixed.