Page 2 of 2

Posted: Sun Jan 15, 2006 10:40 pm
by epoximator
the server assumes that if a client version is marked active, but not marked official, then it must be outdated. this is of course silly since test versions should not be marked official. will be fixed on next update

Posted: Sun Jan 15, 2006 10:49 pm
by su8zer0
Ok, got it. Thanks for the reply. Oh, by the way, if my client is just a small notify app, should i put it @ Clients Wiki page?

Posted: Sun Jan 15, 2006 10:52 pm
by epoximator
yes you should register it here

Posted: Tue Jan 17, 2006 1:28 pm
by su8zer0
Ok, i've registered it.
One more question: If i register client at the server after message/notify has been sent will the client still receive it? I.e. msg was sent @13:00, the client logged in and registered @14:00. Will it still receive the message sent @13:00?

Posted: Tue Jan 17, 2006 2:32 pm
by epoximator
if i understand your question correctly then no.

so when your client logs on to the server it should check whether there are any new messages/notifies or not with NOTIFY before it PUSH and goes into listening mode.

i found a bug in NOTIFYGET btw... will be fixed on next update

Posted: Tue Jan 17, 2006 7:57 pm
by su8zer0
Ok, that's exactly what i meant. Thanks.

Posted: Tue May 02, 2006 10:39 pm
by su8zer0
Hey, it's me again. I've at last managed to finish my systray client (well, almost :P ), but i've recently steppen upon little problem. I'm behind NAT, and when i register my client to receive new notifications, after few minutes (i don't know exactly how many) the "connection" is timed-out. I've tried to PING the api in shorter intervals (as written in wiki), and also i'm using "nat=1" option when authing to api, but it doesn't help. Can you possibly tell me what i'm doing wrong ?

Posted: Wed May 03, 2006 9:40 am
by epoximator
"nat=1" is only for checking whether you are behind a nat router or not. it won't do anything else. how long intervals do you use? my router has a 5 min time-out period, meaning I have to ping before that, like 4.9 sec.

Posted: Wed May 03, 2006 9:54 am
by su8zer0
I've used 5 min. intervals. I guess i just have to make it shorter then. But will it not be too much load on server when let's say 100 clients start sending PINGs every 4 mins. ? (that's ofcourse only a prediction, there is a possibility that nobody will use my proggie :P ).
Oh, and one more thing. To detect NAT (according to wiki) i should compare port used by client and port returned by AUTH. But what if i choose a port, which is unused, and router will not remap it to other (meaning AUTH will return the same port as client is using)? Then i will assume that i'm not behind NAT and use longer keep alive intervals, which will probably result in connection timeout. Is there any other methods of detecting NAT? I've thought of comparing not port numbers but the returned IP number to local IP number but i don't know it will always work.

Perpetually META Reloading Notify List

Posted: Thu Sep 21, 2006 11:27 pm
by Isochroma
I've been playing with another idea for notifications. This one uses the Windows Active Desktop to show an edited local html version of the main page. It is edited to remove all items but the notify line, and also has a meta refresh of 1 minute. Embedding it in a tiny locked window on the desktop, it shows up-to-the-minute # of notifys, and doesn't require special software.

There is however a problem. I'd like to be able to set the actual notify page (the one that pops up when you click the "n notifies" line). Unfortunately, it loads only once. Once it loads, the server clears all the entries, so refreshing won't work. Often I accidentally close (or IE crashes) the notify window and lose the notifys.

So the idea is to make a minor modification to the server software. A Notify is only removed from the list when the user browses the page it is for (anytime after the notify has been generated). This would fix a lot of issues and allow a perpetually auto-reloading list of notifys to be pinned to the desktop (and made into custom toolbars using 3rd party explorer toolbar apps!).

A feature request in more concise language has been submitted to the AniDB Bug & Feature Tracker:

AniDB Auto-Refreshing Notify

Posted: Sat Sep 23, 2006 2:32 am
by Isochroma
The AniDB Auto-Refreshing Notify was removed due to design faults which would cause excessive server load. Instead, a better solution using the UDP API will be implemented. This new program will be able to do lots of interesting things, and will also take up only a small portion of the desktop in a widget-like way.

Posted: Sat Sep 23, 2006 10:20 am
by Der Idiot
[ 12:14:01 ] [ @DerIdiot ] don't tell me...
[ 12:14:10 ] [ @DerIdiot ] isochroma you fucking nuthead
[ 12:14:22 ] [ @DerIdiot ] DON'T run scripts over the website
[ 12:14:25 ] [ @DerIdiot ] use the udp api
[ 12:14:46 ] [ @DerIdiot ] if you are too retarded to do that there is an easy way to deal with you called perm ban
[ 12:15:18 ] [ @DerIdiot ] it's not even about load. there is a suggested and RIGHT way to do this
[ 12:15:25 ] [ @DerIdiot ] it's what the udp api is for
[ 12:15:39 ] [ @DerIdiot ] if there is a feature you need not in yet bug epoxi
[ 12:15:51 ] [ +worf ] he'll get his ass banned for loading too many pages anyway :p
[ 12:15:53 ] [ @DerIdiot ] but fucking don't run scripts on the website
[ 12:16:43 ] [ +worf ] DerIdiot:
[ 12:17:17 ] [ @DerIdiot ] 00:09:23 isochroma mynotifies ?show=mynotifies&show.nhist=1
[ 12:17:17 ] [ @DerIdiot ] 00:09:32 isochroma mynotifies ?show=mynotifies&show.nhist=1
[ 12:17:17 ] [ @DerIdiot ] 00:09:38 isochroma mynotifies ?show=mynotifies&show.nhist=1
[ 12:17:17 ] [ @DerIdiot ] 00:09:40 isochroma mynotifies ?show=mynotifies&show.nhist=1
[ 12:17:17 ] [ @DerIdiot ] 00:09:57 isochroma mynotifies ?show=mynotifies&show.nhist=1
[ 12:17:27 ] [ @DerIdiot ] 5 requests in less than 1 minute
[ 12:17:29 ] [ @DerIdiot ] fucking nutter
[ 12:17:48 ] [ +worf ] kill him
[ 12:18:07 ] [ @DerIdiot ] indeed
[ 12:18:10 ] [ @DerIdiot ] there you have a nice ban
[ 12:18:12 ] [ @DerIdiot ] hf