Normaly not, except if I missed some of them. My problem is that my profile URL has not been fully replicated across all instances on which I've subscriptions :(
@jordanc indeed it does, in a way. I checked some of my subscribers and yes, their subscription have been updated with my new URL. For example here http://identi.ca/yoha
But I'm still receiving requests on old URL scheme so I guess my remote profile on identi.ca has not been fully updated.
So, just wonder to know if there is something I can do, or you can do. I ran script /script/updateprofileurl.php which has generated a lot of salmon messages. Is it supposed to be enough ?
@jordanc, OK thanks, thought it was stronger than a caching issue. I've found a way to get it working again: supporting both URL scheme on my webserver.
But, since I have some tricky configuration, that wasn't so easy to find.
Could definitely be awesome if OStatus supports "live" profile updates.
Anyway it works now :)
Will update you if I still have old URLs within next days
@jordanc Seems I was too optimistic. If my profile has been somewhat updated after URL scheme change, it seems I'm still registered with old one. As a result, salmon checks always fails and I don't received messages. Some profile corruption maybe.
Is there any "magic" way, script or anything else, to fix things in code or do I have to wipe out my current installation and build a new one on a new domain to avoid conclicts with previous install ? Of course, as a metter of fact, identi.ca database is not clean anymore because of my corrupted profile :-/
Anyway, subscribers problem is still pending. They are still registered on my instance (I can see 20 of them on web UI). When looking into DB, I'm supposed to have more than 60 subscribers. Where are the others gone ? don't know yet.
If I can suggest something, StatusNet should only use id like nickname@domain.tld instead of http URL. This way, we can still find howto to reach a user with webfinger and never care again about URL changes.
It probably wouln't hurt to add your comments to that bug thread. As for the discrepancy with subscribers I'm not sure, that's kind of odd, most likely has to do with the url changing though.
Finally fixed subscribers issue this week-end. There's still an issue with my profile as registered on identi.ca but my subscribers can see my notices again.
@jordanc Here's my feedback of my URL scheme change. I really apologies if this did cause any problem on you side. This was not the goal :-/
1. Switch URL scheme (FancyURL switched to ON and SingleUser switched to ON). 2. Stopped receiving updates from other instances like identi.ca Stopped sending updates to other instances like identi.ca 3. Used script scripts/updateprofile.php, trying to fix things 4. Profile (http://identi.ca/user/remote/263727) changed from http://status.jbfavre.org/index.php/jbfavre to http://status.jbfavre.org/ - Displayed profile URL updated (from http://status.jbfavre.org/index.php/jbfavre to http://status.jbfavre.org/) - Guess that: * was because I used script scripts/updateprofile.php * Atom feed not updated (still http://status.jbfavre.org/index.php/api/statuses/user_timeline/1.atom). _ Could be checked in hubsub table, ostatus_profile and profile tables * Subscribers feedsub not updated (still the old uri in feedsub table) _ Same callback ID used (http://identi.ca/main/push/callback/2539) * Profile is not completely updated because of DB denormalization (I'll have to look deeper into code to confirm that point) 5. New remote profile created on identi.ca (http://identi.ca/user/remote/486887) - Same profile URL (http://status.jbfavre.org/) - Guess that: * feedurl is the right one for this profile (http://status.jbfavre.org/api/statuses/user_timeline/1.atom) * did not received notices since I used my new remote profile, without active subscriptions on identi.ca. _ old URL scheme was not answering anymore, see bellow point 6 on how I fixed it * my notices were not propagated either, because of topic URL not updated in my instance DB _ hubout was never triggered, see bellow point 7 on how I fixed it 6. Have been able to renew my subscriptions - Usin OStatus plugin's scripts plugins/OStatus/scripts/resub-feed.php and plugins/OStatus/scripts/update-profile.php - Guess that: * I'm somewhat still subscribed to identi.ca users with old profile _ Could be checked in hubsub table 7. Have been able to update hubsub (my subscribers callback) on my instance - Changed topic URL (from http://status.jbfavre.org/index.php/api/statuses/user_timeline/1.atom to http://status.jbfavre.org/api/statuses/user_timeline/1.atom) in hubsub table - Updated hashkey (sha1($topic.'|'.$callback) in hubsub table - Guess that: * Remote server (the one hosting callback URL) does not check updates against uri from feedsub :(
Comments
All your database links etc may be broken since the change.
Regards,
Andrew.
My problem is that my profile URL has not been fully replicated across all instances on which I've subscriptions :(
I checked some of my subscribers and yes, their subscription have been updated with my new URL. For example here http://identi.ca/yoha
But I'm still receiving requests on old URL scheme so I guess my remote profile on identi.ca has not been fully updated.
So, just wonder to know if there is something I can do, or you can do.
I ran script /script/updateprofileurl.php which has generated a lot of salmon messages. Is it supposed to be enough ?
I've found a way to get it working again: supporting both URL scheme on my webserver.
But, since I have some tricky configuration, that wasn't so easy to find.
Could definitely be awesome if OStatus supports "live" profile updates.
Anyway it works now :)
Will update you if I still have old URLs within next days
Seems I was too optimistic. If my profile has been somewhat updated after URL scheme change, it seems I'm still registered with old one.
As a result, salmon checks always fails and I don't received messages.
Some profile corruption maybe.
Is there any "magic" way, script or anything else, to fix things in code or do I have to wipe out my current installation and build a new one on a new domain to avoid conclicts with previous install ?
Of course, as a metter of fact, identi.ca database is not clean anymore because of my corrupted profile :-/
If it can help, I think I've fixed all my subscriptions, at least as far as I can tell, using /plugins/OStatus/script/update-profile.php
Just grabbed all subcriptions URI from DB with SQL and call the script for each of them.
Not very easy, but seems to do the job.
But I'm afraid I could lost them again because of my probable duplicate profile entries (the old one http://status.jbfavre.org/index.php/jbfavre and the new one http://status.jbfavre.org/).
Anyway, subscribers problem is still pending. They are still registered on my instance (I can see 20 of them on web UI). When looking into DB, I'm supposed to have more than 60 subscribers. Where are the others gone ? don't know yet.
If I can suggest something, StatusNet should only use id like nickname@domain.tld instead of http URL. This way, we can still find howto to reach a user with webfinger and never care again about URL changes.
As for the discrepancy with subscribers I'm not sure, that's kind of odd, most likely has to do with the url changing though.
There's still an issue with my profile as registered on identi.ca but my subscribers can see my notices again.
Here's my feedback of my URL scheme change.
I really apologies if this did cause any problem on you side. This was not the goal :-/
1. Switch URL scheme (FancyURL switched to ON and SingleUser switched to ON).
2. Stopped receiving updates from other instances like identi.ca
Stopped sending updates to other instances like identi.ca
3. Used script scripts/updateprofile.php, trying to fix things
4. Profile (http://identi.ca/user/remote/263727) changed from http://status.jbfavre.org/index.php/jbfavre to http://status.jbfavre.org/
- Displayed profile URL updated (from http://status.jbfavre.org/index.php/jbfavre to http://status.jbfavre.org/)
- Guess that:
* was because I used script scripts/updateprofile.php
* Atom feed not updated (still http://status.jbfavre.org/index.php/api/statuses/user_timeline/1.atom).
_ Could be checked in hubsub table, ostatus_profile and profile tables
* Subscribers feedsub not updated (still the old uri in feedsub table)
_ Same callback ID used (http://identi.ca/main/push/callback/2539)
* Profile is not completely updated because of DB denormalization (I'll have to look deeper into code to confirm that point)
5. New remote profile created on identi.ca (http://identi.ca/user/remote/486887)
- Same profile URL (http://status.jbfavre.org/)
- Guess that:
* feedurl is the right one for this profile (http://status.jbfavre.org/api/statuses/user_timeline/1.atom)
* did not received notices since I used my new remote profile, without active subscriptions on identi.ca.
_ old URL scheme was not answering anymore, see bellow point 6 on how I fixed it
* my notices were not propagated either, because of topic URL not updated in my instance DB
_ hubout was never triggered, see bellow point 7 on how I fixed it
6. Have been able to renew my subscriptions
- Usin OStatus plugin's scripts plugins/OStatus/scripts/resub-feed.php and plugins/OStatus/scripts/update-profile.php
- Guess that:
* I'm somewhat still subscribed to identi.ca users with old profile
_ Could be checked in hubsub table
7. Have been able to update hubsub (my subscribers callback) on my instance
- Changed topic URL (from http://status.jbfavre.org/index.php/api/statuses/user_timeline/1.atom to http://status.jbfavre.org/api/statuses/user_timeline/1.atom) in hubsub table
- Updated hashkey (sha1($topic.'|'.$callback) in hubsub table
- Guess that:
* Remote server (the one hosting callback URL) does not check updates against uri from feedsub :(
Your subscriptions are stored in feesub table, you subscribers in hubsub.
But that's definitely NOT recommanded to change ANY URL settings (you've been warned :) )