Remote subscription failed after remote switch to https

My instance my.hethane.se could not subscribe to users on status.telecomix.org recently

I tried for a long time ago, when status.telecomix.org ran an older version (still 0.9 I believe) and they didn't use (force) SSL. Perhaps I didn't too.
The user feed subscription failed back then, but this stored an entry in my 'ostatus_profile' database table with a feeduri containing http://

Today telecomix have updated to 0.9.7fix1 (same as I installed new and clean on the hethane instance). They have also set 'SSL Always', meaning they require a https:// subscription url (I guess, it failed in the OStatus function recognizedFeed).

The errors I got were:
* my.hethane.se: "Internal Server Error - Could not set up remote subscription."

* my.hethane.se logs:
2011-06-09 11:54:31 LOG_ERR: [my.hethane.se:28663.99606b42 POST /main/ostatussub] HTTPClient: HTTP POST https://status.telecomix.org/main/push/hub - 400 Bad Request
2011-06-09 11:54:31 LOG_ERR: [my.hethane.se:28663.99606b42 POST /main/ostatussub] FeedSub::doSubscribe: sub req failed with HTTP 400: Unsupported hub.topic http://status.telecomix.org/api/statuses/user_timeline/1624.atom this hub only serves local user and group Atom feeds.

(as you can see, my feed subscription address is http, despite the new https requirement)

After removing the entry in ostatus_profile and trying to subscribe again, it worked well. However, the error was confusing and not very intuitive. Either the error should reflect the actual problem (bad feed uri) directly on the subscribe page, or the problem should somehow be avoided (rewrite a remote user's feeduri - if http/https changes).

Note that this has only been tried in the SUBSCRIBE PROCESS, not on current subscriptions. Could this bug be causing any other peculiar behaviour?