d02529fde1
implement a forced directory update mode where we unconditionally create a directory sync packet. This is needed to ensure that monthly directory pings are propagated to other directory servers so they can each prove for themselves whether or not an account is alive or dead. We do not trust other directories to provide us information beyond "look at this entry and decide for yourself" as doing otherwise would invite rogue directory manipulations. As this scheduled update occurs on all channels across all servers, we should also pick up refresh messages from all existing channel clones and these should also propagate out to all directory servers using the same mechanism (though perhaps not at the same time).
2014-02-11 14:19:20 -08:00
59094cda51
reversed args in update_modtime, incorrect ud_guid and ud_hash
2014-02-10 20:38:26 -08:00
74fb7d158b
Check for the correct DB name before pushing.
2014-02-10 19:20:55 -08:00
7f741a7e85
add channel_notify_flags to list of things which should *not* be synced across nomads. You probably only want one site to send you notification emails for the same events as opposed to all of them.
2014-02-10 19:18:09 -08:00
c7ffae03d8
perform remote discovery on abook sync of nomadic clones if remote channel (xchan) is unknown
2014-02-09 19:45:22 -08:00
14fd940e08
To be listed as a public site, you need to be an https site with a valid cert. If you don't make the cut, you will either not be listed as a public site or you will be de-listed. Period. This is non-negotiable.
2014-02-07 00:50:04 -08:00
c9879edb3e
break delivery loop if an item is deleted twice
2014-01-10 12:37:48 -08:00
196b3022bd
Merge branch 'master' into movejs
...
Conflicts:
version.inc
2014-01-06 02:37:06 -08:00
d920e212ac
typo in import_directory_profile
2014-01-05 15:51:44 -08:00
0c85c97480
move js files from core
2014-01-04 03:58:21 -08:00
152ed96379
issue #230 - deletion failure in multiple delivery chains
2013-12-26 00:14:17 -08:00
fe00e9b261
extend the directory profiles a bit more
2013-12-25 01:57:04 -08:00
b3fe221b7f
issue #240 - we were using htmlentities instead of htmlspecialchars in several places, and this was a bit greedy in the set of characters which were converted from utf-8 to HTML entities. Also brought mail attachments up to date so they are rendered identically to item attachments.
2013-12-11 23:13:36 -08:00
38577cf26c
issue #225
2013-12-05 18:17:16 -08:00
d8903f09f5
include re-organisation and more doco, post_to_red fix ampersands in categories
2013-12-04 00:19:29 -08:00
7187c493e1
add hooks to zot-finger and import_xchan
2013-12-03 17:55:10 -08:00
9f2efb0291
ensure that every imported channel has a primary hubloc
2013-12-02 23:55:57 -08:00
94c293f2c6
doco
2013-11-28 18:46:59 -08:00
eae3327584
item store hooks
2013-11-28 18:10:04 -08:00
8e0d3c2d6f
doco
2013-11-28 17:47:33 -08:00
fafba385c1
only list undeleted hublocs in zot_finger
2013-11-28 16:46:47 -08:00
ff91541cfd
zot doco
2013-11-28 16:13:09 -08:00
64b467ea98
reduce the likelihood that a given channel will have 30-40 valid hublocs with the same hubloc_url.
2013-11-27 02:51:16 -08:00
3e0ac769aa
white screen
2013-11-21 17:23:14 -08:00
4791b2fd9c
add aid to notifiy table which we may need to supress duplicate notify emails across your channels
...
also try to handle the wretched mess of broken and duplicated hublocs that fred.cepheus.uberspace.de typically reports
2013-11-20 21:09:13 -08:00
d7ee552c57
Protocol: now set data['alg'] on all encapsulated encrypted packets, so that we can more easily retire 'aes256cbc' once it is no longer viable.
2013-11-20 15:20:12 -08:00
f8b07e1935
filter out duplicate recipients on local deliveries. We only need to deliver stuff once to any particular channel.
2013-11-17 20:43:50 -08:00
13538cdd21
pull in some posts when we first connect with a new channel (if allowed to) - if not allowed to, do it if that condition changes
2013-11-17 19:22:24 -08:00
06e0272db8
populate some posts when somebody is granted "read stream" permission
2013-11-17 16:50:32 -08:00
613ff90e6a
silence a warning
2013-11-14 19:33:28 -08:00
727e8cc298
don't store update records if we're not a directory server of some kind
2013-11-04 20:43:32 -08:00
2035a5dd76
allow zot public providers to list their location, as a non US-based server could be a strong selling point.
2013-10-30 01:58:45 -07:00
8da4da37cc
access policy and directory mode were crossed on site table creation
2013-10-30 01:30:37 -07:00
ed8f14549f
send rpost requests from remote sites back to yours.
2013-10-29 21:49:10 -07:00
75ba7ae116
rpost bbcode tag
2013-10-29 18:46:51 -07:00
0b0bd3c207
create update record for accounts on directory server itself during profile changes, re-queue failed directory sync packets, fix account_id index in queue creation, be more selective about updating hubloc_connected (only when we're talking to the associated site). But we still need a way to flag dead accounts and these mechanisms won't cut it, because it isn't a requirement that channels communicate with anybody, except for contacting the directory when the account is created. I think we need to make every channel ping the directory once a month. Then we can find those that have not done so (after syncing with other directories). We can't have the directory just flag dead accounts as this would create a way for an anti-social attacker to become a directory server and mark all the accounts dead.
2013-10-24 19:38:50 -07:00
89378fb12a
update even if no change
2013-10-14 22:20:14 -07:00
a13ab4ee9b
sql wrong number of args
2013-10-14 21:09:39 -07:00
e1fb45bc4a
bring back photo shadows (via theme settings)
2013-10-02 22:59:58 -07:00
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
friendica
Olaf Conradi