aboutsummaryrefslogtreecommitdiffstats
path: root/mod/zfinger.php
Commit message (Collapse)AuthorAgeFilesLines
* remove cyclic dependency on XCHAN_FLAGS_HIDDENfriendica2014-07-051-2/+3
|
* honour the admin censored flag in the directory, and some slow progress on ↵friendica2014-06-221-1/+2
| | | | extended likes
* bring back birthdaysfriendica2014-06-021-5/+10
|
* this should be better - "xchan deleted" state on remote sites only follows ↵friendica2014-04-071-5/+6
| | | | the xchan_flags and not the channel_pageflags; XCHAN_FLAGS_DELETED should only be set if the channel is to be removed from the entire network. As mentioned in a previous commit, channel_pageflags could be set to PAGE_REMOVED but still leave living clones on other sites.
* prevent follows of and notifications to deceased channelsfriendica2014-04-071-2/+4
|
* bring friends backfriendica2014-03-061-2/+1
|
* some anomolies found when viewing connections in various cases.friendica2014-03-021-2/+14
|
* extend the directory profiles a bit morefriendica2013-12-251-1/+5
|
* Provide a fallback channel to probe for magic-auth when we have no prior ↵friendica2013-12-151-5/+27
| | | | | | | | communications with a site. This will be a system channel if one exists, otherwise any channel will do. We'll try to use the first valid channel on the site because that was probably created when the site was installed and is the closest thing to a system channel we've got.
* add hooks to zot-finger and import_xchanfriendica2013-12-031-0/+1
|
* allow zot-info to return results for address= with webbies or naked nicknamesfriendica2013-11-291-1/+2
|
* reduce the likelihood that a given channel will have 30-40 valid hublocs ↵friendica2013-11-271-1/+1
| | | | with the same hubloc_url.
* allow zot public providers to list their location, as a non US-based server ↵friendica2013-10-301-0/+1
| | | | could be a strong selling point.
* structure for channel unionsfriendica2013-09-261-5/+0
|
* adult channel settingfriendica2013-09-221-3/+4
|
* add "tiered" access policy, add tagcloud to directory pagesfriendica2013-09-181-0/+2
|
* site sellpage linksfriendica2013-09-171-0/+1
|
* Pieces we'll need to tie together chanman and account/channel deletion and ↵friendica2013-09-171-1/+2
| | | | | | | | directory sync. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. OK? Understood?
* fix the missing brace before pushingfriendica2013-09-141-2/+3
|
* some fixes to directory keyword searchesfriendica2013-09-141-2/+4
|
* No need to add name_updated twice in zfinger responseOlaf Conradi2013-09-111-2/+1
|
* premium/restricted channel connections implemented, configure at ↵friendica2013-08-211-1/+1
| | | | yoursite/channel/nickname - this basically redirects "follow" requests to a premium channel's sell page if it has one configured. You can still click through and create a connection request (introduction), but this provides a means for the channel owner to state their terms. If you don't abide by the terms, you will likely be blocked or the channel deleted. This facility is extensible in a number of ways.
* basic structure for premium channel implementationfriendica2013-08-211-0/+12
|
* Add a site access policy (to determine if this is really a public site or ↵friendica2013-08-061-0/+10
| | | | just an open site) and add an orphan flag to xchans in case all their hublocs go away. Get rid of a couple of DO NOT EDIT template messages which were still lurking in the tree.
* hide detailed site information if you're off the grid.friendica2013-07-241-23/+32
|
* add more siteinfofriendica2013-07-241-0/+14
|
* more site statsfriendica2013-07-241-0/+5
|
* start saving site infofriendica2013-07-231-0/+6
|
* add age to directory profile - requires updating on each birthday and that ↵friendica2013-06-301-0/+3
| | | | part is still missing
* Add site registration policy to site record. This is not yet used or stored, ↵friendica2013-06-201-1/+8
| | | | but potentially can be exchanged through directory mirrors to automatically create "open site" lists.
* .friendica2013-03-101-0/+6
|
* send correct 'searchable' directory setting based on default profile settingfriendica2013-02-121-0/+4
|
* update friends in common tool now that poco is workingfriendica2013-01-311-10/+0
|
* security fixes related to directory access and sites that are off the gridfriendica2013-01-221-2/+1
|
* hidden directory entriesfriendica2013-01-221-1/+2
|
* zfinger issue stray unfinished statementfriendica2013-01-041-2/+4
|
* temporary feed import/export (public only for the moment) until this is ↵friendica2013-01-031-7/+14
| | | | integrated with remote permissions
* zome issues registering new hubsfriendica2013-01-021-1/+1
|
* poco discoveryfriendica2013-01-011-0/+3
|
* This was bloody hard to sort out.... but now it's sorted and we can move ↵friendica2012-12-271-9/+11
| | | | 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?"
* add keywords to zot-info profilefriendica2012-12-261-0/+10
|
* add important profile fields to zot-info if permitted - for directoryfriendica2012-12-261-12/+22
|
* allow toplevel domain redirects for zot-infofriendica2012-12-251-0/+11
|
* wrong constantfriendica2012-12-201-2/+2
|
* directory discoveryfriendica2012-12-201-0/+14
|
* some changes for directory servicesfriendica2012-12-191-0/+4
|
* one could say we've sort of got zot - at least there are two-way ↵friendica2012-11-121-7/+18
| | | | communications for channel meta info, don't yet know if it's working
* starting to get into the hairy parts of zot - identity, location, and ↵friendica2012-11-101-3/+3
| | | | permission synchronisation. After this, messaging should be a piece of cake.
* secure permission discoveryfriendica2012-11-021-1/+3
|
* add key passing and verification to targeted discoveryfriendica2012-11-021-5/+13
|