aboutsummaryrefslogtreecommitdiffstats
path: root/include/items.php
Commit message (Collapse)AuthorAgeFilesLines
* fix private message encryption since the input_filter mangled itfriendica2013-09-031-2/+2
|
* webpage content-type -- needs cleaning up and a security check once all the ↵friendica2013-09-021-7/+3
| | | | important bits are in place.
* Sheesh. Three lines of Javascript. All you have to do is find which of the ↵friendica2013-09-011-0/+11
| | | | three lines is doing something wrong. Or FILE A BUG. Or use a different browser (not *try* a different browser, *use* a different browser), or turn off freaking tinymce. But no - let's argue about browsers instead.
* get rid of ssl_policy - it's implicit in the site urlfriendica2013-08-271-16/+16
|
* email attachments (and fix email photos)friendica2013-08-191-0/+10
|
* item_store logging to discover where object is getting quote mangled.friendica2013-08-181-1/+4
|
* Another try at issue #61 and #62 - an earlier fix was partially working but ↵friendica2013-08-181-9/+14
| | | | the issue persisted - this extends it a bit.
* don't include archived contacts in public posts, unless specifically requestedfriendica2013-08-151-2/+3
|
* typofriendica2013-08-141-1/+1
|
* fix expire so it actually should expire stuff; and mostly the correct stuff ↵friendica2013-08-141-11/+17
| | | | - though it DOESN'T currently send out notifications to connections
* important bits we need to allow php executable content. These must be ↵friendica2013-08-111-18/+35
| | | | explicitly allowed - but only if the account has ACCOUNT_ROLE_ALLOWCODE and *only* for web pages and profile fields. This content cannot be transmitted to other sites.
* remove some un-needed codefriendica2013-08-071-1320/+10
|
* convert all stored json calls to json_decode_plus()friendica2013-08-061-9/+9
|
* add extra logging to tag_deliverfriendica2013-08-051-2/+6
|
* potentially fixes the "federation" bug w/r/t/ tagged forumsfriendica2013-08-011-2/+2
|
* pass item by reference so title can be alteredfriendica2013-08-011-12/+20
|
* ensure that no unencrypted content leaks through item_store which is private ↵friendica2013-08-011-9/+24
| | | | | | - we typically do this in mod/item, but some functions bypass mod/item to create private posts
* fix some privacy leakage in logsfriendica2013-07-311-0/+15
|
* better mail obscuringfriendica2013-07-311-15/+15
|
* zot feed - getting cut off too earlyfriendica2013-07-291-6/+9
|
* ensure conversation is includedfriendica2013-07-291-0/+1
|
* fix some weirdness on the zot feedfriendica2013-07-291-12/+21
|
* fix bug #84, make imported messages from your clones show up on your wallfriendica2013-07-291-0/+5
|
* tgroup_check wasn't allowing comments through.friendica2013-07-291-2/+9
|
* encrypt private messages on disk - there are still a couple of places where ↵friendica2013-07-281-2/+10
| | | | the text is leaked in the logs during processing.
* make zot_finger more bulletprooffriendica2013-07-211-1/+1
|
* private mail is just a little more private now. Not encrypted and the ↵friendica2013-07-191-5/+20
| | | | | | obfuscation is easily reversible, but not casually readable by browsing logfiles or mysql dumps. This isn't backward compatible - folks will have to upgrade if they can't read their mail.
* add channel_name to delivery logs because it is a bit more useful than an ↵friendica2013-07-151-1/+2
| | | | xchan_hash
* fix some issues that showed up in the logs.friendica2013-07-151-0/+7
|
* Add self to recipient lists. Sure we already have a copy but it's possible ↵friendica2013-07-141-0/+5
| | | | our nomadic channel clones don't.
* some work on issue #62 (comments collapsing on liveupdate), but still a work ↵friendica2013-07-021-3/+0
| | | | | | in progress some work on photo consolidated "view/edit", but still a work in progress
* fix some community tagging bugsfriendica2013-06-301-1/+3
|
* add age to directory profile - requires updating on each birthday and that ↵friendica2013-06-301-0/+1
| | | | part is still missing
* doc update, plus possible fix to "complex delivery chains" issue. Basically ↵friendica2013-06-291-1/+40
| | | | when the top-level post creator replies to a thread he sent to a forum via tags, it isn't getting redelivered to the forum members.
* fix cid queryfriendica2013-06-271-1/+1
|
* community tag issuesfriendica2013-06-201-2/+7
|
* found it - but I'll do some more testing before undoing the bypassfriendica2013-06-161-1/+1
|
* undefined functionfriendica2013-06-161-1/+1
|
* typosfriendica2013-06-161-2/+2
|
* 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