[aprssig] (no subject)
steve at dimse.com
Wed Sep 9 21:27:40 EDT 2015
On Sep 9, 2015, at 5:33 PM, Tom via aprssig <aprssig at tapr.org> wrote:
> The DStar data has not stopped flowing in to the APRS IS. My point is it's not flowing out by default to the IGate via the TCPIP connection as it was before. Tom brought up a "software update" and I'm gonna look at that as the smoking gun. That'll be the next check...
> I can run a filter b/*-A/*-B/*-C/*-D and see all the DStar machines fed back to my IGate via the server connection. Before the software update I never had to do this...
> See my point now?
Hmmm... so if I understand...
YOU: I will blindly trust the arbitrarily implemented default filtering controlled by the whims of others
OTHERS: perhaps implemented arbitrary whims (since you haven't given specific calls I can't verify)
YOU: How dare you not do what I want!
Is this not correct? Did you not blindly trust others to implement whatever filtering they chose?
When filtering was proposed on the APRS IS I argued against it, because I felt the users, not the network, should decide what they saw. The argument against it was that the user can specify any filter string they want, and as the APRS IS continued to grow it really became inevitable anyway even if I hadn't turned over management. The reality is a very tiny number of people can do pretty much anything they want in terms of controlling the APRS IS, without public discussion or feedback. I do believe they do things they think are in the public good, but I'd like to see any changes discussed publicly here and some attempt made at consensus building.
But until there is a change in the way it is managed, as a user if you choose to connect to a filtered port you get what they want to feed you as a default. Connect to the unfiltered ports (thankfully still available), explicitly specify what you want to receive in a long and awkward filter string, or stop complaining that others are doing what you allow them to do.
More information about the aprssig