#tantekthe point is, you might eventually transfer that number to Google Voice etc. and then it is no longer strictly a mobile number, however, because that information is not visible whereever you're publishing, you're not likely to notice that the information is out of date and thus it rots.
#tantekso no, you don't really want to bother wasting time giving it an invisible type
#tantekor if the type matters to you, then it deserves to be visible
#tantekand then the likelihood that you'll fix it goes way up
#chlI'd recommend pinning your hosts file so that microformats.org points to the (mt) IP. that's the only way to *really* be sure you're seeing what you'll see when DNS moves.
#chl@tantek yeah, i'm not implying we shoudl switch dns back over. just saying that changing your hosts file is a better way to test than using mt.microformats.org, in case there's any stuff that's wired to just microformats.org in the code.
#tantekchl - for those of us that aren't entire sure what you mean by "pinning your hosts file" - let's be more specific - it sounded like you wanted someone to edit the hosts file on the old server
#chlthat article shows how to do it for windows, os x, and linux.
#chl(sorry, i do this all the freaking time, i forgot not everybody does :) )
#chlif if you add the line I put above to the hosts file on your local machine, and do the flush cache thing in os x, then restart your browser, it will be have *exactly* as if you'd switched actual DNS. so that's why it's the best way to test.
Soopaman joined the channel
#tantekchl - add to the start or end of the hosts file?