aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
...
* | in probe diagnostic - note https failure as diagnostic info - this also ↵friendica2013-10-011-3/+3
|/ | | | changes zot_finger so you can tell it not to fallback. This could be useful in corporate environments that are off the grid or other high security situations (as much as anything could be considered high security which relies on SSL).
* add the auto form submit even though it doesn't seem to work. Will debug it ↵friendica2013-10-011-1/+1
| | | | later.
* Add possibility to use a block a channel menu (set channel_menublock to the ↵zottel2013-10-011-1/+1
| | | | | | lowercase title of the block without special chars) Fix comanche_block() SQL
* implement republish permission for use in sourced channelsfriendica2013-09-303-1/+14
|
* directory sync - this will either work, or it won't work, or it will ↵friendica2013-09-304-64/+192
| | | | | | | | | 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.
* there's no $a in comanche_block() (zottel)friendica2013-09-301-1/+2
|
* ret_secret is not usedOlaf Conradi2013-09-301-5/+0
|
* RSS feeds as channel sources. It's feasible and within reach, however ↵friendica2013-09-291-45/+35
| | | | | | | | there's a lot of work left to do. How bad does anybody want it? Let's find out...
* remove the "Similar Interests" link until somebody makes it workfriendica2013-09-291-1/+1
|
* sources management pagefriendica2013-09-291-0/+1
|
* TypoThomas Willingham2013-09-291-1/+1
|
* Issue #117Thomas Willingham2013-09-291-10/+11
|
* Merge https://github.com/friendica/red into zpullfriendica2013-09-291-2/+2
|\
| * Fix Comanche menusThomas Willingham2013-09-281-2/+2
| |
* | Issue #158friendica2013-09-291-2/+2
|/
* close commentfriendica2013-09-282-1/+2
|
* fix can_comment_on_post when viewing wall-to-wallfriendica2013-09-282-6/+20
|
* convert to plaintext before matching words in body. Otherwise every post I ↵friendica2013-09-261-1/+5
| | | | make with a link in it is going to match a test for zot.
* aggregate channelsfriendica2013-09-261-26/+86
|
* Merge https://github.com/friendica/red into zpullfriendica2013-09-262-2/+6
|\
| * Merge pull request #155 from oohlaf/fixesOlaf Conradi2013-09-261-1/+5
| |\ | | | | | | Explain why public comments are disabled and what needs to happen to enable them.
| | * Add explanation why public comments are disabled.Olaf Conradi2013-09-261-1/+5
| | |
| * | TypoThomas Willingham2013-09-261-1/+1
| | |
* | | structure for channel unionsfriendica2013-09-262-2/+3
|/ /
* / suppress creating the directory update record for profile updates which are ↵friendica2013-09-252-4/+13
|/ | | | part of the normal import_xchan sequence - otherwise we get two for every change. Create it normally if we are called with a profile_update message and don't go through the whole import_xchan thing.
* populate the new fields in the directory updates tablefriendica2013-09-241-9/+17
|
* don't send email notifications for likes (as comment notifications). We'll ↵friendica2013-09-241-1/+6
| | | | need a separate preference for whether you want notifications for likes.
* Fix observer=1 tag. Using only observer without =1 won't work anymore now.zottel2013-09-241-2/+2
|
* reduce susceptibility to bleichenberger attackfriendica2013-09-241-1/+1
|
* spice this up a little bit...friendica2013-09-231-0/+8
|
* add [observer] tags and [observer.baseurl]zottel2013-09-231-0/+20
|
* one more edge case in the public perms - don't match perms = 0 which is ↵friendica2013-09-221-2/+3
| | | | private, this and prior checkin are for issue #114
* fixes for display and search privacy enforcementfriendica2013-09-221-10/+36
|
* bug #150, if deny access is present but nobody has been allowed, create an ↵friendica2013-09-221-1/+22
| | | | allow list containing everybody in your address book. Then subtract those who are denied.
* adult channel settingfriendica2013-09-221-0/+7
|
* hopefully(?) the final word on remote comment permissionsfriendica2013-09-201-3/+1
|
* fix contact comment permissionsfriendica2013-09-201-1/+6
|
* missing uid check on comanche_block to ensure we get the block with that ↵friendica2013-09-201-1/+2
| | | | name that we own
* OK, sure.friendica2013-09-201-1/+1
|
* hopefully this will go over a bit better - check post owner permissions as ↵friendica2013-09-201-1/+3
| | | | well as local owner permissions for comments during submission, since the comment was being blindly accepted on the local system due to only checking the profile owner. Also change collections query to include only top-level posts by a member of the collection.
* Mark child posts as commentable when parent is set to commentableOlaf Conradi2013-09-201-1/+2
|
* Enable likes again on postsOlaf Conradi2013-09-201-1/+1
|
* is_commentable() had some major issues when applied to the atrocity known as ↵friendica2013-09-203-12/+30
| | | | | | ConversationObject, hopefully this won't destabilise the network as it's a somewhat major permission tweak related to comments; also add any local clones to allowed_public_recips() as they should always be allowed recipients. Not sure what to do about host permissions in the event of clones. They have more than one host, and it isn't spelled out in the sent message. All of this stuff will make your head hurt.
* missing hashfriendica2013-09-192-2/+3
|
* provide a "safe search" backend and allow for self-censorship using nsfw or ↵friendica2013-09-192-0/+16
| | | | adult profile keywords. Eventually the directories will be forced to mark adult profiles and sync this knowledge between them. At the moment there's no way to do an unsafe search, but we really just need a checkbox and pass the value through directory to dirsearch on the back end, and some will want this as a pconfig.
* trim commas from keywordsfriendica2013-09-191-0/+1
|
* sync item_search with yesterday's network fix for collections. Add ud_addr ↵friendica2013-09-191-6/+12
| | | | to update table to store the target address since it's possible the mirroring directory won't yet have an xchan or hubloc they can link the ud_hash to and therefore mayn't know how to contact them.
* set default charset of email_header_encode, add ud_flags to indicate which ↵friendica2013-09-181-1/+1
| | | | (directory sync) updates have been processed in some way.
* add "tiered" access policy, add tagcloud to directory pagesfriendica2013-09-182-1/+3
|
* Changed CSS class "selected" to "active" in navbar, according to ↵Olivier Migeot2013-09-181-1/+1
| | | | https://abcentric.net/display/f17b319c6d4b616a0d0a639e177969c6ae084248f1ee2bec9d8147c9291bf495@abcentric.net