PtokaX 0.3.3.1 released... - Page 2
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

PtokaX 0.3.3.1 released...

Started by PPK, 10 June, 2005, 02:21:13

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Dessamator

well, in theory its a feature, ppk seems to have done that deliberately(im unsure), the info is sent to everyone(excluding the person whos logging in) , i think that happens because the person hasnt logged in entirely !

 either way only ppk knows why, i think he said something about it in another thread!
Ignorance is Bliss.

?[-?Genius?-]?

Hi ppl

I detect one error in massmasg

Ex: !massmsg teste

Bot working but if i try

Ex: !massmsg

                         __________________________________________________________________________
                        [__________________________________________________________________________]

               bla bla bla

                         __________________________________________________________________________
                        [__________________________________________________________________________]  

Dont?work, sory my inglish :(

Its a good ptokax, problema is the massmsg :(

[][][] Genius

TTB

Feature request...

!topic    - change topic
!topic                 - view topic


2nd one doesn't exist yet. Could be handy when ppl put links in the topic!

It could be RC10e, but when users sending there message to PMtoOPs, they don't get any respons. It would be nice if there is....

Keep up the good work PPK! I run now 0.3.3.1 without any probs...!
TTB

(? ?.??.-> Admin @ Surfnet hubs <-.??.???)

??????Hawk??????

#28
Quote!topic - view topic

hehehehehe    " Look UP "  do you need a command to show you whats already displayed.   :P  :P


FIne Piece of Work PPK

running error Free this end..

??????Hawk??????

Dessamator

QuoteOriginally posted by •[-•Genius•-]•
Hi ppl

I detect one error in massmasg

Ex: !massmsg teste

Bot working but if i try

Ex: !massmsg

                         __________________________________________________________________________
                        [__________________________________________________________________________]

               bla bla bla

                         __________________________________________________________________________
                        [__________________________________________________________________________]  

Dont?work, sory my inglish :(

Its a good ptokax, problema is the massmsg :(

[][][] Genius

i tried it and it worked perfectly, the only (nice) change i noticed is that it doesnt send the mass to the (sender) besides that everything is fine
Ignorance is Bliss.

TTB

QuoteOriginally posted by ??????Hawk??????
Quote!topic - view topic

hehehehehe    " Look UP "  do you need a command to show you whats already displayed.   :P  :P


FIne Piece of Work PPK

running error Free this end..

??????Hawk??????

You don't get it. First of all, a topic can be longer then can be displayed in the client... Second, if someone put this link in the topic:

"Hi! Check this site: http://frontpage.fok.nl/nieuws/54966 "

(just an example)... then !topic is much easier!! *Click*

Greetz
TTB

(? ?.??.-> Admin @ Surfnet hubs <-.??.???)

bastya_elvtars

It takes approx. 5 lines to script.
Everything could have been anything else and it would have just as much meaning.

Dessamator

hmm, indeed good point, but why not just send a banner? its simpler for those cases , whats the use of adding a big topic if the ppl cant see it ???
Ignorance is Bliss.

TTB

QuoteOriginally posted by Dessamator
hmm, indeed good point, but why not just send a banner? its simpler for those cases , whats the use of adding a big topic if the ppl cant see it ???

A banner mostly can't be changed by users... and has a timer on it... That's why I think this 5 lines  can be added (in my oppinion)

And I request this because it ppl in my hub put links in the topic...
TTB

(? ?.??.-> Admin @ Surfnet hubs <-.??.???)

ConejoDelMal

#34
try this:

sBot = "Topic_Bot"

sTopic = frmHub:GetHubTopic()

function ChatArrival(curUser, sData)
	local s,e,cmd = string.find( sData, "^%b<>%s+(%S+)%s*(%S*)|$" )
	if (cmd=="!stopic") then
	curUser:SendData(sBot, sTopic)
	return 1
	end
end

might not be perfect... I'm still learning how to code :P
Rede-DC Comunidade Portuguesa de DC

Dessamator

#35
change this
curUser:SendData(sBot, sTopic)


to this ::

curUser:SendData(sBot,frmHub:GetHubTopic() )


since ur using the that api only once no need to put it in a variable !
Ignorance is Bliss.

Ubikk

I'm not satistied with 0.3.3.1 because it automaticly disconnects users with rmDC++
I know it's a buggy client, but a lot of my friends are using it, including me. It would be better if this feature could be turned off (allow/not allow users using rmDC++)

Dessamator

well, u have 2 solutions use a script to send them a msg to change their buggy clients, or go back to a previous version of ptokax which allowed that, because that request has been made b4, and if i remember correctly ,
PPK didnt change anything !
Ignorance is Bliss.

Ubikk

#38
atm i use ptokax 0.3.3.0 b17.03 and it works just fine with buggy clients :D
You dont understant... i dont want the users to change their buggy clients... all i want is a way to keep these clients... all the users from my hub are from the same local network and everything works fine even with those clients. If we decide to change them it should be OUR option and not the hubsoft's ... this is just annoying  :(
Wich is the last PtokaX version that allows rmDC++ clients?

Dessamator

hmm, well, no1 forced u to change anything, either way the last version, i think was 17.08 just test it and find out
Ignorance is Bliss.

??????Hawk??????

QuoteOriginally posted by Ubikk
atm i use ptokax 0.3.3.0 b17.03 and it works just fine with buggy clients :D
You dont understant... i dont want the users to change their buggy clients... all i want is a way to keep these clients... all the users from my hub are from the same local network and everything works fine even with those clients. If we decide to change them it should be OUR option and not the hubsoft's  ... this is just annoying  :(
Wich is the last PtokaX version that allows rmDC++ clients?


It is NOT the hubs soft  ..  you should be taking this up with the Creator of Said  " BUGGY Clients "  NOT the creator or Ptokax.

PPK is doing a Great Job here and shouldnt be asked to allow for these clients..


HAWK

PPK

QuoteOriginally posted by Ubikk
It would be better if this feature could be turned off (allow/not allow users using rmDC++)
It would be better to use DC protocol compatible client :P If client send bad command is disconnected, for me is here no other way...
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

TTB

QuoteOriginally posted by [AT]conejodelmal
try this:

sBot = "Topic_Bot"

sTopic = frmHub:GetHubTopic()

function ChatArrival(curUser, sData)
	local s,e,cmd = string.find( sData, "^%b<>%s+(%S+)%s*(%S*)|$" )
	if (cmd=="!stopic") then
	curUser:SendData(sBot, sTopic)
	return 1
	end
end

might not be perfect... I'm still learning how to code :P

Thanx, but I already created that..... ghehe. It is just more finished when it is in the PtokaX release, and not in a script loaded by the scripts section.
TTB

(? ?.??.-> Admin @ Surfnet hubs <-.??.???)

Dessamator

Good Luck convincing PPK to add that m8, :), just bribe him :))
Ignorance is Bliss.

ruspant

I've got a nasty someone who enjoys himself flooding my hub with connections a couple of time a day...
The problem is  ptokax (0.3.3.1 dbg) crashes any time.

[18:33:28] <(+Mastro?di?Chiavi+)> *** Connection flood from IP 151.44.53.79 detected.
[18:33:29] <(+Mastro?di?Chiavi+)> *** Connection flood from IP 151.44.53.79 detected.
[18:33:30] <(+Mastro?di?Chiavi+)> *** Connection flood from IP 151.44.53.79 detected.
[18:33:31] <(+Mastro?di?Chiavi+)> *** Connection flood from IP 151.44.53.79 detected.
[18:33:32] <(+Mastro?di?Chiavi+)> *** Connection flood from IP 151.44.53.79 detected.
[18:33:33] <(+Mastro?di?Chiavi+)> *** Connection flood from IP 151.44.53.79 detected.
[18:33:44] <(+Mastro?di?Chiavi+)> *** Connection flood from IP 151.44.53.79 detected.
[18:33:45] <(+Mastro?di?Chiavi+)> *** Connection flood from IP 151.44.53.79 detected.


I've set a TempBan on "New Connection from same IP" with a rate of 10 on 60 secs.
The problem is that the ip is banned but since the flood continues, the message still comes out and then the hub falls.


---------------------------14/06/2005 18.29.35---------------------------
Exception 'EStackOverflow' in module WS2HELP.dll at 000004B7
Stack overflow

Call stack:
:71A214B7 [WS2HELP.dll]
:71A33D07 [WS2_32.dll]
:71A40F1B [WS2_32.dll]
:018E4427 [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]
:71A39680 [WS2_32.dll]
:018E37E1 [nl_lsp.dll]
:018E443A [nl_lsp.dll]

Main Thread ID = 00000904, Current Thread ID = 00000904
Registers:
EAX = 00000002  CS = 001B  EIP = 71A214B7  Flags = 00010202
EBX = 7C8097DF  SS = 0023  ESP = 00033000    EBP = 00033004
ECX = 006EDDC0  DS = 0023  ESI = FFFFFFFF    FS  = 003B
EDX = 00000014  ES = 0023  EDI = 00033054    GS  = 0000
Code at CS:EIP
56 8D 04 40 C1 E0 04 57 8D 74 08 04 6A 02 8D 46
Stack:
02082778 00033014 71A33D07 006EDDC0 00000568
00000000 00000000 018E443A 00535205 011A9528
005FDB0B 011923C8 00000000 00000000 011E93E4
018E443A FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF

Additional info:
Application Title : PtokaX DC Hub 0.3.3.1 [debug]
Major : 5
Minor : 1
Build : 2600
SP : 2
Type : 1
iJoins: 260, iParts: 209, iLogged: 42
NicklistLen : 659
OplistLen   : 217
MyInfosLen  : 2727
MyInfosTagLen  : 3951
QueueA Size : 1388
QueueA Len : 0
QueueB Size   : 110
QueueB Len   : 0
PQueue Size  : 15
PQueue Len  : 0
HQueueA Size  : 113
HQueueA Len  : 0
HQueueB Size  : 43
HQueueB Len  : 0
OPQueueA Size  : 168
OPQueueA Len  : 0
OPQueueB Size  : 211
OPQueueB Len  : 0
InfoQueue Size  : 153
InfoQueue Len  : 0
OQ-QueueA Size  : 314
OQ-QueueA Len  : 0
OQ-QueueB Size  : 31
OQ-QueueB Len  : 0


Obviously.. if I block the flooding IP with my FW .. the problem ends for a while... at least since my nasty user does not changes his dyn IP...

Any hints ?

Ubikk

QuoteOriginally posted by ??????Hawk??????
QuoteOriginally posted by Ubikk
atm i use ptokax 0.3.3.0 b17.03 and it works just fine with buggy clients :D
You dont understant... i dont want the users to change their buggy clients... all i want is a way to keep these clients... all the users from my hub are from the same local network and everything works fine even with those clients. If we decide to change them it should be OUR option and not the hubsoft's  ... this is just annoying  :(
Wich is the last PtokaX version that allows rmDC++ clients?


It is NOT the hubs soft  ..  you should be taking this up with the Creator of Said  " BUGGY Clients "  NOT the creator or Ptokax.

PPK is doing a Great Job here and shouldnt be asked to allow for these clients..


HAWK

You dont understand :)
What I meant was that it should be the admin's decission if his hub will allow rmDC users or not ! It seems fair to me :(

