78a8d176ac
post signatures
2013-10-02 21:04:48 -07:00
6e2695f94a
that would've messed it up
2013-10-02 04:13:35 -07:00
de9aee8a07
block forgeries
2013-10-02 02:50:02 -07:00
494090a3b7
in probe diagnostic - note https failure as diagnostic info - this also changes zot_finger so you can tell it not to fallback. This could be useful in corporate environments that are off the grid or other high security situations (as much as anything could be considered high security which relies on SSL).
2013-10-01 22:20:09 -07:00
e992cfeca9
directory sync - this will either work, or it won't work, or it will possibly recurse and blow up the matrix. Hard to say. Do you feel lucky? Well do ya' ... punk? Rule #1 - don't mess with anything unless it's blowing up the matrix. If it doesn't blow up the matrix, but doesn't work, just let it go and let's figure out what it is doing and what it isn't doing.
...
The flow is as follows:
Once a day go out to all the directory servers besides yourself and grab a list of updates. This happens in the poller. If we've never seen them before add them to the updates table. The poller also looks to see if we're a directory server and have updates that haven't yet been processed. It calls onedirsync.php to process each one. If we contact the channel to update and don't find anything (we're just doing a basic zot_finger), set a ud_last timestamp. If this is set we will only try once a day for seven days. Then we stop trying to update.
This will probably cause a spike the first time through because you haven't seen any updates before, but we spread out the load over your delivery interval.
2013-09-30 18:33:27 -07:00
0497c441df
ret_secret is not used
2013-09-30 09:59:22 +02:00
edc5566f79
structure for channel unions
2013-09-26 16:25:28 -07:00
6519433301
suppress creating the directory update record for profile updates which are 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.
2013-09-25 21:22:36 -07:00
00e5ded1c8
populate the new fields in the directory updates table
2013-09-24 20:13:53 -07:00
cdfb5f9dc7
adult channel setting
2013-09-22 20:38:24 -07:00
e6d93b2516
is_commentable() had some major issues when applied to the atrocity known as 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.
2013-09-20 05:45:11 -07:00
876a9d1850
missing hash
2013-09-19 21:13:45 -07:00
54abed8457
provide a "safe search" backend and allow for self-censorship using nsfw or 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.
2013-09-19 19:50:13 -07:00
a5656c350d
trim commas from keywords
2013-09-19 01:45:06 -07:00
e4d2e2200e
add "tiered" access policy, add tagcloud to directory pages
2013-09-18 17:47:26 -07:00
d3aa31be4d
site sellpage links
2013-09-17 22:27:51 -07:00
ff2ada207a
Pieces we'll need to tie together chanman and account/channel deletion and 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?
2013-09-17 20:50:09 -07:00
4b5d91ccb5
found it
2013-09-15 23:02:18 -07:00
4decbacda1
more logging
2013-09-15 22:19:24 -07:00
b3575484c7
don't create a directory sync notification (entry in the updates table) if 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.
2013-09-15 19:04:11 -07:00
129a119c84
implement what I hope will now be the server side of directory sync, add 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.
2013-09-15 03:48:43 -07:00
053893b067
some fixes to directory keyword searches
2013-09-14 17:20:24 -07:00
94417eecba
import_xchan - check every known hubloc/location field and create a new hubloc if anything at all changed anywhere.
2013-09-14 01:56:25 -07:00
cf87653a92
need to figure out what's causing this
2013-09-12 22:50:41 -07:00
3a2d11bde1
so public_recips and allowed_public_recips is working so much better than 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.
2013-09-12 20:11:56 -07:00
ca1b8dbe1e
Merge pull request #129 from MicMee/master
...
to flag failed auth attempts in db table hubloc as hubloc_receive_error
2013-09-12 02:26:56 -07:00
82f4b1767e
delete logger line; was the wrong place.
2013-09-11 14:05:33 +02:00
2228264772
flag failed auth attempts in DB table hubloc
2013-09-11 13:59:45 +02:00
d593b40d9a
assuming this doesn't blow up the internet like the last fix - this is a 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.
2013-09-11 02:03:37 -07:00
5e230edb85
well that really stuffed things up...
2013-09-10 22:45:04 -07:00
3e5414cf35
provide detailed error to remote site for the myriad of things that can go wrong inside item_store(), !! this changes the return of item_store !!
2013-09-10 19:06:06 -07:00
fd540cd596
just a typo
2013-09-09 10:30:37 +02:00
25a5a5ff4d
some alteration to the way directory sync was originally supposed to work. 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.
2013-09-09 01:05:29 -07:00
e11f2a9b02
make sure new contacts who are not yet in the address book are sync'd across clone instances
2013-09-08 20:38:15 -07:00
c65ea0b97b
public site list (will take a few days to populate, assuming folks have updated their site access policy which old sites do not have)
2013-09-05 22:00:06 -07:00
c8e27b54ec
update hubloc_timestamps
2013-08-27 17:08:59 -07:00
31b934eb5e
clone sync was trying to update xchan info in the abook loop.
2013-08-26 20:58:07 -07:00
7a8363c328
more cleanup from the mess yesterday - you might have a look for xchan_addr and hubloc_addr with slashes in them and fix them - especially getting rid of ip addresses and the /channel/xyz in the addr fields
2013-08-26 17:06:19 -07:00
e9125ce065
try to fix bad addresses that got into the network
2013-08-25 20:17:45 -07:00
7546117388
Try to ensure full paths don't leak into xchan_addr and hubloc_addr
2013-08-25 20:11:49 -07:00
141c8ccb1f
possible fix for mention tags not posting to mentioned forum (when send stream permission is blocked)
2013-08-22 05:50:15 -07:00
32ff0932bf
add detailed logging to public recips - find out why some public recipients are getting bypassed (David Benfells' problem with tagging groups, etc.)
2013-08-22 03:24:50 -07:00
5083aa3cbd
implement premium channel discovery
2013-08-21 17:34:04 -07:00
5aa508dba7
don't import any hubloc that doesn't have a sitekey. Eventually we should also verify that it is a valid key, as we've already seen one case where one character got mangled and messed up communication.
2013-08-11 16:16:05 -07:00
24b9799dca
convert all stored json calls to json_decode_plus()
2013-08-06 03:54:49 -07:00
85c7d7165f
yhis should fix the privacy leak - as well as non-private replies to private posts
2013-08-01 14:27:40 -07:00
0d22e1eefb
fix some privacy leakage in logs
2013-07-31 18:57:14 -07:00
7b3c29ebe6
fix bug #84 , make imported messages from your clones show up on your wall
2013-07-29 17:30:46 -07:00
d002ff668a
encrypt private messages on disk - there are still a couple of places where the text is leaked in the logs during processing.
2013-07-28 21:04:03 -07:00
53118a4352
add gz to access denied files to block rotated logs from public access
2013-07-26 03:50:46 -07:00
friendica
Olaf Conradi
Michael Meer