fair; what this suggests is putting a small script on static.simile that recognizes exactly the one magic tag, and deletes everything inside the identified span. Then we make sure that runs before xibit or before timeline. This might become a magnet for spammers, but then we can think of something else.
Ben Hyde wrote: > On Feb 15, 2007, at 8:20 AM, David Karger wrote: > >> OK, here's one quick and very dirty suggestion for keeping xibits >> visible to google ... >> <span ex:index-content="true> >> and put anything you want working as google index terms inside >> </span> >> Make exhibit's first action on load be to delete this span from the >> dom >> > > The problem that data rendered by Javascript is invisible is not > owned by exhibit, but rather, Exhibit and Timeline are victims. A > quick and dirty solution along those lines should be bundled in a > separate do-hicky, don't you think? > > _______________________________________________ > General mailing list > [email protected] > http://simile.mit.edu/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
