Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | ret_secret is not used | Olaf Conradi | 2013-09-30 | 1 | -5/+0 |
| | |||||
* | structure for channel unions | friendica | 2013-09-26 | 1 | -1/+2 |
| | |||||
* | suppress creating the directory update record for profile updates which are ↵ | friendica | 2013-09-25 | 1 | -4/+4 |
| | | | | part of the normal import_xchan sequence - otherwise we get two for every change. Create it normally if we are called with a profile_update message and don't go through the whole import_xchan thing. | ||||
* | populate the new fields in the directory updates table | friendica | 2013-09-24 | 1 | -9/+17 |
| | |||||
* | adult channel setting | friendica | 2013-09-22 | 1 | -0/+7 |
| | |||||
* | is_commentable() had some major issues when applied to the atrocity known as ↵ | friendica | 2013-09-20 | 1 | -1/+4 |
| | | | | | | ConversationObject, hopefully this won't destabilise the network as it's a somewhat major permission tweak related to comments; also add any local clones to allowed_public_recips() as they should always be allowed recipients. Not sure what to do about host permissions in the event of clones. They have more than one host, and it isn't spelled out in the sent message. All of this stuff will make your head hurt. | ||||
* | missing hash | friendica | 2013-09-19 | 1 | -1/+2 |
| | |||||
* | provide a "safe search" backend and allow for self-censorship using nsfw or ↵ | friendica | 2013-09-19 | 1 | -0/+10 |
| | | | | adult profile keywords. Eventually the directories will be forced to mark adult profiles and sync this knowledge between them. At the moment there's no way to do an unsafe search, but we really just need a checkbox and pass the value through directory to dirsearch on the back end, and some will want this as a pconfig. | ||||
* | trim commas from keywords | friendica | 2013-09-19 | 1 | -0/+1 |
| | |||||
* | add "tiered" access policy, add tagcloud to directory pages | friendica | 2013-09-18 | 1 | -0/+2 |
| | |||||
* | site sellpage links | friendica | 2013-09-17 | 1 | -4/+8 |
| | |||||
* | Pieces we'll need to tie together chanman and account/channel deletion and ↵ | friendica | 2013-09-17 | 1 | -0/+10 |
| | | | | | | | | directory sync. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. Please do not mess with any of this. OK? Understood? | ||||
* | found it | friendica | 2013-09-15 | 1 | -3/+3 |
| | |||||
* | more logging | friendica | 2013-09-15 | 1 | -0/+3 |
| | |||||
* | don't create a directory sync notification (entry in the updates table) if ↵ | friendica | 2013-09-15 | 1 | -17/+30 |
| | | | | the site record was updated - without checking first to see if anything changed. This is causing lots of sync entries when nothing changed to warrant it. | ||||
* | implement what I hope will now be the server side of directory sync, add ↵ | friendica | 2013-09-15 | 1 | -5/+12 |
| | | | | viewsrc to item_photo_menu, and log what changed in import_xchan update objects so we can find out why there are so many updates when nothing _obvious_ has changed that should trigger it. | ||||
* | some fixes to directory keyword searches | friendica | 2013-09-14 | 1 | -1/+1 |
| | |||||
* | import_xchan - check every known hubloc/location field and create a new ↵ | friendica | 2013-09-14 | 1 | -4/+8 |
| | | | | hubloc if anything at all changed anywhere. | ||||
* | need to figure out what's causing this | friendica | 2013-09-12 | 1 | -0/+6 |
| | |||||
* | so public_recips and allowed_public_recips is working so much better than ↵ | friendica | 2013-09-12 | 1 | -4/+12 |
| | | | | before, but was still not quite right. We seem to be getting all the right results for top-level posts now, but comments aren't getting through on channels for which we've allowed them to send us their stream, but not comment on our posts. The reason is we were seeing if they could comment - and we only need to do that if we own the post. If they own the post, we only need to check if they can send us their stream. | ||||
* | Merge pull request #129 from MicMee/master | friendica | 2013-09-12 | 1 | -1/+2 |
|\ | | | | | to flag failed auth attempts in db table hubloc as hubloc_receive_error | ||||
| * | delete logger line; was the wrong place. | Michael Meer | 2013-09-11 | 1 | -1/+0 |
| | | |||||
| * | flag failed auth attempts in DB table hubloc | Michael Meer | 2013-09-11 | 1 | -1/+3 |
| | | |||||
* | | assuming this doesn't blow up the internet like the last fix - this is a ↵ | friendica | 2013-09-11 | 1 | -1/+1 |
|/ | | | | very old bug that's been reported time and time again and nobody every bothered to debug or even report it somewhere where we could monitor it. It's buried somewhere in my stream, but basically is "things don't work right if you've got 'everybody in my address book' permissions" on "can send me their channel stream and posts". I think this is Michelle's problem and anybody else who has en empty matrix after making lots of connections. | ||||
* | well that really stuffed things up... | friendica | 2013-09-10 | 1 | -2/+2 |
| | |||||
* | provide detailed error to remote site for the myriad of things that can go ↵ | friendica | 2013-09-10 | 1 | -4/+8 |
| | | | | wrong inside item_store(), !! this changes the return of item_store !! | ||||
* | just a typo | Michael Meer | 2013-09-09 | 1 | -1/+1 |
| | |||||
* | some alteration to the way directory sync was originally supposed to work. ↵ | friendica | 2013-09-09 | 1 | -25/+14 |
| | | | | I'm making this up as I go and not exactly certain where to go next but it makes more sense now and I think the basic idea will actually work. I'll just have to keep making it up until it does work. | ||||
* | make sure new contacts who are not yet in the address book are sync'd across ↵ | friendica | 2013-09-08 | 1 | -0/+14 |
| | | | | clone instances | ||||
* | public site list (will take a few days to populate, assuming folks have ↵ | friendica | 2013-09-05 | 1 | -3/+16 |
| | | | | updated their site access policy which old sites do not have) | ||||
* | update hubloc_timestamps | friendica | 2013-08-27 | 1 | -5/+14 |
| | |||||
* | clone sync was trying to update xchan info in the abook loop. | friendica | 2013-08-26 | 1 | -1/+1 |
| | |||||
* | more cleanup from the mess yesterday - you might have a look for xchan_addr ↵ | friendica | 2013-08-26 | 1 | -0/+3 |
| | | | | and hubloc_addr with slashes in them and fix them - especially getting rid of ip addresses and the /channel/xyz in the addr fields | ||||
* | try to fix bad addresses that got into the network | friendica | 2013-08-25 | 1 | -0/+3 |
| | |||||
* | Try to ensure full paths don't leak into xchan_addr and hubloc_addr | friendica | 2013-08-25 | 1 | -1/+1 |
| | |||||
* | possible fix for mention tags not posting to mentioned forum (when send ↵ | friendica | 2013-08-22 | 1 | -3/+25 |
| | | | | stream permission is blocked) | ||||
* | add detailed logging to public recips - find out why some public recipients ↵ | friendica | 2013-08-22 | 1 | -0/+3 |
| | | | | are getting bypassed (David Benfells' problem with tagging groups, etc.) | ||||
* | implement premium channel discovery | friendica | 2013-08-21 | 1 | -5/+14 |
| | |||||
* | don't import any hubloc that doesn't have a sitekey. Eventually we should ↵ | friendica | 2013-08-11 | 1 | -2/+7 |
| | | | | also verify that it is a valid key, as we've already seen one case where one character got mangled and messed up communication. | ||||
* | convert all stored json calls to json_decode_plus() | friendica | 2013-08-06 | 1 | -2/+2 |
| | |||||
* | yhis should fix the privacy leak - as well as non-private replies to private ↵ | friendica | 2013-08-01 | 1 | -0/+1 |
| | | | | posts | ||||
* | fix some privacy leakage in logs | friendica | 2013-07-31 | 1 | -14/+0 |
| | |||||
* | fix bug #84, make imported messages from your clones show up on your wall | friendica | 2013-07-29 | 1 | -0/+12 |
| | |||||
* | encrypt private messages on disk - there are still a couple of places where ↵ | friendica | 2013-07-28 | 1 | -6/+17 |
| | | | | the text is leaked in the logs during processing. | ||||
* | add gz to access denied files to block rotated logs from public access | friendica | 2013-07-26 | 1 | -1/+2 |
| | |||||
* | the rest of the heavy lifting on clone sync - now we're down to some log ↵ | friendica | 2013-07-25 | 1 | -1/+82 |
| | | | | messages and a whole lot of testing | ||||
* | build_sync_packet was looking at stale channel info - load it fresh from the DB. | friendica | 2013-07-25 | 1 | -1/+8 |
| | |||||
* | log the sync packets locally at LOGGER_DATA level | friendica | 2013-07-25 | 1 | -0/+2 |
| | |||||
* | more work on clone sync | friendica | 2013-07-25 | 1 | -0/+101 |
| | |||||
* | fix media uploads in api (specifically friendica for android) | friendica | 2013-07-25 | 1 | -34/+0 |
| |