aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* implement 'can_comment_on_post()' which doesn't require a separate DB lookup ↵friendica2013-06-163-3/+43
| | | | per item.
* We will need a per item comment policy to be able to determine in advance if ↵friendica2013-06-161-3/+12
| | | | we have permission to comment on something , and we'll need to send it out with all communications. The current check is not only flawed but also a huge performance hit. Also provide the ability for an item to disable commenting completely - such as for a webpage or wherever you want to prevent comments on one item, without requiring a change to your entire permission scheme. All of this is only partially implemented at the moment but we need the structures in place on several sites in order to finish it without breaking everything.
* hopefully this won't screw up everything - if it does, revert. Otherwise ↵friendica2013-06-162-23/+31
| | | | this should work at delivery time to check tag deliveries and bounce the message before it's stored if the channel doesn't allow you to post and you aren't allowed to tag deliver either. Previously this was handled after the post was already stored so you needed posting permission as well as tag deliver permission to get past the checks.
* don't federate webpages ;-)friendica2013-06-151-0/+6
|
* fix "new connection has less permissions than public"friendica2013-06-151-4/+12
|
* silence a pointless warningfriendica2013-06-151-1/+1
|
* push refresh messages, performance work on conversations and configs, doc ↵friendica2013-06-145-29/+95
| | | | updates
* missing includefriendica2013-06-131-0/+1
|
* feeds are bit more standards compliant and a bit less broken nowfriendica2013-06-121-40/+39
|
* very minimal Atom feed - there will be a lot of bugs and unparseable content ↵friendica2013-06-121-192/+64
| | | | if you've got elaborately structured objects, but I got the thing to at least render in firefox given some quick test posts. If you find bugs (as you certainly will), feel free to fix them.
* missed a few zrl/zmg conversions, like for translate_item and enotify messagesfriendica2013-06-122-26/+27
|
* by default pending connections have no rightsfriendica2013-06-061-2/+2
|
* no GMT_TIMESTAMP() in mysql - use UTC_TIMESTAMP() insteadfriendica2013-06-061-1/+1
|
* This should get community tagging pretty close to working - deleting a ↵friendica2013-06-042-6/+36
| | | | community tag is left as a FIXME
* tagging posts now sends out a presumably legal activity message - all that's ↵friendica2013-06-041-2/+10
| | | | missing is catching it on the post owner's side, checking if people can tag this stream, and then add the tag to the parent message.
* fix buggered contact photosfriendica2013-06-031-0/+20
|
* templatise alt_pagerfriendica2013-06-031-13/+9
|
* move oohembed service to addonfriendica2013-06-031-5/+10
|
* force delayed_publish time comparisons to UTC.friendica2013-05-291-2/+2
|
* add photos and albums enumeration to Red API (will allow us to export either ↵friendica2013-05-292-3/+54
| | | | all our photos or individual albums using a script)
* Typo, or somehow ended up with a missing line another way.Thomas Willingham2013-05-291-0/+1
|
* Merge https://github.com/friendica/red into zpullfriendica2013-05-281-0/+1
|\
| * Add red smiley for the sake of consistency with Friendica's set.Thomas Willingham2013-05-281-0/+1
| |
* | issue #55 (number 2)friendica2013-05-281-4/+6
|/
* convert most red photos to zmgfriendica2013-05-283-15/+17
|
* cleanup localisation of like activitiesfriendica2013-05-281-5/+3
|
* wrong attribution on likes of comments in email notifications. Let's also ↵friendica2013-05-282-34/+22
| | | | call the thing they liked a comment instead of a status
* add support for zmg bbcode tag (img with class=zrl) which will eventually ↵friendica2013-05-271-1/+3
| | | | get turned into a zid link when rendered for display. TODO - turn photo items and photos uploaded into posts into zmg, then run all incoming bbcode posts through a filter to see if there's a photo from a known hubloc (with an http(s): src attr - not data:) and if so turn it into a zmg. Then fix the zidify functions to look for class="zrl" and we're done.
* fix zidify_img_callback - wrong number of argsfriendica2013-05-271-1/+1
|
* zidify img links, delay notifier until actually published for time ↵friendica2013-05-274-8/+42
| | | | travelling posts
* use http_authorization header with nginxfriendica2013-05-231-0/+10
|
* move new_cookie() to the session driver so we can use it for other purposes ↵friendica2013-05-232-10/+11
| | | | besides "normal" web login (for instance magic auth)
* more progress on items_fetch (new name)friendica2013-05-232-36/+39
|
* implement time travelling postsfriendica2013-05-232-0/+19
|
* first cut at generic item searchfriendica2013-05-221-0/+222
|
* and the obligatory typofriendica2013-05-221-0/+1
|
* add api/red/channel/stream POST method (post_activity_item()), add ↵friendica2013-05-221-0/+12
| | | | additional endpoint to channel export to api/red/channel/export/basic
* add basic input filtering to the simple activity postingfriendica2013-05-221-0/+20
|
* missing commafriendica2013-05-211-1/+1
|
* improvements to post_activity_item() so that it does not behave differently ↵friendica2013-05-211-0/+13
| | | | with delivery plugins than post_local via the API.
* fix app displayfriendica2013-05-212-2/+8
|
* more permissions descriptive text to lessen confusionfriendica2013-05-211-1/+1
|
* some auto-friending cleanupsfriendica2013-05-191-1/+3
|
* typo in auto permissionsfriendica2013-05-191-1/+1
|
* doc update plus fix the "only to those in my address book" permissionfriendica2013-05-181-0/+5
|
* extend delivery reports to mailfriendica2013-05-161-1/+11
|
* workarounds for people that re-install and end up polluting everybody's ↵friendica2013-05-161-2/+2
| | | | databases with stale entries
* fix setting account_roles for admin accountfriendica2013-05-151-1/+1
|
* fix intltext template driverfriendica2013-05-154-6/+12
|
* fix intltext templates - maybefriendica2013-05-152-23/+25
|