aboutsummaryrefslogtreecommitdiffstats
path: root/include/dir_fns.php
Commit message (Collapse)AuthorAgeFilesLines
* regression: (-1) update_flag still exists in one function. This should be ↵friendica2014-06-011-1/+1
| | | | UPDATE_FLAGS_FORCED or 2.
* Set a default directory server from a hard-wired list if one was not ↵friendica2014-04-251-3/+24
| | | | previously chosen.
* directory sync issuesfriendica2014-03-031-0/+3
|
* implement a forced directory update mode where we unconditionally create a ↵friendica2014-02-111-5/+8
| | | | directory sync packet. This is needed to ensure that monthly directory pings are propagated to other directory servers so they can each prove for themselves whether or not an account is alive or dead. We do not trust other directories to provide us information beyond "look at this entry and decide for yourself" as doing otherwise would invite rogue directory manipulations. As this scheduled update occurs on all channels across all servers, we should also pick up refresh messages from all existing channel clones and these should also propagate out to all directory servers using the same mechanism (though perhaps not at the same time).
* reversed args in update_modtime, incorrect ud_guid and ud_hashfriendica2014-02-101-2/+2
|
* extend the directory profiles a bit morefriendica2013-12-251-0/+4
|
* improve the directory popup a bitfriendica2013-12-231-2/+2
|
* split private messages into two modules - "message" is just for message ↵friendica2013-12-211-2/+2
| | | | lists, "mail" is for reading and writing conversations. This is so we can Comanchify it cleanly.
* Don't let nobody set an xconfig in safe search.Thomas Willingham2013-12-111-1/+2
|
* Fix missing argument warningOlaf Conradi2013-11-121-1/+1
|
* turn safemode into a proper widgetfriendica2013-11-111-0/+1
|
* More safe search - since the default is one, toggle only works afterThomas Willingham2013-11-111-1/+1
| | | | | an initial xconfig is set - the first one will turn safe search on (ie, do nothing from a users point of view). Fix that.
* Stray lineThomas Willingham2013-11-091-3/+0
|
* Clean upThomas Willingham2013-11-091-1/+1
|
* Bring safe search to the UIThomas Willingham2013-11-091-0/+18
|
* create update record for accounts on directory server itself during profile ↵friendica2013-10-241-2/+5
| | | | changes, re-queue failed directory sync packets, fix account_id index in queue creation, be more selective about updating hubloc_connected (only when we're talking to the associated site). But we still need a way to flag dead accounts and these mechanisms won't cut it, because it isn't a requirement that channels communicate with anybody, except for contacting the directory when the account is created. I think we need to make every channel ping the directory once a month. Then we can find those that have not done so (after syncing with other directories). We can't have the directory just flag dead accounts as this would create a way for an anti-social attacker to become a directory server and mark all the accounts dead.
* extra loggingfriendica2013-10-141-1/+4
|
* sql typo in directory syncfriendica2013-10-141-1/+1
|
* directory sort links on sidebarfriendica2013-10-131-0/+11
|
* provide config for preferred directory serverfriendica2013-10-131-0/+3
|
* directory sync - this will either work, or it won't work, or it will ↵friendica2013-09-301-3/+61
| | | | | | | | | possibly recurse and blow up the matrix. Hard to say. Do you feel lucky? Well do ya' ... punk? Rule #1 - don't mess with anything unless it's blowing up the matrix. If it doesn't blow up the matrix, but doesn't work, just let it go and let's figure out what it is doing and what it isn't doing. The flow is as follows: Once a day go out to all the directory servers besides yourself and grab a list of updates. This happens in the poller. If we've never seen them before add them to the updates table. The poller also looks to see if we're a directory server and have updates that haven't yet been processed. It calls onedirsync.php to process each one. If we contact the channel to update and don't find anything (we're just doing a basic zot_finger), set a ud_last timestamp. If this is set we will only try once a day for seven days. Then we stop trying to update. This will probably cause a spike the first time through because you haven't seen any updates before, but we spread out the load over your delivery interval.
* really, truly fix the age missing in directory bugfriendica2013-07-021-1/+4
|
* for directory sync, ensure we have a fallback master; even if we have ↵friendica2013-04-181-0/+43
| | | | nothing else
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* fix localdir privacy (again)friendica2013-02-191-1/+5
|
* set xchan hidden flag correctly when local directory updatefriendica2013-02-191-0/+20
|
* directory debuggingfriendica2013-02-191-0/+2
|
* This was bloody hard to sort out.... but now it's sorted and we can move ↵friendica2012-12-271-0/+3
| | | | forward again. Put back xtag for efficient keyword searching, use it in conjunction with xprof['keywords'] to avoid a SQL triple join and group_concat (which simply won't scale on a directory server), figured out how best to work timezone corrected birthdays into the protocol. The directory can even provide an age if one was provided to it. Both of these things need some more work, but we have the mechanisms and a plan how to do it right instead of "how the !@#$ are we going to do pull this off?"
* get rid of xtagfriendica2012-12-271-3/+0
|
* master/standalone directory profile updatefriendica2012-12-261-0/+51
|
* directory page still needs a lot of work, look up locally if local master or ↵friendica2012-12-191-0/+6
standalone, need to put some basic profile info in discovery page and direct to local directory master
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-13 05:35:23 +0000