OpenGuides-Dev

openguides-dev@lists.openguides.org

701 discussions

help with some questions? (WikiSym 2006)
by M.B.Gaved 06 Apr '06

06 Apr '06

Dear fellow OG admins, developers, interested parties Mark Gaved and Tom Heath here, we look after the Milton Keynes Open Guide (kindly hosted and sysadmin'd by Christoper Schmidt) we're also PhD students at the Open University. We're thinking of putting in a paper to WikiSym 2006 (http://www.wikisym.org/ws2006/) describing the Open Guides: discussing what people are doing, what we all hope to achieve, how Open Guides differ from other wikis or community information resources. The Open Guides appeal to us as wikis that serve physically co-located communities. This intersects with our PhD research interests, and we'd like to promote Open Guides at the WikiSym conference. We're posting to ask for your help putting this paper together: would you mind answering some questions about the Open Guide you're involved in (as an admin, a content 'editor', general helper etc)? Wed like to gather together peoples thoughts and ideas and write them up with some general information about the Open Guides as the paper; we hope that by doing this we can increase awareness of the Open Guides amongst a worldwide academic audience. We hope this sounds like both a worthwhile and interesting thing to take part in. If you're interested please could you have a go at answering the questions below and mail your answers back to us.... also feel free to get in contact if you've got any other thoughts or comments. Cheers! look forward to hearing from you... Mark and Tom A. Your Open Guide ------------------ 1. How would you describe the Open Guide you work on to somebody who wanted to find out about it? 2. Who is the anticipated audience for your Open Guide? Who are your users right now? 3. What do you see as the purpose of the open guides? (feel free to get philosophical!) e.g. how is it different from other wikis/city guides? 4. Are there rules and regulations users must follow? How about your admin team (e.g. how do you make decisions)? B. Your role in the Open Guide ------------------------------ 1. How did you come to be involved in the Open Guide?- can you tell us what you do? 2. What was your goal when your Open Guide (or your involvement in it) started? What are the current goals? 3. How long do you see yourself being involved in your Guide? 4. Have people used the Guide in any ways you didn't expect? (and has 'vandalism' been a problem?) C. Publicity and outreach ------------------------- 1. Do you publicise your Guide? How? D. Future of the Guide ---------------------- 1. How successful do you think the project is? Which goals have been met? Which remain elusive? 2. How long do you see the project going on for? 3. If someone told you they were planning to start an Open Guide, what advice would you give them? thanks for helping us with this. We'll keep you posted as we progress... please email your answers, thoughts, ideas to Mark: m.b.gaved(a)open.ac.uk or Tom: tom.heath(a)gmail.com

5 4

Re: beg a wee favour, pick your brains for a few minutes?
by Jo Walsh 05 Apr '06

05 Apr '06

dear Mark, all, I was halfway through this long-postponed mail when the responses started flooding through to the list. It only half-applies to me as I don't run a Guide - at least not currently - but here you are. On Wed, Mar 29, 2006 at 10:37:19AM +0100, M.B.Gaved wrote: > 1. How would you describe the Open Guide you work on to somebody who wanted to find > out about it? I'd describe it as a collaborative guide to a city, which everyone is welcome to contribute to. To a geek, i'd say that it was a wiki with spatial metadata, designed to provide a very simple location oriented service. > 2. Who is the anticipated audience for your Open Guide? Who are your > users right now? This doesn't really apply to me, as really I don't run a Guide myself, i only harass other peoples' :) I'd say that i don't anticipate an audience, hope that anyone who's motivated to, should find it as easy as possible to contribute. > 3. What do you see as the purpose of the open guides? (feel free to get > philosophical!) e.g. how is it different from other wikis/city guides? How is it different? It was the first spatial wiki project that i am aware of; a lot of things a bit like it have come along since (wikitravel, wikistreets etc) Its emphasis is "by locals, for locals"; it's not a guide for outsiders, like many city guides and travel guides are. Its emphasis isn't on editorialising or promotion - no commercial affiliation, no advertising, not trying to direct its users. It offers really detailed feeds of its data+metadata, and encourages others to reuse the data, unlike a lot of other spatial annotation sites which are trying to lock their data up in silos and just provide a neat web view that will bring more 'eyeballs' along. > 4. Are there rules and regulations users must follow? How about your > admin team (e.g. how do you make decisions)? Doesn't apply to me... in general i would say, the fewer rules, the fewer bars to contribution. Keeping copyrighted data away is important, to make sure the content in an Open Guide can be freely re-used... > B. Your role in the Open Guide > ------------------------------ > > 1. How did you come to be involved in the Open Guide?- can you tell me > what you do? I got involved back in summer 2002 when the original London Guide was just moving from moinmoin to a complete rewrite in perl by Kate Pugh based on CGI::Wiki. At the time, i was getting really heavily into RDF and playing with spatial annotation / collaborative mapping ideas; Earle, the Guide's originator, and quite a few of our friends picked up the RDF bug from Dan Brickley together. Since then i've found the London and then the Boston guide a really useful resource in my feed aggregation / spatial modelling projects. I did start a San Francisco Guide when i was staying there. I didn't really know the town or have a community of people around me who were into contributing, so the Guide quickly died when i moved away :/ [quick break while reinstating http://sf.openguides.org/ ] > 2. What was your goal when your Open Guide (or your involvement in it) > started? What are the current goals? My personal goal was to get more spatial information modelled in RDF into the world, and to help prove concepts for "collaborative mapping" approaches. My current goals are to help provide a drop-in replacement for some of the Google Maps API dependencies; this involves more talking to people who are working on open source web mapping clients and waiting for someone else to write the silver bullet :) > 3. How long do you see yourself being involved in your Guide? cf the SF guide; it's hard for me to make maps of somewhere that i'm not physically in, all the time. So a Guide is dependent on its owner and most active contributors sticking around. I didn't need to start a Guide when i moved to Boston, because Chris Schmidt was way ahead of me. I've socialised it a bit, but not really practically helped. > D. Future of the Guide > ---------------------- > > 1. How successful do you think the project is? Which goals have been > met? Which remain elusive? I think the amount of things "a bit like" the Open Guide that are now in the world, is an indicator that the project has been a real success. Dom's work on packaging and installability has really helped. I think that's still the main bar to entry, though, and that running a Guide hosted service would help more people get on board. I've wondered about 'writeability' in the interface - to what extent can non-geeks feel empowered to contribute, not scared off by too many form fields, too many potential places to put information. Chris's tweaks to the UI have helped with that a bit. > 3. If someone told you they were planning to start an Open Guide, what > advice would you give them? To get at least 2 other people involved, to keep it alive; to look at what other kinds of sites and location services are around to connect to; to hook up with people making maps of the area, and not rely on "Google Will Provide" too much; at this point, to think hard about mobile (GPRS,wireless portal) interfaces to their Guide to help bring the information nearer to where it describes. sorry this was briefer than most, piles to do, hth :) jo

