The regexes can be pulled into an application at runtime, or at any
other time by humans, machines, and perhaps beasts.

For now I am happy to take the submitted noise-tweet candidates and
create the regexes from them.

I’m thinking of expanding the filtering to include application names
(the “source” from the status). Like “foursquare.” But then we get
into an area where many Twitter users will want to see those, so this
brings to mind client features where users can select which of these
repository filters to use.

Reply via email to