[Dxspider-support] Dx-World and DxCluster

Sat Feb 11 13:05:15 GMT 2023

Something like that I have started to do. I have sent emails to sysops that are partners of others that there is no way to contact them, asking them if they have data from these nodes and if not, requesting a set/isolate, less traumatic than the set/look, but just as effective.

Half of the requests have received a response, the others are waiting. We will see if there is collaboration.

Kin

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk> En nombre de Ian Maude via Dxspider-support
Enviado el: sábado, 11 de febrero de 2023 13:46
Para: The DXSpider Support list <dxspider-support at tobit.co.uk>
CC: Ian Maude <ijmaude at icloud.com>
Asunto: Re: [Dxspider-support] Dx-World and DxCluster

Back in the early days, if a sysop had an issue and we emailed them but got no answer, we simply locked them out.  It’s amazing how quickly they responded then!  Of course, we were not as interconnected then.

73 Ian

On 11 Feb 2023, at 12:27, Kin via Dxspider-support <dxspider-support at tobit.co.uk> wrote:

Hi,

You are talking about two interrelated issues, one is access to the nodes and the other is the structure and functioning of the network itself. Both can be improved, but there is a lot of work involved.

It is time for the ideas to go a step beyond, with descriptions, pros vs. cons, feasibility, impact, real examples, ...

It is not about user authentication, which has existed for more than two decades, and is hardly being used despite being very easy to implement (see in wiki i.e.), it is about putting protection measures in place, but these measures are not only the responsibility of the developer, we sysops are an active part of the solution and the problem. It is high time to not take a back seat and to assume our responsibility in the management of our node, which is still a part of the network we interact with. 

It is a pity that Bouvet was not activated earlier to give visibility to a problem that has been going on for so long and on which Dirk is still working. Today you can read comments that would have been appreciated when the Community was asked to get more involved with management, complaints and requests for change.

I remember not long ago asking for support for software such as N1MM to incorporate a *password* field associated with each node. The debate was opened and I think only 3 or 4 people seconded the request, ergo the N1MM team dismissed the request. Where were we then?

I've been trying for a month to contact *all* the sysops that use DXSpider and are out of date, and most of the emails I've sent have gone unanswered. Even 3 or 4 of these nodes have simply disappeared, others that do show up on this forum when they have problems are *absent*. But thanks to those who have taken an interest and collaborated, a small change in the network is being achieved. If we sysops ourselves don't get involved, we can't ask much of the developers.

Think that it is not enough just to update our node, we have to be aware of the changes that have been applied, of the new functionalities and of what the developer is asking of us. You have to read the *Change* file that comes with each new build.

Do we want a change? Let's show it.

Kin EA3CV

De: Dxspider-support <dxspider-support-bounces at tobit.co.uk <mailto:dxspider-support-bounces at tobit.co.uk> > En nombre de Iain Philipps via Dxspider-support
Enviado el: sábado, 11 de febrero de 2023 9:58
Para: 'The DXSpider Support list' <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk> >
CC: Iain Philipps <iain.philipps at 77hz.net <mailto:iain.philipps at 77hz.net> >
Asunto: Re: [Dxspider-support] Dx-World and DxCluster
Importancia: Alta

Greetings.

While I do not disagree that there CAN be technology solutions which potentially help, I would (personally) resist such calls. The issue here isn’t software; it is the BEHAVIOUR of the users.

You can not narrowly focus on “fixing Spider” and expect to solve world peace; there are other networks out there (using other software) generating and routing “bad” traffic – how about fixing those first?

It is possible to ameliorate by implementing further controls, but nothing is getting better until someone fixes the root cause – the rebel users.

73 de WR3D

From: Dxspider-support <dxspider-support-bounces at tobit.co.uk> On Behalf Of "Fabián Malnero, EB1TR" via Dxspider-support
Sent: 11 February 2023 08:48
To: The DXSpider Support list <dxspider-support at tobit.co.uk>
Cc: "Fabián Malnero, EB1TR" <fabian at eb1tr.com>; The DXSpider Support list <dxspider-support at dxcluster.org>; Luigi Carlotto IK5ZUK <ik5zuk at tiscali.it>
Subject: Re: [Dxspider-support] Dx-World and DxCluster

Perhaps it would be necessary to think in a more pragmatic way about not "reinventing the wheel".

There are applications that solve all transport needs in an extremely efficient, centralized, secure and scalable way.

Implementations like MQTT, Kafka, EMQX can be more than valid solutions, solidly proven and linked to balancing systems (HAProxy, NGinx, Traeffic, etc.) and some additional services for information verification can be an ideal solution. If all this were open source and deployed in the cloud, we would be talking about an ambitious and modern project.

This, obviously, cannot be done if development is not centralized and we all push towards a common goal. Perhaps the decentralization of nodes is part of the problem.

Greetings.

  _____  

Fabián Malnero, EB1TR
T:  <https://www.twitter.com/eb1tr> @eb1tr
W:  <https://www.eb1tr.com/> EB1TR.com

_______________________________________________
Dxspider-support mailing list
Dxspider-support at tobit.co.uk
https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20230211/869b9e41/attachment.htm>