What does this mean in practice?
- If you're looking for a feed that lists hot topics and advanced threads, as well as admin info about lavag.org's health, then continue to follow @lavag. Also, if you want something to go out on the @lavag feed then it needs to link back to a post on lavag.org (eg: if you have a new idea in the NI Idea Exchange, post about it here at lavag.org too, and we'll pick it up from there - feel free to send us a twitter DM if there's something you think we should tweet).
- If you also want to know about all things LabVIEW (new releases, training, cool apps, etc) that aren't on lavag.org then follow @vishots too - it's run by our very own founder Mike, and is chocked-full of LabVIEW goodness.
- To avoid duplication. We're concentrating @lavag on lavag.org content so we don't cross the streams with @vishots. We expect that everyone will follow both feeds, and it gets annoying when you often see duplicate posts coming in from both feeds (it's like that joke someone emailed to you years ago that now everyone in your family emails to you again as they discover the internet).
1 Relf, C. G. et al, "LAVA - LabVIEW Advanced Virtual Architects", 09 February 2010, Forum | Site News | Don't forget to follow @lavag on Twitter ( http://lavag.org/top...vag-on-twitter/ )