I think somewhere less obvious (like under ones user profile) there should be a place to check a box to enable "advanced user options." And if that is checked then such abnormal things would be accepted?
Not sure how feasible/easy that sort of thing is for Chris to code though.
I think that is actually the best idea. Adding a flag to each user (default false) and using it to enable those things (checks that were present before!) should not be that difficult. At least it should be easier than adding an extra step in the workflow.
Rob
On 10 Apr 2019, at 17:12, Rob Janssen pe1chl@amsat.org wrote:
I think somewhere less obvious (like under ones user profile) there should be a place to check a box to enable "advanced user options." And if that is checked then such abnormal things would be accepted?
Not sure how feasible/easy that sort of thing is for Chris to code though.
I think that is actually the best idea. Adding a flag to each user (default false) and using it to enable those things (checks that were present before!) should not be that difficult. At least it should be easier than adding an extra step in the workflow.
and who would be responsible for turning the flag on/off? The user themselves? In which case aren’t we back to square one (with some/most users at least).
or perhaps a coordinator? Do they want the extra responsibility?
Chris
Rob
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
I would propose an alternate solution. Since the number of such valid gateways is so very few, perhaps it would work well enough that someone must *be* a coordinator to set up a gateway whose outside-world address is in network 44. On the rare occasion that such a gateway is needed, the ham needing it can simply contact his coordinator and they can enter it. It only takes a few seconds to do. - Brian
On Wed, Apr 10, 2019 at 06:12:12PM +0200, Rob Janssen wrote:
I think somewhere less obvious (like under ones user profile) there should be a place to check a box to enable "advanced user options." And if that is checked then such abnormal things would be accepted?
Not sure how feasible/easy that sort of thing is for Chris to code though.
I think that is actually the best idea. Adding a flag to each user (default false) and using it to enable those things (checks that were present before!) should not be that difficult. At least it should be easier than adding an extra step in the workflow.
Rob
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
If we talk about updating the gateway: Wouldn't it be useful to also have a way to send messages to users or coordinators? I know their mail addresses are private, but sometimes such contacts are needed. A simple message box where one could pick a subnet owner or coordinator...
Marius, YO2LOJ
On 11.04.2019 00:28, Brian Kantor wrote:
I would propose an alternate solution. Since the number of such valid gateways is so very few, perhaps it would work well enough that someone must *be* a coordinator to set up a gateway whose outside-world address is in network 44. On the rare occasion that such a gateway is needed, the ham needing it can simply contact his coordinator and they can enter it. It only takes a few seconds to do.
- Brian
Yes Marius. I think that would be a very nice enhancement to the portal.
Right now, people can use the 'contact us' and it evenually reaches the right person, but because the forwarding is done manually, it can take a while. - Brian
On Thu, Apr 11, 2019 at 01:23:40AM +0300, Marius Petrescu wrote:
If we talk about updating the gateway: Wouldn't it be useful to also have a way to send messages to users or coordinators? I know their mail addresses are private, but sometimes such contacts are needed. A simple message box where one could pick a subnet owner or coordinator...
Marius, YO2LOJ
On 11.04.2019 00:28, Brian Kantor wrote:
I would propose an alternate solution. Since the number of such valid gateways is so very few, perhaps it would work well enough that someone must *be* a coordinator to set up a gateway whose outside-world address is in network 44. On the rare occasion that such a gateway is needed, the ham needing it can simply contact his coordinator and they can enter it. It only takes a few seconds to do.
- Brian
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
+1
Michael, N6MEF
-----Original Message----- From: 44Net 44net-bounces+n6mef=mefox.org@mailman.ampr.org On Behalf Of Brian Kantor Sent: Wednesday, April 10, 2019 3:53 PM To: AMPRNet working group 44net@mailman.ampr.org Subject: Re: [44net] RIP problems?
Yes Marius. I think that would be a very nice enhancement to the portal.
Right now, people can use the 'contact us' and it evenually reaches the right person, but because the forwarding is done manually, it can take a while. - Brian
On Thu, Apr 11, 2019 at 01:23:40AM +0300, Marius Petrescu wrote:
If we talk about updating the gateway: Wouldn't it be useful to also have a way to send messages to users or coordinators? I know their mail addresses are private, but sometimes such contacts are needed. A simple message box where one could pick a subnet owner or coordinator...
Marius, YO2LOJ
On 11.04.2019 00:28, Brian Kantor wrote:
I would propose an alternate solution. Since the number of such valid gateways is so very few, perhaps it would work well enough that someone must *be* a coordinator to set up a gateway whose outside-world address is in network 44. On the rare occasion that such a gateway is needed, the ham needing it can simply contact his coordinator and they can enter it. It only takes a few seconds to do.
- Brian
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
-
Brian Kantor -
G1FEF -
Marius Petrescu -
Michael Fox - N6MEF -
Rob Janssen