aboutsummaryrefslogtreecommitdiffstats
path: root/include/conversation.php
Commit message (Collapse)AuthorAgeFilesLines
* revert to prepare_page - but have it call prepare_bodyfriendica2013-11-151-1/+1
|
* allow rpost to set source appfriendica2013-11-151-1/+1
|
* e2ee in comments and a bit of cleanup so not every theme has to define how ↵friendica2013-11-141-3/+0
| | | | to insert bbcode, only if they're doing something special (e.g. this is how to implement a javascript plugin :-)), and I got rid of the predefined http:// in the bbcode for urls. You're almost always pasting a url which already has that bit and it just creates an extra step.
* ability to use other ciphersfriendica2013-11-111-0/+5
|
* e2eefriendica2013-11-101-0/+2
|
* provide expire feature on post and comments as well as private messages. ↵friendica2013-11-071-1/+5
| | | | This requires a feature setting and is currently unmaskable - if the author says it's gone, there's not a lot you can do to stop it or try and save it. It's gone.
* issue #189 - show post edited time on relative date hovertipfriendica2013-10-301-0/+1
|
* Comanche documentation and some cleanup of layout page (including link to ↵friendica2013-10-281-2/+7
| | | | doco) and a few other webpage related cleanups
* remote post module so that from anywhere on the web or at least within the ↵friendica2013-10-271-2/+2
| | | | matrix you'll be able to share content or we can have apps on other sites that post status updates on your wall. All with your permission of course as you'll have to click "share" to actually post it.
* Optionally pass a prepared "top level" item into conversation(). This will ↵friendica2013-10-241-3/+3
| | | | eventually be used by the photos module where the "top level item" of the conversation is a photo with editing and album navigation controls and doesn't look anything like a post.
* link to source - if it's on the display page link to original source ↵friendica2013-10-201-1/+1
| | | | (probably on a different site). All other conversations link to 'llink' which is a local copy and may provide a richer possibility of interactions, especially if you're logged in locally and it's your own copy of the post.
* Put a status editor on the display page if you're logged in. This fixes ↵friendica2013-10-181-1/+1
| | | | issue #113 and also provides the ability to reshare from that page.
* replace a bunch of graphic icons with vector iconsfriendica2013-10-081-1/+1
|
* post signaturesfriendica2013-10-021-0/+7
|
* OK, sure.friendica2013-09-201-1/+1
|
* use prepare_body in api calls to properly render content, add 'mode' to ↵friendica2013-09-161-0/+1
| | | | conversation templates so that themes can use the module context to suppress or show comments as desired
* implement what I hope will now be the server side of directory sync, add ↵friendica2013-09-151-8/+12
| | | | 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.
* provide templating options in comanche for the underlying webpage element - ↵friendica2013-09-041-0/+6
| | | | in this case the way the author is displayed. Leave this open for other forms templating options.
* my badfriendica2013-09-031-1/+1
|
* typofriendica2013-09-031-1/+1
|
* personal config to just show the page content without author info - probably ↵friendica2013-09-031-3/+5
| | | | this needs to be a page option
* add a layout selectorfriendica2013-09-021-0/+12
|
* preserve mimetype on page editsfriendica2013-09-021-4/+5
|
* oh that's whyfriendica2013-09-021-1/+2
|
* fix webpage storagefriendica2013-09-021-1/+1
|
* only allow richtext editor on pages if bbcode is the default mimetype, ↵friendica2013-09-021-6/+6
| | | | otherwise use plaintext editor. This will eventually need work to support a visual editor for html or other types.
* allow a channel owner to define a default mimetype on webpages (otherwise ↵friendica2013-09-021-2/+8
| | | | default to "choose") - also fix the selector w/r/t php code. There is no ui for setting either at the moment, but for instance with wiki pages we probably don't want to have multiple choice of the mimetype. Keep it simple.
* webpage content-type -- needs cleaning up and a security check once all the ↵friendica2013-09-021-0/+8
| | | | important bits are in place.
* more debugging on localize_item top find out why likes are not translated in ↵friendica2013-08-311-1/+7
| | | | notifications, but are in displayed posts (using 'new' on matrix page) - in one case we're successfully pulling stuff from item['object'] and in the other we aren't - and it's the same object.
* silence some warnings at php E_ALL levelsfriendica2013-08-281-0/+2
|
* It's a wretched mess, but at least photo comments show up again when viewing ↵friendica2013-08-281-0/+1
| | | | the photo. This is just temporary until these conversations are merged into the common conversation viewer, so it's not worth spending a lot of time cleaning up the remnants.
* Preparatory work for photo conversations (third time). Also take away unused ↵friendica2013-08-271-7/+12
| | | | "post new activity" preferences until they actually do something.
* more loose endsfriendica2013-08-271-1/+4
|
* extra logging for translating likes in notification emails - which is still ↵friendica2013-08-221-0/+3
| | | | failing on occasion.
* fix superblock for commentsfriendica2013-08-201-0/+14
|
* localize_item() thinks all likes on posts are likes on comments because we ↵friendica2013-08-191-1/+1
| | | | didn't pass any info in the activity object to distinguish them from each other.
* malformed ru string filefriendica2013-08-081-1/+1
|
* convert all stored json calls to json_decode_plus()friendica2013-08-061-2/+2
|
* we've been storing json_encoded structures on disk in several places because ↵friendica2013-08-061-5/+3
| | | | it's a lot easier to parse than xml - but OMG do they get mangled - stored as single quoted strings when escaped as if double quoted. We need to use my new function json_decode_plus() wherever we need to parse one of these babies to make sure we get it right. Maybe we should've just used serialize().
* enotify: localize things we know how to translatefriendica2013-08-051-4/+0
|
* fix some weirdness on the zot feedfriendica2013-07-291-0/+2
|
* remove double tags on search results, updates to install doco to get rid of ↵friendica2013-07-091-12/+0
| | | | Friendica name there and clarify Red requirements.
* fall back on object author/actor if no ownerfriendica2013-06-181-6/+6
|
* Support arbitrary likes - "David likes Bob's bicycle" or "Nancy likes ↵friendica2013-06-181-0/+13
| | | | Margaret's breasts" or whatever... This is a tricky activity to construct. You will need to set the object owner to the owner of the "thing" and the object title to the name of the "thing". The thing liked can include a photo if desired. This will probably have issues working correctly in other activitystreams environments.
* provide support for "bob likes Lisa's channel" activitiesfriendica2013-06-181-17/+32
|
* undo comment policy override - there are a handful of stored posts from the ↵friendica2013-06-181-10/+10
| | | | 17th-June with a broken policy (which won't have a comment box) but it seems to be working for both recent and older posts.
* push refresh messages, performance work on conversations and configs, doc ↵friendica2013-06-141-2/+5
| | | | updates
* missed a few zrl/zmg conversions, like for translate_item and enotify messagesfriendica2013-06-121-25/+26
|
* cleanup localisation of like activitiesfriendica2013-05-281-5/+3
|
* get search page working with live-update and endless scroll, still not ↵friendica2013-05-091-3/+0
| | | | perfect - there may be duplicated content and possibly unauthorised content and 'timeago' not working correctly - will deal with those later, but at least you can see results.