1 0

Re: Fwd: help with some questions? (WikiSym 2006)
by Christopher Schmidt 05 Apr '06

05 Apr '06

On Tue, Mar 28, 2006 at 04:36:45PM +0100, M.B.Gaved wrote: > A. Your Open Guide > ------------------ > > 1. How would you describe the Open Guide to somebody who wanted to find > out about it? The Open Guide to Boston is an attempt to create a free and open guide to the city of Boston. It is very similar to a number of other services that exist -- CitySearch being the most popular in and around Boston -- but instead of businesses paying for ratings, search results, and reviews, it is something that any user can edit, and any business can add or edit their own listing. > 2. Who is the anticipated audience for your Open Guide? Who are your > users right now? Everyone who uses the web to look up information on their favorite restaurants, bars, or anything else. Everyone who Googles for local search results. Anyone who wants to look up what's near where they are, or what's near something else. Currently the active participating audience is a relatively small, but growing, group of users who I have recruited via online forums about Boston. There are also several people who have come in via Google hits, which is the most common way that people get to the Open Guide to Boston -- approximately 500-600 hits per day come in from users who have googled and found the open Guide to Boston. > 3. What do you see as the purpose of the open guides? (feel free to get > philosophical!) e.g. how is it different from other wikis/city guides? Structured metadata allows for machineprocessable resouroces to take advbantage of knowledge that would not otherwise be available about a city. This can be used to a great advantage in many cases: the Google Maps example that Boston first implemented (and later was integrated into the Open Guides software) is an example of this. There are also numerous other applications of providing a machine-readable version of data that can be exploited from outside the system, rather than "APIs" needing to be built in-system. Full data exports are always the most important aspect of any open data project, and the OpenGuides software provides them in abundance. > 4. Are there rules and regulations users must follow? How about your > admin team (e.g. how do you make decisions)? No rules for users. I basically do my best to maintain useful information without it turning into a spam-filled pit. This means that I let through everything except that which is obviously not neccesary: A location can be described in more ways than "It's infested with crackheads", as one editor wrote. I'm the only admin team there is, so I make the decisions as I see fit, on a case by case basis, when there are problems -- which thus far, there haven't been. > > B. Your role in the Open Guide > ------------------------------ > > 1. How did you come to be involved in the Open Guide?- can you tell me > what you do? Originally, I was introduced to the OpenGuides project via the FOAF project, as both are working to provide machine readable content to the masses -- one about people, the other about places. I took an interest in the project, and set up a Guide for Manchester, NH, but never really did anything with it -- it languished into obscurity. However, when I moved to Boston, I was more successful at getting help from other editors. I'm a developer in the project -- I've made a number of code contributions that increase the usability of the guide. I also maintain and am pretty much the sole admin for the Open Guide to Boston. > 2. What was your goal when your Open Guide (or your involvement in it) > started? What are the current goals? My original Open Guide was designed to provide a data source for an RDF tool I was working with, and to that end I populated it with the content of a MySQL database that I had access to for businesses in Manchester, NH. However, with the Open Guide to Boston, I started it as a solution to people who were looking for a "Boston Wiki" -- something that people could edit for reviews, etc. My current goal is to be better known than CitySearch. > 3. How long do you see yourself being involved in your Guide? For a long time. I've been doing various things with Guides for the past 18 months, and I expect this to continue into the future -- even if it's not as a contributing developer, at least as an admin of the Boston Guide. > 4. Have people used the Guide in any ways you didn't expect? (and has > 'vandalism' been a problem?) Vandalism has not been a problem. There has, to this point, been relatively little use of the guide outside a core group of technically competent users with the best intentions of the Guide in mind. > > C. Publicity and outreach > ------------------------- > > 1. Do you publicise your Guide? How? Not yet. Right now, I'm still working on cleaning up technical kinks with hosting and running of the guide to allow it to be useful to all users: Publicity, until that happens, is more than I'm looking for. However, I do oftentimes link to the guide when I'm talking about someplace I've been, in various communities online. This has resulted in some users finding an interest in the guide simply from these links (rather than from active publicity) and contributing. I am working to establish a tool which is usable for more than just technical users, after which I'll be having conversations with local news organizations about what angle I could possibly use in local publicity -- but until the Guide is generally usable by *viewers* rather than just editors, there isn't much point. > D. Future of the Guide > ---------------------- > > 1. How successful do you think the project is? Which goals have been > met? Which remain elusive? I think that the London Guide has proved to be successful, but I think there are other guides which have proved much less so. It's very easy to have a Guide fail to work out -- you need a dedicated group of editors working for a long time to create a useful resource for the public in order to create something that is not going to be ignored. Boston is very close to passing the tipping point where I could stop babysitting it full time, and still have useful content. Many web visitors are now starting to notice it, and things are definitely improving. I think the key to the Open Guide to Boston success was the ability to build on a dataset which populated much of the metadata for nodes. Typing in tedius addresses and so on is no fun, and the Boston Guide (due to copyright law in the US) was able to build upon Yellow Pages listings to create a database that's usable even without lots of 'real' content. But the real value comes when people start to get interested in editing, and it's not quite there yet. I don't know what the solution is for this -- how did Wikipedia get started? I've never been able to figure out how you get people to rally around a community -- but I'm pretty sure that you can't force it, no matter what. > 2. How long do you see the project going on for? Until it's done. And it's never done. :) > 3. If someone told you they were planning to start an open guide, what > advice would you give them? Find a partner in crime. Never start an Open Guide unless you have at least one other person to edit with you. Otherwise you'll spend all your time working on editing, and none of your time actually enjoying the product of your work. It's better if you can get a whole bunch of people, of course, but I wouldn't hold my breath for that eventuality. -- Christopher Schmidt Web Developer

