aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-0813-33/+34
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* attempt to format diaspora reshares correctly. This might be an iterative ↵friendica2014-09-081-24/+21
| | | | process.
* import_profile_photo array warningsfriendica2014-09-081-2/+2
|
* add categories to eventsfriendica2014-09-071-0/+24
|
* support the recent (2 years ago) changes to diaspora photo embedsfriendica2014-09-061-0/+6
|
* extra_query_args() restricted to $_GET only. $_REQUEST was adding cookies ↵friendica2014-09-061-4/+5
| | | | and this is undesired and potentially a security issue.
* ajax workfriendica2014-09-061-0/+14
|
* illegal string offset warningsfriendica2014-09-051-1/+1
|
* improved logging if you're using php54 or laterfriendica2014-09-041-2/+8
|
* issue #451 - clear gid and cid from network tab if discover is selectedfriendica2014-09-041-7/+7
|
* bb2diaspora_itembody - empty body, that explains a lotfriendica2014-09-041-0/+2
|
* fix the client side of pocofriendica2014-09-041-11/+20
|
* import_author_rss not succeeding, missing urlfriendica2014-09-041-4/+5
|
* unset item_nocomment when starting a new delivery chainfriendica2014-09-041-1/+8
|
* oops forgot about the privacy exclusionfriendica2014-09-041-4/+5
|
* allow feeds to be sourcedfriendica2014-09-041-1/+1
|
* realm detection logic reversedfriendica2014-09-041-1/+1
|
* allow stuff with Diaspora authors to federate in zot conversations even if ↵friendica2014-09-043-1/+24
| | | | the local site has diaspora disabled. This way it won't look like folks are talking to themselves.
* sort out some of the bb2d madnessfriendica2014-09-032-70/+27
|
* this is turning into a wretched mess. It's going to get worse before it gets ↵friendica2014-09-032-200/+99
| | | | better, but I'm trying to do this incrementally so I don't break the whole shebang for a few days. It will get better once all the bbcode translation is done in a single place (cross fingers), and we can just sign the post once when we submit it and be done with it. If Diaspora ever implements editing of existing posts we'll have to go back and do the whole wretched mess over again.
* implement service class for feed polling frequenecy, fixed a service class ↵friendica2014-09-033-89/+91
| | | | bug, moved service class stuff from plugin to account.php where it belongs and load that by default instead of on demand
* store diaspora meta info in the item table. It has to go there or it will ↵friendica2014-09-033-44/+50
| | | | kill us with complex joins. We can phase out the sign table once this all checks out.
* outbound feed issuefriendica2014-09-032-4/+4
|
* fix diaspora_handle_from_contact()friendica2014-09-021-2/+2
|
* if we don't have a stored diaspora author signature which has been passed ↵friendica2014-09-021-0/+1
| | | | the baton since the post's creation, fill in the field with their redmatrix signature. It's pointless, but there's so much pointless stuff in here that I doubt it matters. From what I can ascertain - nobody is going to look at it anyway.
* try to proceed with a diaspora relayable even if we don't have the original ↵friendica2014-09-021-7/+9
| | | | author's signature.
* provide a config option to prevent wall uploads (photos and files) from ↵friendica2014-09-021-30/+0
| | | | being set to the same ACL as the containing post, and instead are uploaded with public visibility (no ACL). This is to prevent folks on other networks from seeing prohibited signs for things uploaded into a private conversation. It is primarily useful when posting to collections that have mixed folks from red and other networks and an otherwise public (typical) profile. Consequently, these uploads will match your chosen default visibility for photos and storage and not that of the containing conversation item (and is only useful if the default visibility is public). This choice must be explained adequately because it represents a complex series of tradeoffs and side effects. It will reduce complaints from other networks about blocked content, but essentially forces you to use another method (dav or the photos page) if you wish to upload protected files/media.
* feed removal issuefriendica2014-09-022-6/+8
|
* use feed title for channel name before checking author, make feed items ↵friendica2014-09-023-8/+37
| | | | shareable (they're private to the channel so they won't be shown in searches), try and handle Diaspora mentions a bit more elegantly. (Bug: we don't convert mentions to Diaspora's format on outbound at all!)
* minor nitsfriendica2014-09-011-4/+8
|
* fix phantom attachments in feedsfriendica2014-09-012-2/+2
|
* logic invertedfriendica2014-09-011-1/+1
|
* issue #578 - this won't fix old items but should work going forward. The ↵friendica2014-09-012-2/+2
| | | | extra time slop shouldn't be needed and will in fact result in possibly undesired redundancy.
* Merge remote-tracking branch 'upstream/master'Thomas Willingham2014-09-029-66/+276
|\
| * use feed icon as default avatar for rss connectionsfriendica2014-09-012-3/+6
| |
| * honour the feed_contacts settingfriendica2014-09-011-0/+5
| |
| * get out the sunniesfriendica2014-08-314-7/+32
| |
| * various rss fixesfriendica2014-08-312-11/+25
| |
| * service class check for feeds. Note limit is account based, not channel based.friendica2014-08-311-21/+33
| |
| * rss feed discoveryfriendica2014-08-312-25/+178
| |
| * sql error in profile_activityfriendica2014-08-312-5/+3
| |
* | Add check_upstream_directory() to check that your directory is stillThomas Willingham2014-08-312-0/+23
|/ | | | | a directory, and if it isn't, let find_upstream_directory() find you a new one.
* doc change - read it.friendica2014-08-301-0/+3
|
* insecure network filterfriendica2014-08-301-1/+40
|
* various diaspora issuesfriendica2014-08-294-22/+76
|
* more queue tweaksfriendica2014-08-282-2/+2
|
* the queue driver is universal now - we don't need to filter it.friendica2014-08-281-1/+1
|
* lots of little Diaspora issuesfriendica2014-08-284-10/+46
|
* remove noisy log statementfriendica2014-08-281-2/+0
|
* when updating the commented timestamp on the parent post (item_store) don't ↵friendica2014-08-282-2/+5
| | | | include any time travelling posts. They can mess up the conversation sort order in a big way until they're actually published.