aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* 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
* fix sql for directory tagcloudfriendica2013-09-171-1/+1
|
* provide the back-end for a directory tag cloudfriendica2013-09-171-0/+60
|
* site sellpage linksfriendica2013-09-171-4/+8
|
* Pieces we'll need to tie together chanman and account/channel deletion and ↵friendica2013-09-173-20/+84
| | | | | | | | 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?
* missing verb on items linked to photosfriendica2013-09-171-1/+1
|
* more work on viewing obscured api postsfriendica2013-09-162-10/+17
|
* use prepare_body in api calls to properly render content, add 'mode' to ↵friendica2013-09-163-8/+11
| | | | conversation templates so that themes can use the module context to suppress or show comments as desired
* several oauth fixes - shred doesn't completely work yet, but it also doesn't ↵friendica2013-09-162-32/+46
| | | | completely NOT work, so at least there's some improvement
* found itfriendica2013-09-151-3/+3
|
* more loggingfriendica2013-09-151-0/+3
|
* don't create a directory sync notification (entry in the updates table) if ↵friendica2013-09-151-17/+30
| | | | the site record was updated - without checking first to see if anything changed. This is causing lots of sync entries when nothing changed to warrant it.
* implement what I hope will now be the server side of directory sync, add ↵friendica2013-09-152-13/+24
| | | | viewsrc to item_photo_menu, and log what changed in import_xchan update objects so we can find out why there are so many updates when nothing _obvious_ has changed that should trigger it.
* some fixes to directory keyword searchesfriendica2013-09-141-1/+1
|
* set menu_channel_id before we use it in a queryMichael Johnston2013-09-141-3/+2
|
* let me edit menu_desc even if menu_name has not changedMichael Johnston2013-09-141-2/+4
|
* Revert broken commitOlaf Conradi2013-09-141-92/+2
|
* First try to tell a comment from a like/dislike in notification systemmrjive2013-09-141-2/+92
|
* import_xchan - check every known hubloc/location field and create a new ↵friendica2013-09-141-4/+8
| | | | hubloc if anything at all changed anywhere.
* doc update, put more telemetry on notifier and try to ensure that private ↵friendica2013-09-132-0/+7
| | | | posts have recipients.
* need to figure out what's causing thisfriendica2013-09-121-0/+6
|
* No point beating a dead horsefriendica2013-09-121-1/+8
|
* so public_recips and allowed_public_recips is working so much better than ↵friendica2013-09-121-4/+12
| | | | before, but was still not quite right. We seem to be getting all the right results for top-level posts now, but comments aren't getting through on channels for which we've allowed them to send us their stream, but not comment on our posts. The reason is we were seeing if they could comment - and we only need to do that if we own the post. If they own the post, we only need to check if they can send us their stream.
* remove some debugging stuff now that the problem they were trying to locate ↵friendica2013-09-121-5/+0
| | | | down has been solved.
* Merge pull request #129 from MicMee/masterfriendica2013-09-121-1/+2
|\ | | | | to flag failed auth attempts in db table hubloc as hubloc_receive_error
| * delete logger line; was the wrong place.Michael Meer2013-09-111-1/+0
| |
| * flag failed auth attempts in DB table hublocMichael Meer2013-09-111-1/+3
| |
* | assuming this doesn't blow up the internet like the last fix - this is a ↵friendica2013-09-111-1/+1
|/ | | | very old bug that's been reported time and time again and nobody every bothered to debug or even report it somewhere where we could monitor it. It's buried somewhere in my stream, but basically is "things don't work right if you've got 'everybody in my address book' permissions" on "can send me their channel stream and posts". I think this is Michelle's problem and anybody else who has en empty matrix after making lots of connections.
* make comments work againfriendica2013-09-101-1/+2
|
* well that really stuffed things up...friendica2013-09-102-3/+3
|
* this should fix the foreign language like notifications (again)friendica2013-09-101-2/+4
|
* change wording on item_store message so we can find failures fast with grep ↵friendica2013-09-101-1/+1
| | | | item_store logfile | grep -v created
* provide detailed error to remote site for the myriad of things that can go ↵friendica2013-09-105-27/+60
| | | | wrong inside item_store(), !! this changes the return of item_store !!
* z_fetch_url - include curl debug info in return array and log it (at ↵friendica2013-09-101-0/+10
| | | | | | logger_data level) on failure This should probably be at a lower log level, but unsuccessful connections could happen a lot on a busy production site so we'll try to keep the log noise down unless somebody really needs to track this info.
* just a typoMichael Meer2013-09-091-1/+1
|
* some alteration to the way directory sync was originally supposed to work. ↵friendica2013-09-091-25/+14
| | | | I'm making this up as I go and not exactly certain where to go next but it makes more sense now and I think the basic idea will actually work. I'll just have to keep making it up until it does work.
* perform a refresh_all when an import has completed so that all your ↵friendica2013-09-081-3/+2
| | | | connections get a fresh update.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-07 05:42:53 +0000