<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
How about</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
2. Login every user to my node and use their IP address when spotting.</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div class="elementToProof" style="font-family: Aptos, Aptos_EmbeddedFont, Aptos_MSFontService, Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
If they're connecting to your node, they'll probably have an IP address.</div>
<div id="appendonsend"></div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Dxspider-support <dxspider-support-bounces@tobit.co.uk> on behalf of Gregor Surmann via Dxspider-support <dxspider-support@tobit.co.uk><br>
<b>Sent:</b> Sunday, March 9, 2025 8:35 PM<br>
<b>To:</b> The DXSpider Support list <dxspider-support@tobit.co.uk><br>
<b>Cc:</b> Gregor Surmann <gs@funil.de><br>
<b>Subject:</b> [Dxspider-support] Webclusters, the second</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Hello!<br>
<br>
I am running a big web cluster, too. I have the following options:<br>
<br>
<br>
1. Spot "by" and "ip" (current solution), having spots rejected because of <br>
verify. Nodes will drop the spots and someone here will complain ;)<br>
<br>
2. Login every user to my node (previous solution), having many spotters <br>
with the same IP (of the web server). Someone here will complain ;)<br>
<br>
3. Fake the whole login and spot process with a fake node, fake PC messages <br>
etc. This could work, but why should I take this path?<br>
<br>
4. Whatever different solution appears...<br>
<br>
<br>
73 de Gregor, DO5SSB<br>
<br>
-- <br>
| Gregor 'SinusPL' Surmann | gs@funil.de | Will work for bandwidth |<br>
|--------------------------------------------------------------------------|<br>
| The UNIX Guru`s view of Sex: | <a href="http://www.sinuspl.net">
www.sinuspl.net</a> |<br>
| unzip; strip; touch; finger; mount; fsck; more; yes; umount; sleep |<br>
<br>
_______________________________________________<br>
Dxspider-support mailing list<br>
Dxspider-support@tobit.co.uk<br>
<a href="https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support">https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support</a><br>
</div>
</span></font></div>
</body>
</html>