aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* don't include plus-sign in the stored term for imported mentionsfriendica2014-09-101-1/+3
|
* this should be the final piece of the puzzlefriendica2014-09-091-0/+14
|
* cross-network mention issuesfriendica2014-09-091-2/+5
|
* Did I ever mention how much I HATE hacking crypto? If you've got a protocol ↵friendica2014-09-091-1/+12
| | | | doc that says how you sign something, you damm well better sign it that way.
* go through the entire discovery sequence for mentions to make sure we have ↵friendica2014-09-091-1/+9
| | | | the correct URL
* diaspora connections being marked orphan on directory serversfriendica2014-09-091-1/+1
|
* some fixes for auto-perms across networksfriendica2014-09-091-9/+9
|
* reduce log level of inbound d* posts until we get through some of the more ↵friendica2014-09-091-1/+1
| | | | serious federation issues
* and provide a strong hint by showing the errant account_flagsfriendica2014-09-091-5/+5
|
* in case somebody has problems and does an update to try and fix it, put ↵friendica2014-09-091-0/+13
| | | | something in the logs to show what's happening.
* argument order reversed in downgrade_accountsfriendica2014-09-091-2/+2
|
* encode rss message-id's - warning this will double store all existing rss ↵friendica2014-09-091-9/+8
| | | | feed items and probably make a mess of things
* put back old pointerfriendica2014-09-091-1/+1
|
* fix empty reshared contentfriendica2014-09-091-2/+2
|
* doco correctionfriendica2014-09-091-11/+5
|
* syntax error in dba driver, document z_post_urlfriendica2014-09-092-0/+30
|
* if we have php54 don't log the whole damn stack on a db error, just the ↵friendica2014-09-091-2/+5
| | | | current frame
* d* friending vsprintf errorfriendica2014-09-092-2/+4
|
* heavy lifting on diaspora likes. Still needs much more work - especially as ↵friendica2014-09-081-67/+56
| | | | we're ignoring signatures at this time
* prevent red#matrix smilie replacements from tripping over each other.friendica2014-09-081-2/+3
|
* diaspora_like - sql errorfriendica2014-09-081-22/+15
|
* one more timefriendica2014-09-081-2/+3
|
* missed onefriendica2014-09-081-2/+5
|
* 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.