| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | hubzilla compatibility function | redmatrix | 2015-06-11 | 1 | -0/+14 |
| | | |||||
| * | asjld work | redmatrix | 2015-06-02 | 1 | -3/+13 |
| | | |||||
| * | bare bones ASLD | redmatrix | 2015-05-31 | 1 | -4/+44 |
| | | |||||
| * | some basic background work for activitystreams-json-ld-2.0 conversions | redmatrix | 2015-05-31 | 1 | -0/+37 |
| | | |||||
| * | there was a reason we included that file | redmatrix | 2015-05-28 | 1 | -3/+3 |
| | | |||||
| * | Merge pull request #332 from solstag/zotfeedcleanup | Klaus | 2015-05-24 | 1 | -3/+1 |
| |\ | | | | | Import security only when necessary, use correct variable in log | ||||
| | * | Import security only when necessary, use correct variable in log | Alexandre Hannud Abdo | 2015-05-22 | 1 | -3/+1 |
| | | | | | | | | | Just some cleanup, seemed like the intent of previous changes was so | ||||
| * | | federation problem from diaspora comments relayed through red channels due ↵ | redmatrix | 2015-05-23 | 1 | -1/+1 |
| |/ | | | | to typo | ||||
| * | cloning abook entries was broken in several ways if the target xchan wasn't ↵ | redmatrix | 2015-05-20 | 1 | -0/+8 |
| | | | | | available on the clone site. This should make it less broken. | ||||
| * | don't allow item_id to update without a valid post id | redmatrix | 2015-05-20 | 1 | -0/+5 |
| | | |||||
| * | PRIVACY: possible privacy leakage under a defined set of circumstances | redmatrix | 2015-05-20 | 1 | -5/+8 |
| | | |||||
| * | product was a bad string to use because we may require it for e-commerce, ↵ | redmatrix | 2015-05-13 | 1 | -1/+1 |
| | | | | | and RED_PLATFORM is equally problematic for other reasons. | ||||
| * | zotfeed issues | friendica | 2015-04-24 | 1 | -3/+3 |
| | | |||||
| * | block unfederated posts from zot_feed | friendica | 2015-04-23 | 1 | -0/+6 |
| | | |||||
| * | issue #176, sender copy of item not obscured if using private mention | friendica | 2015-04-20 | 1 | -1/+3 |
| | | |||||
| * | match parens | friendica | 2015-04-14 | 1 | -1/+1 |
| | | |||||
| * | post_activity_item incorrectly setting the obj_type when a valid type was ↵ | friendica | 2015-04-14 | 1 | -1/+1 |
| | | | | | specified | ||||
| * | Some documentation and whitespaces at line endings. | Klaus Weidenbach | 2015-04-10 | 1 | -159/+232 |
| | | |||||
| * | update features, allow sys account page deletion | friendica | 2015-04-08 | 1 | -0/+5 |
| | | |||||
| * | Correcting reported Doxygen syntax warnings. | Klaus Weidenbach | 2015-03-29 | 1 | -457/+405 |
| | | | | | | | | Fixed wrong Doxygen syntax and add some of the available FIXME to Doxygen documentation. Updated Doxygen configuration to add also all capital letter tags. Adding some more Doxygen documentation. | ||||
| * | remove bogus grouping from fix for #938 | friendica | 2015-03-28 | 1 | -2/+2 |
| | | |||||
| * | issue #938 | friendica | 2015-03-28 | 1 | -2/+8 |
| | | |||||
| * | also allow service classes to set post expiration. These take priority over ↵ | friendica | 2015-03-24 | 1 | -3/+3 |
| | | | | | the site default. | ||||
| * | more work on expiration, make system limits useful - even in retrospect | friendica | 2015-03-24 | 1 | -1/+5 |
| | | |||||
| * | provide a site-wide expiration policy without loopholes - still need work to ↵ | friendica | 2015-03-24 | 1 | -1/+1 |
| | | | | | reduce the impact of expiration queries. | ||||
| * | sql errors on postgres with yestderday's optimisation | friendica | 2015-03-24 | 1 | -2/+2 |
| | | |||||
| * | improve performance of the zotfeed queries | friendica | 2015-03-23 | 1 | -10/+9 |
| | | |||||
| * | some tabs title statuseditor restructuring | Mario Vavti | 2015-03-21 | 1 | -1/+1 |
| | | |||||
| * | The random bad signatures are because something somewhere is trimming the ↵ | friendica | 2015-03-17 | 1 | -2/+2 |
| | | | | | body text. It could be any one of hundreds of functions that touch the message body. We really want to trim the body text, so I'm putting back all the trim statements - in mod/item and item_store and item_store_update. The last fix for random bad sigs noted that one of the trims wasn't there, so the others were removed. The correct fix is for all the trims to be there. We will probably have a few (quite a few) bad sigs during the transition back to trimmed text but this should nail it for anybody on recent code and with new content. | ||||
| * | The never ending saga of parent = 0 bugs on Dreamhost. | friendica | 2015-03-01 | 1 | -0/+10 |
| | | |||||
| * | this may actually fix the deliver loop when deleting existing items. It's ↵ | friendica | 2015-02-25 | 1 | -0/+15 |
| | | | | | hackish but I don't see any other way out. | ||||
| * | Found the cause of the delete looping, and I can prevent it going forward. ↵ | friendica | 2015-02-25 | 1 | -1/+10 |
| | | | | | The issue remains what to do about comments which are already in the DB and have ITEM_ORIGIN incorrectly set. We can't exactly reset them because the "original" context has been lost. (Sorry but couldn't resist an insider pun that none of you will be able to follow anyway). Read the comments. | ||||
| * | call post_local hooks prior to storing a post that is going to be sourced. ↵ | friendica | 2015-02-25 | 1 | -0/+2 |
| | | | | | There are some fields in the actual stored item that may change when we start the second delivery chain so a few plugins may not deal with these items correctly. Since we only source public items these effects will be slight. | ||||
| * | Fixes tag delivery regex for when multiple tags are present | Alexandre Hannud Abdo | 2015-02-13 | 1 | -2/+2 |
| | | | | | | Previous regex would cause matches to span several tags when present, thus never recognizing the mention. | ||||
| * | provide relief to sites that are severely impacted by the slow ITEM_UNSEEN ↵ | friendica | 2015-02-12 | 1 | -5/+4 |
| | | | | | searches. This does not incorporate any other flag optimisations as that will require a major DB update and possibly involve significant downtime. This is just to bite off a little chunk now and provide some much needed relief. | ||||
| * | Dot not trim body in order to avoid issues with signature checks | Alexandre Hannud Abdo | 2015-02-12 | 1 | -2/+2 |
| | | |||||
| * | issue #843 | friendica | 2015-02-11 | 1 | -0/+3 |
| | | |||||
| * | more efficient processing of response activities, plus a proof of concept ↵ | friendica | 2015-02-11 | 1 | -2/+9 |
| | | | | | fix for the problem of receiving a delete notification before we actually get the item which we're supposed to delete. | ||||
| * | item voting tools | friendica | 2015-02-10 | 1 | -2/+2 |
| | | |||||
| * | issue #889 private tags for forums no longer recognised after tag refactor a ↵ | friendica | 2015-02-02 | 1 | -0/+1 |
| | | | | | few weeks back. This solution is not optimal as it also leaves you in the privacy ACL in some cases and not in others but it restores the previous functionality | ||||
| * | remote_user => remote_channel | friendica | 2015-01-28 | 1 | -1/+1 |
| | | |||||
| * | local_user => local_channel | friendica | 2015-01-28 | 1 | -5/+5 |
| | | |||||
| * | limit the number of forums that can be tagged in a single post - default is ↵ | friendica | 2015-01-28 | 1 | -8/+46 |
| | | | | | 2. The reason is simple - count how many posts would be in transit simultaneously if this was unlimited and somebody tagged 40-50 forums. In practice when used legitimately - we've rarely seen more than two, in fact I don't recall seeing more than two ever. Typically it is one and occasionally two. Changing the default is tricky - a client system cannot do it, but the site hosting a forum can choose to. Since not all sites that host forums will choose to do so, the ordering of the mentions would then be important. | ||||
| * | improved route mismatch detection. We will be less strict about the absolute ↵ | friendica | 2015-01-27 | 1 | -33/+20 |
| | | | | | route matching and only look at the last hop before it got to us - which is ultimately all we should care about (since that sender controls the thread permissions). Route mismatches seem to occur somewhat frequently from yamkote (for unknown reasons), and the logging has been improved a bit so it should provide some slightly more useful debugging info in case it still happens going forward. Oh, also we'll set the parent on comments when we store the initial post (item_store()) and only go back and set the parent for top-level posts. This should reduce the number of comments with missing parents on shared hosts, but may increase the number of missing threads. Probably worthwhile to do a query occasionally for parent = 0 and see how we're doing and how many have shared host related delivery issues. | ||||
| * | correct some activity object types (for comments), also fix a foreach ↵ | friendica | 2015-01-14 | 1 | -2/+7 |
| | | | | | warning resulting from recent tag work | ||||
| * | federate consensus items (in network only). Work in progress. | friendica | 2015-01-14 | 1 | -0/+7 |
| | | |||||
| * | check mentions against the appropriate xchan_url and not a hard-coded ↵ | friendica | 2015-01-13 | 1 | -4/+4 |
| | | | | | /channel/ string | ||||
| * | don't wipe out the item body of a linked item to a photo when doing a normal ↵ | friendica | 2015-01-12 | 1 | -7/+18 |
| | | | | | delete and not forced | ||||
| * | change deletion behaviour of linked photo items. Previously deleting the ↵ | friendica | 2015-01-12 | 1 | -28/+12 |
| | | | | | visible item in the conversation deleted the photo as well. Now photos must be deleted in the photos module. Deleting the linked item removes any attached conversation elements (likes, etc.) and sets the conversation item to hidden. This may create an issue in the future if we move the photo tags, title, or other photo elements to the linked item rather than the photo. Noting here so this can potentially be discovered and remembered at that time. | ||||
| * | Refactor mention code to make it more reusable | Stefan Parviainen | 2015-01-12 | 1 | -0/+31 |
| | | |||||
 |
index : volse-hubzilla.git | |
| Volse Hubzilla -- soft fork of main Hubzilla core for Volse | Harald Eilertsen |
| aboutsummaryrefslogtreecommitdiffstats |