2 1

[Fwd: Re: a first shot at some questions....]
by IvorW 05 Apr '06

05 Apr '06

This was originally posted as a private reply, but really there's no reason why I shouldn't go public with it. -------- Original Message -------- Subject: Re: a first shot at some questions.... Date: Mon, 03 Apr 2006 22:15:09 +0100 From: Ivor Williams To: M.B.Gaved <M.B.Gaved(a)open.ac.uk>, t.heath(a)open.ac.uk References: <E0FEA5DF00E59E409F90C854A1B45BAA6B600C(a)EPPING-EVS1.open.ac.uk> > >A. Your Open Guide >------------------ > >1. How would you describe the Open Guide to somebody who wanted to find out about it? > > My answer to this question depends on how technical or otherwise, the person is. For the completely non-technical, I describe the Guide as a website with lots of reviews of pubs and restaurants, and useful information about anything in London. For the more technical, I use the word wiki, and explain (if they don't know the concept) that anyone can contribute. >2. Who is the anticipated audience for your Open Guide? Who are your users right now? > > I think it's quite a broad portfolio. The initial intention was targetting the guide at geeks. As such, the initial subjects we were covering were ones of interest to geeks, particularly London.pm. However, I saw the guide as having a much broader scope, and started writing pages that could be of interest to anybody, and the content has developed along those lines. In terms of the current user base, I think it's quite diverse. I keep running into people who've already heard of OpenGuides. I have personally had feedback from CAMRA, from an employee of London Transport, and from trade unionists finding my page on the West London Trades Union Club. >3. What do you see as the purpose of the open guides? (feel free to get philosophical!) e.g. how is it different from other wikis/city guides? > > I think the primary function is to inform. A second aim is to be objective. A third is to provide a vehicle for feedback, and rapid updating by the virtual community that exists on account of their discovering OpenGuides. Other city guides tend to be commercial, pandering to the wishes of paying sponsors, and of limited use and limited objectivity. Also, because "anyone can edit", I feel comfortable that I can visit an establishment listed in the guide, and update it with my findings. Compared with other wikis, the structured metadata is what sets OpenGuides apart. In particular, the geodata can be used for finding distances and plotting points on maps. I've not seen other wikis that can do this. >4. Are there rules and regulations users must follow? How about your admin team (e.g. how do you make decisions)? > > My rules for contributors are set down in the page "Wiki Etiquette", which was entirely my own wording. Common sense is the principle that applies - I translated this into the Wiki Etiquette page so that others would have a reference point where we could all agree on our policy. This page has had to evolve over time, with changes in software, changes in copyright and licensing policy, and in the light of various kinds of abuse and attacks. When it comes to admin decisions, the "common sense" rule applies. If we're unsure we'll probably make a change (or change the node back) but keeping the controvertial revision available. Something that's blatant spam or offensive, will just get deleted. More recently, I have been keeping an admin log page for deletes, so that we have a record, including recording the IP addresses of any spammers and suchlike. I tend to email the other admins directly (not via a list) for matters which are sensitive, e.g. a security hole I discovered early on. >B. Your role in the Open Guide >------------------------------ > >1. How did you come to be involved in the Open Guide?- can you tell me what you do? > > This was through London Perl Mongers. I was one of the 3 founders of the first guide - involved both as a major contributor, and as a software developer. In terms of roles, I do pretty much everything bar the hosting. I don't have access to the box OGLondon is running on, but I run a mirrored copy on a couple of my machines. >2. What was your goal when your Open Guide (or your involvement in it) started? What are the current goals? > > The original goal of a useful guide to London that people can edit and keep up to date, has definitely been met, and is continuing to be met. The goal of sharing data and building a community of mutually supporting websites is being met, albeit from a specialist niche. I'm finding it difficult to separate the goals of OGLondon and the goals of the OpenGuides project as a whole, since I am involved with the big picture, including software development. In many ways, I now think it's important to keep a standard common code base that all guides can share. It's tempting to look at ways of improving the software for London, but this feels wrong to me. Many of the developments that have happened, have been applied to individual guides, leading to a fragmented picture - this has created work for developers merging these patches in order for everyone to get the benefit. >3. How long do you see yourself being involved in your Guide? > > This is one of my main hobbies and loves. I don't see myself losing interest. >4. Have people used the Guide in any ways you didn't expect? (and has 'vandalism' been a problem?) > > The most extreme case of vandalism was in September 2005, when Brazilian hackers managed to trash the London database. This took us offline for a few weeks, and lost some updates. We also get regular spam attacks, though we are looking at ways of combatting them in software. Version history has been a godsend here, as we can always see what was there before, and indeed "diff" the content. The spam situation for London is under control, as enough admins watch the recent changes, and spam gets deleted fairly promptly. We've also had salesmen creating pages for their own establishments - restaurants, aromatherapy, a chain of car showrooms, even TimeOut magazine! What happens is that we tend to blockquote what has been written as "Some anonymous contributor, presumably from XYZ, wrote the following:" and add that one of our regular contributors will review the place properly. There was also the skating wars - two rival skate clubs, one of which was defacing the entry for the other, which resulted in a ban. And there was the pedicabs page, where someone keeps changing some of the web links so they don't work. I tend to spot edits like that, and reach for the "delete" and file the IP address in the Admin Log. I don't actually have the power to ban anybody, but I would drop a mail to those that do. >C. Publicity and outreach >------------------------- > >1. Do you publicise your Guide? How? > > Word of mouth, and internet. We don't have any paid advertising, as this is not only a potential waste of money, but would also probably upset a few of our community as getting commercial. We had the same reaction when we tried running Google ads. Sometimes if I'm in the mood in a pub or restaurant, I'll mention to the proprietor that I have a website that does reviews, and will be writing one when I get home. This has got me a free drink on a couple of occasions. >D. Future of the Guide >---------------------- > >1. How successful do you think the project is? Which goals have been met? Which remain elusive? > > In terms of London, I think the goal of a useful guide has been met. Our coverage is patchy, but that is due to the distribution of our contributors' homes and workplaces. Over time this will improve. I think we have built a successful community of contributors. In terms of Google search league ladders, we are well up there. For OpenGuides as a whole, there is still much to do. Much of this is in the realm of software development, but we could also do more in terms of spreading the word across the globe. There are many cities that have potential for a guide - it's just a matter of people who are there linking up to create guides. >2. How long do you see the project going on for? > > I see this as a continuous process, rather than a project with a defined finishing line. >3. If someone told you they were planning to start an open guide, what advice would you give them? > > How serious about it are you? How much time have you got to put into it? This is going to occupy you if you want to get it off the ground. How many people have you got to help as contributors? You need a minimum of 3 (counting yourself), ideally between 3 and 12. Once you have launched, you will hopefully acquire new contributors. How long before you can get to 100 pages? Set this as your first milestone. Don't try and launch until you've got 100 pages. If you are talking about siphoning content from somewhere else, that's different - you may be able to launch straight away. If this is the case, double check things like copyright and terms of use. Don't worry too much about the technicalities of hosting - we can offer that to you as a service if you need it (but if you want to host your own guide, that's OK too). What we can't do for you is: (a) be there at your city and (b) have all the local knowledge to write detailed pages. Have a good look at the other guides that are out there, and make use of the best ideas (in your mind). Join the dev list if you are running a guide. That's the best way of finding out what else is happening to OpenGuides elsewhere. Also hang out on IRC, where you'll find plenty of others running guides.

1 0

Templating
by Earle Martin 05 Apr '06

05 Apr '06

Talking to Chris Schmidt on IRC at the moment about macros. He's just coded up @INCLUDE [[Foo]] to include the whole content of "Foo". I was saying that it would be nice to have templates much the way MediaWiki does. He said: "Just specify that @TEMPLATE (Template:Fillin|Variable1|Variable2) will load ?id=Template:Fillin, and replace Variable1 with the content of variable1". As I understand it you could just pass any number of variables into a template call, effectively giving each template its own @_. He continued: "The biggest problem is picking a syntax that won't cause other problems. Most of the current macros use [[ ]] but that results in it being treated as a link so you get lots of extra backlinks." I commented that we could use {{}} for templates instead - again, following the MediaWiki model - and avoid this. We could also drop the "@TEMPLATE" prefix which would be unnecessary. I'd actually like to deprecate all the @THING prefixes if at all possible and use {{}} markup. Here are some suggestions: * {{index_link}} = "@INDEX_LINK [[Cat or Loc You're Looking At]]", likewise for {{index_list}}. * {{index_link|Category Foo}} = "@INDEX_LINK [[Category Foo]]" variable being passed in as mentioned above. index_link and index_list are obviously reserved words as builtins so you shouldn't be able to define templates called that. Thoughts? -- Earle Martin http://downlode.org/ http://purl.org/net/earlemartin/

2 1

Fwd: [openguides-commits] r753 - in trunk: . lib lib/OpenGuides t]
by Earle Martin 05 Apr '06

05 Apr '06

I realized tonight that OpenGuides and OpenGuides::RDF needed a bit of refactoring to accommodate different feed types (since CGI::Wiki can do Atom now - see http://www.earth.li/pipermail/cgi-wiki-dev/2006q2/000246.html), so I went ahead and did it. ----- Forwarded message from svnadmin(a)urchin.earth.li ----- [snip headers] Author: earle Date: 2006-04-05 02:26:00 +0100 (Wed, 05 Apr 2006) New Revision: 753 Added: trunk/lib/OpenGuides/Feed.pm Modified: trunk/Build.PL trunk/MANIFEST trunk/PREREQUISITES trunk/lib/OpenGuides.pm trunk/lib/OpenGuides/RDF.pm trunk/t/22_rss_modwiki.t trunk/wiki.cgi Log: New module, OpenGuides::Feed: this extracts the stuff formerly in OpenGuides::RDF (as sub make_recentchanges_rss) that was invoking CGI::Wiki::Plugin::RSS::ModWiki, and replaces it with a single make_feed method that can be used for any feed format, including Atom (using the new CGI::Wiki::Plugin::Atom). Changes to OpenGuides.pm and wiki.cgi are to use this new module appropriately. [snip diffs] ----- End forwarded message ----- You can see the new code running here. * http://openguides.org/testing/index.cgi?action=rc;format=rss * http://openguides.org/testing/index.cgi?action=rc;format=atom Tests pass (namely t/22_rss_modwiki.t), but there could probably be more - I'm a bit knackered and about to head off to bed, so I think I've used up all my Perl for the evening. Cheers, Earle. -- Earle Martin http://downlode.org/ http://purl.org/net/earlemartin/

1 0

more mod_perl fixes...
by Christopher Schmidt 04 Apr '06

04 Apr '06

Ran into a couple more mod_perl problems today. I think that the patch at http://crschmidt.net/openguides/mod_perl.exit.patch will get rid of all the 'exit 0's in the code that make mod_perl choke. -- Christopher Schmidt Web Developer

2 1

[Fwd: CPAN Upload: I/IV/IVORW/CGI-Wiki-Plugin-SpamMonkey-0.01.tar.gz]
by IvorW 03 Apr '06

03 Apr '06

I could do with some help. Reading the docs for SpamMonkey, it seems that Simon Cozens is not really wanting to support it. What I'm doing should work, but is failing to detect spam, as in t/003_spam.t (test 6 is todo). I've installed Mail::SpamAssassin, which has set up the etc directory, but still no joy. Thanks in advance, Ivor. -------- Original Message -------- Subject: CPAN Upload: I/IV/IVORW/CGI-Wiki-Plugin-SpamMonkey-0.01.tar.gz Date: Sat, 1 Apr 2006 14:59:32 +0200 From: PAUSE <upload(a)pause.perl.org> Reply-To: 48mn-wuei(a)spamex.com To: Ivor Williams <6bed-rgew(a)spamex.com> The uploaded file CGI-Wiki-Plugin-SpamMonkey-0.01.tar.gz has entered CPAN as file: $CPAN/authors/id/I/IV/IVORW/CGI-Wiki-Plugin-SpamMonkey-0.01.tar.gz size: 11858 bytes md5: bd4cf6c8938a3f6431c37567a703980b No action is required on your part Request entered by: IVORW (Ivor Williams) Request entered on: Sat, 01 Apr 2006 12:42:50 GMT Request completed: Sat, 01 Apr 2006 12:59:32 GMT Thanks, -- paused, v460

2 1

Fw: [nycwireless] Mobile-izing! Weeklong Cell Phone "Shoot-Out" at 347 W 16 St (9th Ave)
by Jo Walsh 27 Mar '06

27 Mar '06

Date: Sun, 26 Mar 2006 13:40:03 -0800 (PST) From: Rob Kelley <robjkelley(a)yahoo.com> To: nycwireless(a)lists.nycwireless.net Subject: [nycwireless] Mobile-izing! Weeklong Cell Phone "Shoot-Out" at 347 W 16 St (9th Ave) Precedence: list from http://wikiStreets.com/ (our new name!) --- If you saw [http://wikistreets.com/tiki-read_article.php?articleId=126|today's article ] [http://wikistreets.com/tiki-read_article.php?mode=mobile&articleId=126|(mob… ], you know something shady's going on in the shadow of proud Google's NY offices. A landlord is apparently using a suspicious fire as an excuse to sell a rent-stabilized building as vacant and free-market while the tenants are displaced. And he's using Craiglist to do it. We don't like it, we expect you don't like it, and our cellphones have cameras... __Let's turn the camera's eye on 347 W 16 St.__ Your mission, mobile user, is to go to 347 W 16 St, take a picture of the building with your cellphone, and email it to us at: !!!::[mailto:347@10011.info|__347@10011.info__ ]:: (10011.info is the same as wikiStreets, but it's easier to type into a cellphone.) Each photo we get we'll upload and post to [http://flickr.com/photos/92044402@N00/| Flickr ] with a unique tag. The goal is 100 pics by this Friday, March 31st. We'll be showing our support for the tenants and highlighting this building as a battleground in the war for a culturally rich, economically diverse neighborhood. Rob P.S. PDAs, Laptops, and crazy Linux-modded beasts are also welcome! -- NYCwireless - http://www.nycwireless.net/ Un/Subscribe: http://lists.nycwireless.net/mailman/listinfo/nycwireless/ Archives: http://lists.nycwireless.net/pipermail/nycwireless/ ----- End forwarded message ----- -- ghug is my email archiving bot. if you see it cc'd on this email, please leave it cc'd, that will help me a lot. http://frot.org/ghug

2 2

SpamMonkey
by IvorW 24 Mar '06

24 Mar '06

This could be useful to OpenGuides. -----Original Message----- From: Simon Cozens [mailto:simon@simon-cozens.org] Sent: 23 March 2006 23:28 To: london.pm Subject: [upload(a)pause.perl.org: CPAN Upload:S/SI/SIMON/SpamMonkey-0.02.tar.gz] Since you asked so nicely. Doesn't include the Email::Received stuff, (and therefore RBL checking) of course; look for that coming when it finally passes SpamAssassin's tests. It's still useful; here's a generic spam-trapped comment feature for Maypole: use SpamMonkey; my $sm = SpamMonkey->new; $sm->ready(); sub add_comment :Exported { my ($self, $r, $thing) = @_; my $res = $sm->test($r->params->{content}); if ($res->is_spam) { return $self->error("I think you're a spammer, because your comment: ". join("\n", $res->describe_hits)); } $thing->add_to_comments({ author=> $r->params->{author}, url => $r->params->{url}, content => $r->params->{content}, posted => Time::Piece->new, }); $r->template("view"); } Simon ----- Forwarded message from PAUSE <upload(a)pause.perl.org> ----- From: PAUSE <upload(a)pause.perl.org> Subject: CPAN Upload: S/SI/SIMON/SpamMonkey-0.02.tar.gz To: Simon Cozens <simon(a)simon-cozens.org> Reply-To: cpan-testers(a)perl.org The uploaded file SpamMonkey-0.02.tar.gz has entered CPAN as file: $CPAN/authors/id/S/SI/SIMON/SpamMonkey-0.02.tar.gz size: 6858 bytes md5: 2994361baa44bbadd50248d83471542a No action is required on your part Request entered by: SIMON (Simon Cozens) Request entered on: Thu, 23 Mar 2006 23:22:54 GMT Request completed: Thu, 23 Mar 2006 23:24:15 GMT Thanks, -- paused, v460 ----- End forwarded message ----- -- He is no fool who gives what he cannot keep to gain what he cannot lose.

1 0

← Newer
1
...
26
27
28
29
30
31
32
...
71
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

OpenGuides-Dev