aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* when removing a channel, check to see if there are any valid hublocs ↵friendica2014-10-211-4/+17
| | | | | | remaining before marking the xchan deleted. Issue #657
* Merge https://github.com/friendica/red into pending_mergefriendica2014-10-211-1/+1
|\
| * TypoThomas Willingham2014-10-211-1/+1
| |
* | private forum issuesfriendica2014-10-212-1/+3
|/
* strip out the Diaspora quoted reshare markersfriendica2014-10-201-0/+2
|
* Merge pull request #652 from beardy-unixer/masterRedMatrix2014-10-211-1/+13
|\ | | | | Prevent multiple simultaneous pollers.
| * Screwed up merge - put Mike's stuff back.Thomas Willingham2014-10-201-6/+11
| |
| * Prevent more than one instance of the poller running at a time.Thomas Willingham2014-10-201-12/+19
| |
* | bb2diaspora wallwall comment - match both bits (ITEM_WALL|ITEM_ORIGIN)friendica2014-10-201-1/+1
| |
* | move all theme initialisation to one place - just after calling module_init. ↵friendica2014-10-201-0/+1
|/ | | | Revert if there are serious issues, but please note the issues in as much detail as possible so we can work through them.
* don't auto-archive connections we can't poll.friendica2014-10-191-6/+11
|
* show true author of wall-to-wall comments to Diaspora viewers just like we ↵friendica2014-10-191-0/+13
| | | | did for wall-to-wall posts.
* Tried this once before but had to revert. Basically prevent a comment from ↵friendica2014-10-191-1/+7
| | | | being relayed more than once - as it's a huge drain on resources. But last time I tried this, wall-to-wall comments stopped getting relayed. This checkin should do the right thing in both conditions.
* merge madnessfriendica2014-10-192-110/+73
|
* wall-e random signature failuresfriendica2014-10-191-1/+2
|
* mark signature forgeriesfriendica2014-10-162-2/+8
|
* Merge branch 'master' of https://github.com/pafcu/redStefan Parviainen2014-10-164-6/+8
|\
| * jsonp support (thankxs fabrixxm)friendica2014-10-162-2/+5
| |
| * remove log statementfriendica2014-10-151-2/+0
| |
| * missing event permissionsfriendica2014-10-151-1/+2
| |
| * Don't recognise hashtags starting with #, e.g. ###friendica2014-10-151-2/+2
| |
* | Login menuStefan Parviainen2014-10-161-6/+5
|/
* back to wrestling with the !@#$ diaspora recursive reshare from hellfriendica2014-10-141-3/+8
|
* this is the reason Diaspora forum tagging was brokenfriendica2014-10-141-3/+4
|
* if a hubloc primary change results in an xchan primary change, create a ↵friendica2014-10-131-1/+5
| | | | directory update packet.
* figuring out how to bootstrap the change_primary procedure when all you have ↵friendica2014-10-132-0/+6
| | | | is inconsistent data which you think you trust.
* don't use cached datafriendica2014-10-131-0/+2
|
* there's the problemfriendica2014-10-131-2/+2
|
* more diagnostic when changing primaryfriendica2014-10-131-4/+17
|
* this bug has been there for a *long* time. First time I've ever seen it ↵friendica2014-10-131-1/+1
| | | | triggered.
* Merge https://github.com/friendica/red into pending_mergefriendica2014-10-136-180/+224
|\
| * When you delete something in /cloud stay in the right folder.Klaus Weidenbach2014-10-146-180/+224
| | | | | | | | | | | | | | When you deleted a file in /cloud you was always jumped back to /cloud/[channel], now you will stay in the parent folder. Some more doxygen documentation. Removed duplicate data from logging output and reduced logging in RedDAV in general.
* | sqlfriendica2014-10-131-1/+1
| |
* | new function hubloc_change_primary()friendica2014-10-132-3/+60
|/
* diaspora_send_status() - recalculate markdown translation to pickup any ↵friendica2014-10-122-3/+3
| | | | later message changes after original submission like wall-to-wall attributions for instance. Normally this would've come from our cached version which was stored prior to tag_deliver being run and therefore isn't yet aware that wall-to-wall status may have changed after delivery.
* Merge pull request #636 from dawnbreak/RedDAVRedMatrix2014-10-135-924/+981
|\ | | | | Moved classes from reddav.php into own files.
| * Moved classes from reddav.php into own files.Klaus Weidenbach2014-10-125-924/+981
| | | | | | | | | | | | Finished moving classes out from include/reddav.php into own files. Also continued with namespace for RedDAV. Improved some docs and added some todos and fixmes.
* | cleanup of sync_locations and better logging. There was one significant code ↵friendica2014-10-121-7/+11
| | | | | | | | change but it is unrelated to current issues, basically if no primary was set we were setting everything as primary.
* | content deletion issuefriendica2014-10-121-1/+6
|/
* fix diaspora reshare tagsfriendica2014-10-101-0/+2
|
* ah yes, the redundant relay run was for the benefit of wall-to-wall posts ↵friendica2014-10-101-2/+1
| | | | issue #633
* missing source route after editfriendica2014-10-102-1/+3
|
* remove remnants of old signing structure - now using diaspora_metafriendica2014-10-101-7/+0
|
* reset route to parent route on Diaspora comments flowing upstream so they ↵friendica2014-10-101-3/+5
| | | | won't be rejected going downstream
* make sure diaspora comments get the correct routefriendica2014-10-101-0/+4
|
* improvement in source route checking when handling complex *upstream* ↵friendica2014-10-101-6/+19
| | | | delivery chains, which were not adequately accounted for in the earlier checkin.
* allow (our own) ajax urls to pass through bbcode intact.friendica2014-10-093-3/+5
|
* OK this is important. So read it carefully.friendica2014-10-091-3/+33
| | | | | | | | This checkin implements route matching of comments so that they are only accepted from the same route as the top-level post they are attached to. This way there should be no mis-match of permissions between any posts in the thread. It may not be completely compatible with comments posted in the past (though I've tried to be, there may be some minor issues). In addition it seems that relaying was invoked more often than necessary - especially when a duplicate post arrived which was not processed because the edited time hadn't changed - it still invoked relaying. This fix should improve site performance considerably for comments cross-posted to forums; which got bounced around a bit and delivered redundantly for no reason. Roll this back *only* if it causes a meltdown or comment loss is "serious" (as in OMG people are dying, make it stop!). If we can get past 24 hours without serious issue we need to get everybody onto this code. There may be some minor comment loss (mostly affecting new comments to older posts or likes of older comments) until the majority of sites have moved to the new code. It may be difficult or impossible to deliver comments to posts that pre-date the addition of source routes (April 1, 2014) to anybody but the top-level post author at his/her primary hub. We may wish to close comments on these posts, but let's see how we go before doing that.
* allow a site to over-ride the system app list without causing git issuesfriendica2014-10-091-1/+4
|
* return of the missing diaspora wall-to-wall attributionfriendica2014-10-092-12/+12
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-15 13:11:17 +0000