| 1 |
'x' means: is done! |
| 2 |
|
| 3 |
- keep an eye on disco_feature stuff. |
| 4 |
- fix MUC documentation! |
| 5 |
X make the MUC extension not be tied to a specific connection. |
| 6 |
Let it discover new connections itself. |
| 7 |
=> for this the join_room function might need a connection argument |
| 8 |
to discover the right connection. => maybe use the %args hash for this, |
| 9 |
as the default should be 'the first' connection we can grab. |
| 10 |
=> think about get_room and the implications in general that 'multiple' |
| 11 |
connections are handled by one extension. |
| 12 |
- vcard retrieve sends out presence, but the 'last sent presence' info |
| 13 |
isn't available in the connection or to the vcard extension. |
| 14 |
=> introduce storing the 'last sent presence' and offer a 'send_presence_update' |
| 15 |
method (at least internally), to repeat the last sent presence (be careful |
| 16 |
not to repeat directed presences!). |
| 17 |
- think more about $dont_retrieve_vcard. |
| 18 |
- make exponential falloff in Client.pm when an account couldn't be connected. |
| 19 |
- remove XML::Twig dependency from debug => ... |
| 20 |
- map the domain part correctly w.r.t. IDNA |
| 21 |
- rename 'domain' parameter to 'host', |
| 22 |
and rename the internal host/port to peer_host and |
| 23 |
peer_port. |
| 24 |
- add nick_change to documentation |
| 25 |
- Implement XEP-0045: Multi-User Chat |
| 26 |
x store full jid info on entering room |
| 27 |
x implement delayed delivery for messages |
| 28 |
x WRITE TEST! |
| 29 |
- to mark history of room |
| 30 |
x 7.8 Sending a Private Message |
| 31 |
x 7.9 Sending a Message to All Occupants |
| 32 |
- visitor error (when room not allow without voice to chat) |
| 33 |
- improve room info handler class to retrieve interesting information eaasier |
| 34 |
- room occupant query |
| 35 |
- implement status code mappings |
| 36 |
- that room logged |
| 37 |
- non anonymous |
| 38 |
x look over error reporting (more conclusive errors!) |
| 39 |
x change presenceerror to something more clear |
| 40 |
x entering members only |
| 41 |
x banned |
| 42 |
x nickname conflict |
| 43 |
- with resolution |
| 44 |
x max users |
| 45 |
x locked |
| 46 |
x 11. Error and Status Codes |
| 47 |
x 11.1 Error Codes |
| 48 |
- 11.2 Status Codes |
| 49 |
- managing of discussion history when entering |
| 50 |
- maxchars, maxstanzas, seconds, since |
| 51 |
x nickname changes |
| 52 |
x make own possible |
| 53 |
x log changes of other people nicknames |
| 54 |
- according errors |
| 55 |
- test changing of presence of a user |
| 56 |
- invitations |
| 57 |
- 7.10 Registering with a Room |
| 58 |
- 7.11 Discovering Reserved Room Nickname |
| 59 |
- 7.12 Requesting Voice |
| 60 |
- 8. Moderator Use Cases |
| 61 |
x 8.1 Modifying the Room Subject |
| 62 |
- test error handling of subject_change_error |
| 63 |
- 8.2 Kicking an Occupant |
| 64 |
- 8.3 Granting Voice to a Visitor |
| 65 |
- 8.4 Revoking Voice from a Participant |
| 66 |
- 8.5 Modifying the Voice List |
| 67 |
- 8.6 Approving Voice Requests |
| 68 |
- 9. Admin Use Cases |
| 69 |
- 9.1 Banning a User |
| 70 |
- 9.2 Modifying the Ban List |
| 71 |
- 9.3 Granting Membership |
| 72 |
- 9.4 Revoking Membership |
| 73 |
- 9.5 Modifying the Member List |
| 74 |
- 9.6 Granting Moderator Privileges |
| 75 |
- 9.7 Revoking Moderator Privileges |
| 76 |
- 9.8 Modifying the Moderator List |
| 77 |
- 9.9 Approving Registration Requests |
| 78 |
- 10. Owner Use Cases |
| 79 |
x 10.1.1 General Considerations |
| 80 |
x 10.1.2 Creating an Instant Room |
| 81 |
x 10.1.3 Creating a Reserved Room |
| 82 |
x entering password protected rooms |
| 83 |
- 7.7 Occupant Modification of the Room Subject |
| 84 |
- 10.1.4 Requesting a Unique Room Name |
| 85 |
- 10.2 Subsequent Room Configuration |
| 86 |
- 10.2.1 Notification of Configuration Changes |
| 87 |
- 10.3 Granting Ownership Privileges |
| 88 |
- 10.4 Revoking Ownership Privileges |
| 89 |
- 10.5 Modifying the Owner List |
| 90 |
- 10.6 Granting Administrative Privileges |
| 91 |
- 10.7 Revoking Administrative Privileges |
| 92 |
- 10.8 Modifying the Admin List |
| 93 |
- 10.9 Destroying a Room |
| 94 |
- 7.6 Converting a One-to-One Chat Into a Conference |
| 95 |
|
| 96 |
- write a tutorial for simxml |
| 97 |
- improve the SSL/TLS handling |
| 98 |
- make more tests |
| 99 |
- oob |
| 100 |
- data forms |
| 101 |
- jabber component |
| 102 |
- fix the inaviodable memoryleaks with the callbacks |
| 103 |
the circular object structs. |
| 104 |
- put some serious stuff in the synopsises |
| 105 |
- look at attribute namespace preservation! (if they got |
| 106 |
prefixes, how to parse this with expat? |
| 107 |
see also http://www.w3.org/TR/REC-xml-names/#scoping-defaulting ) |
| 108 |
- fix problem that xml::writer writes after <stream/> ahs been written |
| 109 |
- reproduce by conflicting resources! |
| 110 |
- test the xml parse error object somehow! |
| 111 |
- add context field to IQ error for all the places origin from IQ errors |
| 112 |
(bind_error, session_error, ...) |
| 113 |
- AnyEvent::XMPP::Client |
| 114 |
- find a way to distinguish presences from JIDs that |
| 115 |
are in multiple account's roster. |
| 116 |
- AnyEvent::XMPP missing functionality to be RFC 3920 conform: |
| 117 |
- improve error handling for SASL to |
| 118 |
support retries as specified in RFC 3920. |
| 119 |
(eg. by supporting a method sasl_retry() which takes |
| 120 |
the changed credentials) |
| 121 |
x SRV record lookup |
| 122 |
- weight handling! |
| 123 |
- AnyEvent::XMPP::IM missing functionality to be RFC 3921 conform: |
| 124 |
- 7.2. Business Rules |
| 125 |
- Implement XEP-0115: Entity Capabilities |
| 126 |
- Implement XEP-0190: Best Practice for Closing Idle Streams |
| 127 |
x Implement XEP-0030: Service Discovery |
| 128 |
- see also: XEP-0128: Service Discovery Extensions |
| 129 |
- missing feature: building up a item tree for discovery |
| 130 |
- see also: grep 'XXX\|FIXME\|TODO' * -r |
| 131 |
- lib/AnyEvent/XMPP/Writer.pm: # XXX: removed authname, because it |
| 132 |
ensures maximum connectivitiy |
| 133 |
long term? |
| 134 |
========== |
| 135 |
|
| 136 |
x Implement XEP-0082: XMPP Date and Time Profiles |
| 137 |
- provide maybe _to functions for the old format, |
| 138 |
it's still in use out there |
| 139 |
- make dns resolution async! |
| 140 |
- Maybe implement XEP-0146: Remote Controlling Clients |
| 141 |
x keep an eye on: |
| 142 |
- TLS: implemented, just do some extensive testing WRT blocking, |
| 143 |
i don't trust the current way the watchers are handled, |
| 144 |
i'm in fear of deadlocks... |