Ciao Bimlas bimlas wrote: > > Sorry to fill this thread with my ideas, but I feel like they fit the > title of the topic.
Developing an explicit overview of taggery & linking for TW using examples is a very good idea! I think on the one hand I understood how the concept of "hashtag" came into > being, on the other hand I found a (I think) better use for it. > The widespread use of hashtaggery in social media (Twitter, Instagram, Facebook, Linkedin, Telegram etc) emerged first on Twitter in 2007. At first the experiments using hashtags were met with skepticism. Partly because the simple idea that any of your "content" text AS your "label" identifiers kinda broke some conventions in writing. But hashtags quickly caught on and are a very elegant, compact and are non-duplicating (of fields). Easy to maintain in simple editing. Can support as few or as many as needed. Can be totally part of text flow or just listed in content. I like them. For many, many use cases they are perfectly good and easy and require no special fields creating or maintaining. The one thing that is sometimes an issue is that using hashtags in content text won't always work well for the reader. What I mean is that hashtaggery is both a tagging system AND a recent "*writing convention*". For many academic texts, for instance, it won't work as it breaks their "writers style manuals". > I want to group the recipes to see their properties in a list, e.g. that > if I look at the list of pasta foods, I want to know if that food also > contains sour cream. > Right. Its a good example of leveraging hashtags for TW using alongside other fields. Just FYI the Twitter method of using hashtags makes them ... - case insensitive (both #Buddha & #buddha work the same) - drop irrelevant punctuation to enable full text context integration (e.g. "At that time #Buddha's interest was in ..." is treated as #buddha) Best wishes TT -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/dc6243cf-6c4c-4501-a58c-bde5d90bcf97o%40googlegroups.com.
