The biggest hurdle to overcome here is that Twitter only allows a certain number of updates per hour. If the site DM’ed every user when new events came up, it would easily exceed that limit.

A current workaround is to use the advanced search feature of twitter which allows you to search by location: http://search.twitter.com/advanced

Filter for tweets from sf4answers which have the hashtags #sf4 (and/or #ssf4 for when it comes out) and within the radius of the area you want to get event notifications for.

You can then subscribe to that in an RSS reader.

Of course, you can get filtered RSS feeds from the site itself (as well as calendar feeds), so its a little roundabout.

Great idea. How exactly would you want to navigate such a tag index? Do you simply want it to be a list of tags, with maybe some stats about how many items it is associated with (along with a way to filter it) or are there better, easier ways to navigate these tags?

It’s a good idea, but there are two points to be made around this which I don’t have good solutions to right now:

- Most events (even in a series) don’t happen on a consistent freqnecy, so “every Friday”, “every other Friday”, might not always apply (or, am I missing the point on this, there are more regular events like this which outweigh the number of one-offs on the site?)

- If the events don’t occur anymore, people ^usually aren’t responsible for removing the event from the calendar (this is based on other systems I’ve observed).

I’m not sure how to alleviate the concerns above and make it as easy as possible for the community.

Any suggestions/followup along these lines would be greatly appreciated.

Update 7/5/2010:

Just switching to planned, will be a definite feature.

Based on the feedback, we think that having separate pages are better than having one page with all the terms.

However, we also feel that there should be a separate section.

Under consideration for the names are:

- Terminology
- Glossary
- Dictionary

Anyone could add one and the restrictions on editing would be somewhat low.

Agreed. The stylesheets for the WYSIWYG editor just do not match, and they most definitely should. There should be no (or at least as little) discrepancy as possible between the editor experience and what is shown.