[aprssig] Multi control station situational awareness - How's this supposed to work?

[chiefsfan2 at cox.net]

Since you had a analog landline phone still working that would be a reason to bring back some phone patches like we used to have. And now you can run a BBS on a rasp pi computer which makes for great portability and low power consumption
On Dec 3, 2019, 17:01 -0600, Gregg Wonderly <gregg at wonderly.org>, wrote:
> Yaesu.’s Fusion system provides the ability to send text, audio and photo data to a repeater’s HRI-100 connected computer system. That has power implications, but not much different from bulletins requiring someone to keep sending the for newly connected stations to see.
>
> I like the fusion solution since it decouples the information fanout from net control. There are pluses and minuses for any solution since they are based on the technology used. As Bob said, even the basic function of bulletins is not consistently implemented.
>
> Gregg
>
> Sent from my iPhone
>
> > On Dec 3, 2019, at 4:06 PM, Robert Bruninga <bruninga at usna.edu> wrote:
> >
> > A log of checkins could look like this:
> >
> > BLN1STNLOG:@1030
> > Checkins:ASDFAS,WERR,ERETT,ASDFGG,ZXVCXCZ,ASDFFF,WEQRW,ZXCVVV,SDFDFG,WERTW
> > ER,WRTRYY
> >
> > Each time it changes, update the list and the time. Kepe the same BLN1
> > and it will overwrite the older copy. Or increment the BLN# and have past
> > logs in the Bulleting list.
> >
> > Bob
> >
> >
> > -----Original Message-----
> > From: aprssig <aprssig-bounces at lists.tapr.org> On Behalf Of Greg Troxel
> > Sent: Tuesday, December 3, 2019 3:40 PM
> > To: Greg D <ko6th.greg at gmail.com>
> > Cc: TAPR APRS Mailing List <aprssig at lists.tapr.org>
> > Subject: Re: [aprssig] Multi control station situational awareness - How's
> > this supposed to work?
> >
> > I would urge you to step back and consider your requirements, think about
> > the protocol that will be used at a high level, and then figure out how to
> > use specific techniques to implement that protocol.
> >
> > If what you want to do is publish infomration about status of particular
> > places, then APRS probably is the best fit.
> >
> > If you are trying to synchronize the list of checked-in stations among N
> > NCS stations, then I think you want some sort of database sync protocol
> > which is going to send messages among the participants, and you may or may
> > not want to carry that over APRS.
> >
> > I think you implied this, but from the "train like you'll fight" I would
> > suggest using the over-the-air sync all the time, and not use any
> > direct-to-APRS-IS internet-based injection. Gatewaying to APRS-IS is
> > great for others to probably be able to see what's up, but I think you
> > should plan on no internet, and thus operate that way routinely, because
> > otherwise you are likely to be depending on it more then you think.
> >
> > ALl of this is going to push you to protocols that are very terse and push
> > just the data, with all formatting and UI local. This means writing a
> > local implementation of the UI for the protocol.
> >
> > 73 de n1dam
> >
> >
> >
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at lists.tapr.org
> > http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
> >
> > _______________________________________________
> > aprssig mailing list
> > aprssig at lists.tapr.org
> > http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
>
> _______________________________________________
> aprssig mailing list
> aprssig at lists.tapr.org
> http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20191203/271e9c00/attachment.html>