Hoppie's ACARS and access control

[Jeroen Hoppenbrouwers]

Just because many people know more than one and discussion tends to be enlightening.

I always had some "jokers" on my ACARS system that like to get themselves a throwaway e-mail account, register a logon code, and start sending offensive and harassing messages to random targets. Some of these targets then contact me to see whether there is anything to be done (they are always very friendly and understanding concerning my role in this). I implemented some traditional weak stoppers with word filters and I block out accounts that have sent stupid stuff but this, obviously, won't break the chain.

I don't have the resources and don't plan to implement hard identity verification on Hoppie's ACARS.

E-mail addresses used to be an okay way to link an ACARS account to a person, but nowadays it is not even close to sufficient. SMS texts would be better, but I don't know about free services that are not selling the phone number on to commercial spammers. Using Microsoft, Google, or Apple oauth services may be a way out, but also introduces maintenance work when they change. The same for using oauth to VATSIM, IVAO, or some other organisation. But it may work.

So, let's discuss.


Hoppie

[Gary Oliver]

Integration with the VATSIM oauth probably isn't as difficult as it sounds when someone creates an acars account going forward, could probably put you in touch with someone that knows it inside out, helped me out during AFV development.

All issues with people being bellends is when messaging VATSIM users after all.