PPK

QuoteOriginally posted by Ubikk
What I meant was that it should be the admin's decission if his hub will allow rmDC users or not !
PtokaX is DC hub and DC hub is for DC clients, if client is not DC compatible then is not allowed :P
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

Dessamator

indeed, another thing, why does it emulate other dc clients, if it was a true dc client, it wouldnt have to emulate, it could use its own ! in theory
Ignorance is Bliss.

??????Hawk??????

#48
QuotermDC++ discontinued. Forum Closed.
Every good thing has to end.
You can still download rmDC++ on #####.####.###

Greets to all that supported us. All users, sourcecode-providers, phreakers, our families.
We truly loved you all.

Official statement by coder RM. :
I am terribly sorry, but since forum has been hacked, I changed my idea to everything
and rmDC++ project will be stopped forever. I don't have many strength to continue
and to fix all bugs. It's true that I copied everything from StrongDC++ and CZDC++
except some little stuff which is very buggy. So use some alternate client.
 

Thanks for everything!
/ RM. & Loverius

TTB

QuoteOriginally posted by Dessamator
indeed, another thing, why does it emulate other dc clients, if it was a true dc client, it wouldnt have to emulate, it could use its own ! in theory

There you got a good point... I don't even know this client, or the existance...

Regulair users can use DC++... wouldn't be that big problem, would it...
TTB

(? ?.??.-> Admin @ Surfnet hubs <-.??.???)

SMF spam blocked by CleanTalk