aboutsummaryrefslogtreecommitdiffstats
path: root/include/items.php
Commit message (Collapse)AuthorAgeFilesLines
* implement 'can_comment_on_post()' which doesn't require a separate DB lookup ↵friendica2013-06-161-1/+41
| | | | 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-161-22/+28
| | | | 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.
* 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.
* This should get community tagging pretty close to working - deleting a ↵friendica2013-06-041-2/+32
| | | | 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.
* force delayed_publish time comparisons to UTC.friendica2013-05-291-2/+2
|
* convert most red photos to zmgfriendica2013-05-281-7/+7
|
* wrong attribution on likes of comments in email notifications. Let's also ↵friendica2013-05-281-34/+6
| | | | call the thing they liked a comment instead of a status
* more progress on items_fetch (new name)friendica2013-05-231-36/+38
|
* implement time travelling postsfriendica2013-05-231-0/+9
|
* first cut at generic item searchfriendica2013-05-221-0/+222
|
* 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-211-1/+5
|
* photo driver abstractionfriendica2013-04-251-6/+6
|
* turn naked links in posts into zrl's if we've got a hubloc for the sitefriendica2013-04-181-0/+25
|
* basic poke workingfriendica2013-04-171-1/+1
|
* turn all Red links into zrls (not the old zrls, the new bbcode zrl which ↵friendica2013-04-151-6/+6
| | | | means we can zidify them)
* begin to cut the umbilicalfriendica2013-04-141-1/+1
|
* wrapper function to create arbitrary activities (e.g. for plugins and apps) ↵friendica2013-04-041-0/+65
| | | | with a minimal amount of fuss, though the amount of fuss could increase significantly depending on the nature of the activity. For a simple wall post, just set the $arr['body'] to the desired text and we'll do the rest. If the activity requires special verbs, objects or targets, these will all need to be constructed.
* liking comments were reverted to liking the parent after sending item to ↵friendica2013-04-031-4/+3
| | | | another channel
* update manage table and some documentationfriendica2013-03-271-16/+2
|
* rename 'uri' (and parent_uri) to 'mid' (and parent_mid) since these no ↵friendica2013-03-211-125/+125
| | | | longer remotely resemble uri's and are actually message_id's. This change is potentially destabilising because it touches a lot of code and structure. But it has to get done and there's no better time than the present.
* this might make edits update across the wire, or it might notfriendica2013-02-281-0/+166
|
* mail recall - just set mail_flags = mail_flags & MAIL_RECALLED and tell the ↵friendica2013-02-271-0/+15
| | | | notifier. We'll need a special button for this. Also should probably report whether it was seen or not. Will do that another day.
* remove things calling feed_birthday(), so we can remove itfriendica2013-02-261-2/+2
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* moving onfriendica2013-02-181-0/+8
|
* needle/haystack reversalfriendica2013-02-151-1/+1
|
* public scopefriendica2013-02-151-0/+2
|
* implement sender side of public scope setting (public post, network-wide, ↵friendica2013-02-141-2/+36
| | | | site-wide, etc....)
* placeholder comment for public scope requirementfriendica2013-02-141-0/+7
|
* maybe it would work if I didn't put non-existent php vars into the sql.friendica2013-02-111-1/+1
|
* more progresss on tag deliveryfriendica2013-02-111-5/+3
|
* tag notifications now work.friendica2013-02-111-1/+3
|
* progress on tag deliveryfriendica2013-02-111-4/+6
|
* debug tag_deliverfriendica2013-02-101-1/+4
|
* add mimetype to protocol layersfriendica2013-02-101-10/+13
|
* cleanup issues discovered in the logsfriendica2013-02-071-1/+1
|
* work on notificationsfriendica2013-02-061-0/+62
|
* Communication of mention tags were garbledfriendica2013-02-021-1/+1
|
* sort out the rest of the nasty stuff in the attachment/file api - time to ↵friendica2013-02-011-2/+7
| | | | move on to something else
* debugging of file attachment api - somewhat functional but the attachment ↵friendica2013-01-311-2/+2
| | | | info structure in the item table needs to be re-done.
* It's really not supposed to be quite this chatty on the network - ah that's ↵friendica2013-01-281-6/+18
| | | | why. Oops.
* help deletions alongfriendica2013-01-271-0/+4
|
* ensure zot messages with 'deleted' items set 'created' as a fallback to ↵friendica2013-01-261-1/+2
| | | | ensure the message isn't tossed.