Hanlon’s razor might be a bit harsh, but it could simply be a PEBKAC issue.

We still haven’t found out how some users are apparently thinking they need 
Nabble, at least not through the GnuCash wiki.

(yes, the wiki page mentions it, but doesn’t encourage its use, and the 
reference is how to avoid problems *if* you use it, certainly not that you have 
to or need to. It also mentions ‘Gmane’ but I don’t know if that is still 
active, or if its users simply manage not to have problems so we don’t hear 
about them.)

I suppose Nabble could be nefarious. Some companies have done much worse and 
with a more intricate scheme.

Regards,
Adrien

> On Jul 7, 2020 w28d189, at 8:53 AM, Greg Feneis <mfen...@gmail.com> wrote:
> 
> Not familiar with Nabble, but what if...
> 
> ...A user gives over their GnuCash email list credentials to Nabble at some
> early stage, thinking they're just doing what's required to be on the list
> (a Nabble-sent email with instructions, like a phishing scheme) and Nabble
> takes that info and alters the user's list settings and perhaps password,
> so it eventually seems to the user that the only way the user can access
> the list is through Nabble?
> 
> For this to work, the Nabble bot would need its own account on the list and
> that account would have to get a notification every time a new user joins
> (don't even know if that's possible), or somehow monitor the list's
> activity just enough to detect when new users join the list.
> 
> Something like this might explain why ppl claim various issues with normal
> list interaction + claim they can only read and work with the list through
> Nabble.

_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to