aboutsummaryrefslogtreecommitdiffstats
path: root/include/items.php
Commit message (Collapse)AuthorAgeFilesLines
* issues with diaspora comment signatures on relayed comments that are relayed ↵friendica2014-10-021-4/+6
| | | | through a redmatrix site (parent post is redmatrix) and involve a private post.
* optionally include wall items (posts) in import/exportfriendica2014-09-251-1/+23
|
* TypoThomas Willingham2014-09-251-1/+1
|
* if no rss/atom element author, use feed level contactfriendica2014-09-241-7/+11
|
* make it the defaultfriendica2014-09-241-21/+20
|
* one step closerfriendica2014-09-241-1/+3
|
* more testingfriendica2014-09-241-3/+18
|
* just an experiment - don't do anything with this until I'm finished with it.friendica2014-09-241-0/+9
|
* fix url mismatches of a single trailing slash for feed author/owner ↵friendica2014-09-231-0/+3
| | | | comparisons; update diaspora_compat
* diaspora private mail seems to work now - but there's an obfuscation leak ↵friendica2014-09-231-1/+2
| | | | via the conversation structure that needs to be dealt with.
* feeds with '@' in the URL were being handled as webfinger addresses and ↵friendica2014-09-211-0/+1
| | | | didn't fall through to RSS discovery. Issue #599
* try to sort out walltowall translation for diaspora recipientsfriendica2014-09-191-10/+2
|
* use the more portable encoded_item format for exported items - but with ↵friendica2014-09-161-3/+25
| | | | added attributes so we can use it as a reasonably complete item backup. The encoded_item format gives us extended author and owner information in case we need to probe them to bring the entry back. It also contains taxonomy entries. Importing and/or recovering will best be accomplished in chunks. It could take some time and some memory to chew through this.
* privacy issue - restrictive stream permission setting with a non-targetted ↵friendica2014-09-141-2/+20
| | | | post cannot be enforced on remote networks. Restrict these posts to zot network.
* doc updates and a couple of issues spotted in the logs (diaspora likes, feed ↵friendica2014-09-121-1/+1
| | | | author import)
* correct item author for feeds with multiple or different authorsfriendica2014-09-111-8/+90
|
* encrypt diaspora_meta since it may contain private message contentsfriendica2014-09-101-1/+4
|
* 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
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-14/+14
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* import_profile_photo array warningsfriendica2014-09-081-2/+2
|
* 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 stuff with Diaspora authors to federate in zot conversations even if ↵friendica2014-09-041-0/+17
| | | | the local site has diaspora disabled. This way it won't look like folks are talking to themselves.
* store diaspora meta info in the item table. It has to go there or it will ↵friendica2014-09-031-1/+12
| | | | kill us with complex joins. We can phase out the sign table once this all checks out.
* outbound feed issuefriendica2014-09-031-2/+2
|
* fix phantom attachments in feedsfriendica2014-09-011-1/+1
|
* issue #578 - this won't fix old items but should work going forward. The ↵friendica2014-09-011-1/+1
| | | | extra time slop shouldn't be needed and will in fact result in possibly undesired redundancy.
* get out the sunniesfriendica2014-08-311-1/+1
|
* various rss fixesfriendica2014-08-311-11/+20
|
* doc change - read it.friendica2014-08-301-0/+3
|
* insecure network filterfriendica2014-08-301-1/+40
|
* various diaspora issuesfriendica2014-08-291-2/+48
|
* when updating the commented timestamp on the parent post (item_store) don't ↵friendica2014-08-281-2/+3
| | | | include any time travelling posts. They can mess up the conversation sort order in a big way until they're actually published.
* Ability to close comments at a certain date/time - needed for loom.io ↵friendica2014-08-281-38/+80
| | | | emulation (and many other uses)
* let's make this "specific" since that's what it is.friendica2014-08-281-0/+2
|
* more diaspora stuff - most of the basic bits are there except queueing and ↵friendica2014-08-251-0/+1
| | | | physical delivery (I'm keeping delivery turned off until some of the bugs are fixed so we don't cause inifinite loops or network meltdowns) - now it's just a matter of going through and methodically finding all the bugs
* add "any connections" to can_comment_on_post() - was missingfriendica2014-08-231-0/+1
|
* switch everything over to crypto_encapsulate()friendica2014-08-231-4/+4
|
* issue #573 - this may not fix everything in that issue but should resolve ↵friendica2014-08-221-0/+3
| | | | some of it.
* "false" issuefriendica2014-08-221-4/+9
|
* issue #571 - use feed/nickname?top=1friendica2014-08-221-1/+6
|
* profile edit - missing visibility and drop link on non-default profiles, ↵friendica2014-08-211-4/+4
| | | | re-arrange order of replacing red#matrix smilie so it works correctly, accept a post with body content of '0' which was interpreted by x() as nothing (was treated as integer).
* extensible profiles - add the input form elements. Still needs styling and ↵friendica2014-08-201-135/+99
| | | | we're not yet storing the results. And right now we're ignoring the type and only doing type=string. Oh yeah - and I split off starting the second delivery chain into its own function in tag_deliver since it was largely duplicate code.
* restructure the author and owner info from feedsfriendica2014-08-201-85/+58
|
* greatly simplify consume_feed() - a lot of this was friendica specific and ↵friendica2014-08-201-195/+49
| | | | somebody may want to put some of it back in, but we'd be much better off building a zot compatible feed for friendica (hint,hint) - even if it didn't support the other protocol bits. Special purpose feed handlers for things like likes, dislikes, events, and community tags are better handled as zot arrays. We have all those handlers. We just need to pass them a JSON message instead of an XML/Atom message. Handlers for statusnet follow messages are another casualty. That's easy to bring back - but we need to keep driving nails into the XML coffin or the damn zombies will get out.
* fangs baredfriendica2014-08-191-1/+23
|
* snakebite continuedfriendica2014-08-191-53/+108
|
* also reset comment policy on alternate delivery chainsfriendica2014-08-191-2/+4
|
* make sure privacy scope is completely reset on second delivery chain - ↵friendica2014-08-191-8/+62
| | | | revert if there are forum issues, this is subtle and complicated