Slashdot Mirror

It was in 2003 when he was revamping his forums. He sent out an email to members that was similar to what he posted here but slightly different, including what you're describing:

If you post something and it gets deleted, we'll use a cookie to actually continue to show you your own post. We just don't show it to anyone else in the world. 9 times out of 10, you won't even know your post has been deleted. If you delete cookies or go to another computer, you may catch us, but most of the time people don't even notice that their post was removed.

It was Joel first. I, too, remember reading about it many years ago. (Jeff's post is just a year old.) Here's a mention of it from 2004:

http://joi.ito.com/weblog/2004/12/20/happy-trolls.html

(See comment #2)

[later]

Aha! I knew I had it. Way back when, he was revamping his community, and he, briefly, made it so you had to sign up to get an email to hear when it would be launched. I still have that email. It is entitled "Building Communities with Software" but it differs slightly from this. According to Google there is exactly one copy of the original email on the WWW and here it is.

If you post something and it gets deleted, we'll use a cookie to actually continue to show you your own post. We just don't show it to anyone else in the world. 9 times out of 10, you won't even know your post has been deleted. If you delete cookies or go to another computer, you may catch us, but most of the time people don't even notice that their post was removed.

"DIY" and software do not appear together often enough.

I would teach them how to create their own personal "apps" using Squeak. Use Nebraska to collaborate and share in class. Look for a few techies to help.

To get stared, try Sugar on a Stick and look at Etoys, a specialized subset of Squeak. (You use Squeak to create Etoys.)

http://www.squeak.org/

http://squeakland.org/

http://www.sugarlabs.org/

Nebraska: http://wiki.squeak.org/squeak/1356

Wider range of info: http://squeak.zwiki.org/SqueakNotes

A recent class at University of Illinois: https://agora.cs.illinois.edu/display/cs598rej/Spring+2009;jsessionid=3BA508D972A809064DC117DBDF7C36C8

Not only is a good wiki a fantastic tool for this, I've got one for you that's zero-installation and zero-cost. Zwiki is a robust and proven wiki engine and I'm still offering http://zwiki.org/FreeHosting. Later, export or zsync the content to your own Zope server if you wish. I use it all the time to organize information and and document procedures for my clients. The lightweight page hierarchy, email integration and integrated issue tracker come in handy. If you'd like further tips on this, ask me in #zwiki on irc.freenode.net.

That would be Zwiki. Eg: http://zwiki.org/FrontPage/contents#PageHierarchy. This was partly influenced by Drupal's books.

http://zwiki.org/ZwikiTracker is easy and effective. See the links demonstrating three different views (use login x, x for the last). Also works in Plone.

Set up a wiki, set the privileges so that only the site's owners can edit and add pages and presto... the simplest Content Management System. Works really well for small companies where you train one or two persons to be in charge of the site.

Use something like ZWiki that has a big application server behind it, so you can integrate other tools (shop, blogs, forum) and let the site grow as needed.

For Zope, try Zwiki. With Zwiki under Plone (which runs under Zope; it is like an onion),which will take care of access control, at an overhead cost, though. I haven't played with it much in a year or so, and I cannot recall how fine grained the access controls are (I think it is wiki-level, not page-level access). For page level / group access, you would probably need multiple wikis, although you'd need to check the docs for certain. You can always just use a Plone site instead of a wiki (Plone offers full WYSIWYG editing, access control, tracking of revisions, rollback, etc). Zwiki - Access Control and membership. Plone also has some docs on zwiki, link to a plone/zwiki demo.

Zope plus Plone - if you are looking for a content management system, or Zwiki if you are looking for a wiki solution, or learn Python and roll your own inside of Zope's Management Interface (ZMI).

Before you know it you will have dynamic content coming out of your ears - and you won't have to muck about with a relational database at all (and the ZODB scales better anyway from my experience).

Easily done - build the Wiki on top of an app server that handles the security for you.

Without wanting to flog a dead horse, Zope will do this for you. Ooh look - a Zope-based wiki. Plays nicely on top of Plone, too.

I belive http://umiststudents.com/ runs on Plone. Obviously http://plone.org does too. Neither are ugly looking by any stretch any both very usable. A lot of effort has gone into Plone to make it look "plain" - that is clean & simple to use. That's surprisingly hard with such a full featured CMS. Much easy to make one cluttered.

Setup's much quicker & simpler than the apache/php/mysql combo.There's a plone installer now that even sets everything up for you. That's your webserver, app server, content management system and database all in one.

As for Zope sites looking the same - just look at the various sites in this post. I'd say Postnuke sites all look far more alike to be honest.

Bruce Eckel's site http://www.mindview.net/ runs on standard Zope. That looks OK to me. Some UK Home Office sites too eg http://www.drugs.gov.uk/Home. All look pretty professional.

Zope is excellent at wiki's too. The whole "page is an object" model fits wikis very well. Zwiki http://www.zwiki.org is one of the best I've seen,

Zope, Plone, and Zwiki are all progressing at a fair pace. If you haven't tried in a while it's worth having another look. I think one of the main problems is that it's just so different to other solutions out there. I'm used to J2EE development. From JSPs it's reasonably simple to pick up ASP & PHP. Zope requires a bit more of a mindshift.

Please ignore the last paragraph of my last comment.

. o O ( Preview button...oh, yeah! )

You could probably build something on top of Zope (which comes with a ZWiki component), and might find gZigZag interesting.

Tinderbox, and Userland's products, though not open/free, are two other platforms to build on or learn from.

If you are going the Wiki route, I suggest you evaluate ZWiki. Zwiki is a Zope product that adds Wiki capabilities to Zope. this gives you the flexibility of a Wiki with the power of the Zope framework.

Zope's excellent. It's really very simple - a web server, app server and database all rolled into one. Everything can be managed via the browser.

As the above poster says, there are loads of free products that plug into it do do whatever you want. In your case it sounds as if Zwiki would be ideal. If you wanted to go further then Zope also has a complete content management product you can use, called the CMF.

We've used Zwiki for an intranet and it's been extremely useful. Lets you have a set of searchable web pages can be easily edited without users having to know HTML.

To go all out in the Zope world I'd suggest a CMF Portal, potentially one based on Plone