Title: oddsocket's Replies | WordPress.org

---

# oddsocket

  [  ](https://wordpress.org/support/users/oddsocket/)

 *   [Profile](https://wordpress.org/support/users/oddsocket/)
 *   [Topics Started](https://wordpress.org/support/users/oddsocket/topics/)
 *   [Replies Created](https://wordpress.org/support/users/oddsocket/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/oddsocket/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/oddsocket/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/oddsocket/engagements/)
 *   [Favorites](https://wordpress.org/support/users/oddsocket/favorites/)

 Search replies:

## Forum Replies Created

Viewing 1 replies (of 1 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[plugin jetpack]](https://wordpress.org/support/topic/plugin-jetpack/)
 *  [oddsocket](https://wordpress.org/support/users/oddsocket/)
 * (@oddsocket)
 * [14 years, 5 months ago](https://wordpress.org/support/topic/plugin-jetpack/#post-2273150)
 * Same problem here – I can confirm that although the bug affecting xmlrpc is now
   six years old, Namesco absolutely will not allow even a single user to have this
   block lifted.
 * WordPress for Android and iOS are able to reference xmlrpc without it having 
   to specifically address the xmlrpc.php file, can the Jetpack server not do the
   same?

Viewing 1 replies (of 1 total)