Commit graph

59 commits

Author SHA1 Message Date
friendica
8a907a789f more diagnostic when changing primary 2014-10-13 17:59:03 -07:00
friendica
6503b91131 sql 2014-10-13 16:12:32 -07:00
friendica
1b0390af06 new function hubloc_change_primary() 2014-10-13 15:27:56 -07:00
friendica
f19d718631 that's why remove_obsolete_hublocs() isn't telling anybody when it does its thing, I forgot to uncomment the bit that tells everybody after I tested it. I needed extensive testing to make sure we didn't accidentally wipe out all hublocs everywhere. Testing went fine so I just assumed it was all working as planned; but went back today to find out why I wasn't told of a recent change. 2014-09-30 23:41:50 -07:00
friendica
0dc33900b6 provide a way to sync locations and get rid of bogus hublocs, now implemented 2014-09-14 22:19:19 -07:00
friendica
0350b76d85 some backend work for the remaining missing bits of mod_hubman - this is still a fair ways from being complete and is not ready for prime time. Basically we'll let a channel send out a public message saying "these are my currently approved locations" and anything that isn't in the list will be marked deleted. We'll send out this message when locations change somehow - either through direct personal involvement (hub revoke, change primary, channel import) or during a system rename or "find bad/obsolete hublocs" activity. This way we won't have clones sending back location info we just got rid of and re-importing the bad entries. 2014-09-13 16:00:09 -07:00
friendica
233e4e1363 remove some code duplication 2014-07-14 01:38:16 -07:00
friendica
fa5ac26828 doco 2014-03-19 19:56:21 -07:00
friendica
68fc2a220e prune_hub_reinstalls() and add cron weekly as a side effect 2014-03-19 19:53:14 -07:00