Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing first edits from an IP on launch #17

Open
webster opened this issue Jul 14, 2014 · 4 comments
Open

Missing first edits from an IP on launch #17

webster opened this issue Jul 14, 2014 · 4 comments

Comments

@webster
Copy link

webster commented Jul 14, 2014

It seems that the first time that an IP address in range makes an edit after anon is launched, the edit is ignored. In --noop mode, I've been able to reproduce this on several different IP addresses while testing. It would seem to me that this means that the first edit from any IP in range is missed, after each launch of anon.

  1. Start anon
  2. Edit a page from an IP in range (let's say 127.0.0.2)
  3. Nothing listed in the console
  4. Edit a page from the same IP in range (again, 127.0.0.2)
  5. Appears in console
  6. Edit a page from 127.0.0.3
  7. Nothing listed in console
  8. Edit a page from 127.0.0.3 again
  9. Appears in console
  10. Edit a page from 127.0.0.3 again
  11. Appears in console
  12. Control+C to kill anon
  13. Start anon again
  14. Edit a page from 127.0.0.3 again
  15. Nothing appears in console
  16. Edit a page from 127.0.0.3 again
  17. Now it re-appears in console.

As provided here, the second, third, and so on are all showing up just fine. The first one never does. And even if an IP has made a change before, that is forgotten and the first update on re-launch of anon is missed again.

@webster
Copy link
Author

webster commented Jul 14, 2014

Never mind, this does not appear to be reproducible if I wait awhile before testing a change. Because there's no documentation, I wasn't aware that anon was connecting to an IRC server to listen for changes, so there's a bit of a long wait in negotiating that connection.

I might suggest letting people know that it's connecting to an IRCd (and over an unencrypted connection, at that). Some hosts prohibit IRC. Thanks!

@webster webster closed this as completed Jul 14, 2014
@edsu
Copy link
Owner

edsu commented Jul 15, 2014

It does take some time for anon to join all 33 IRC channels, because they can't be joined all at once or else the client gets booted for excess flood. I'm glad you figured it out! Some documentation is probably needed.

@jarib
Copy link
Contributor

jarib commented Jul 15, 2014

Perhaps a "finished setup" event could be console.log'ed to make this obvious.

@edsu edsu reopened this Jul 15, 2014
@edsu
Copy link
Owner

edsu commented Jul 15, 2014

Yes, I like the idea of a 'finished setup' log message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants