quote:
Originally posted by lysp
Although i havent studied the very latest protocol (13) i believe you are wrong. Open/close notifiers DO work.
In the technical pure sense of the word, yes... they always will notify when a window has been closed/opened. But the problem is they also notify on other events (as you know) but that last part isn't well understood by many people who use the notifiers as such. And because of that they aren't reliable in the sense to determine the cause of the notification. And something which isn't reliable, doesn't work (or it would be called "reliable" otherwise).
But if you mean "realiable" as in: they will always give a notifications, then yes, true...
quote:
Originally posted by lysp
When someone is idle for around 30 seconds it'll drop the connection. While its true it doesnt display a difference between a closed or dropped connection anymore, you can still estimate what happened due to timing.
Which has been quite often a problem because that timing has changed from protocol version to protocol version. <= not my words, but words of those who actually made such notifiers (eg: TheBlasphemer).
And IIRC, it even changed under other circumstances also at one point (not sure about that though).
quote:
Originally posted by lysp
So in conclusion it DOES work, and if you dont rely on it 100% due to the irregularities i mentioned above then its fine.
Yep ....though, provided you know the implications etc, just as you correctly explained. And there in lies the problem. Not everybody has that knowledge to deal with such things.
And that is also the same aspect as with those "block checkers". The reason I mentionned the block checkers is not because they work the same (as they worked in a total different matter; it hadn't todo with phone numbers, it was because of the fact that the
"only users in my allow list can see my status"-option had a bug), but they caused exactly the same confussions, misconceptions, etc amung people....
/ 
