On Fri, Oct 19, 2012 at 12:32:18PM -0700, we recorded a bogon-computron collision of the <[email protected]> flavor, containing: [...counting spaces in javAPRSSrvr 4.x filters on object names...] > "m/800 t/n e/WE7U-WX o/UP844 /STEAM /" > > So... If using Xastir and filtering against a javAPRSSrvr4.x server > (Firenet-1/2/3), you'll have to move the Object portion to the end, put in a > trailing slash, and count spaces. There should be nine chars total in an > Object name. > > Having to count spaces is ridiculous. It requires the user to have some > familiarity with the APRS spec and/or to read the filter docs VERY carefully. > Existing filter strings that have worked for years may be broken now and > there's no indication of this to the user. I'm talking to Pete to see if > this can't be resolved in a better manner than having every user change their > filter strings.
Ick. That really is a change for the worse. Hope Pete changes it. -- Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM "And, isn't sanity really just a one-trick pony anyway? I mean all you get is one trick, rational thinking, but when you're good and crazy, oooh, oooh, oooh, the sky is the limit!" --- The Tick _______________________________________________ Xastir mailing list [email protected] http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
