friendica
e64ec31a9d
add the message-id to delivery reports. This _could_ allow an enterprising developer to collect the delivery reports for a given post and store them in a DB table so that the sender could track and verify where a message had been sent on a web page and verify the success or failure of those attempts without requiring admin access. (To be fair this would also need an extra flag which hasn't yet been implemented to indicate that a channel created a second delivery chain of the message).
2014-04-10 22:17:35 -07:00
friendica
bf1f18e172
Include the entire original item when notifying other channels of deletions as it contains important routing and scope information. Previously we were only sending a couple of critical fields like the message-id, flags, and creation date. The thinking was that it is deleted, let's not resend the deleted contents anywhere. But in order to route this through the same path the original post took we really need the entire original post with all of its baggage attached.
2014-04-10 16:14:19 -07:00
friendica
74029a9ee9
this should be better - "xchan deleted" state on remote sites only follows the xchan_flags and not the channel_pageflags; XCHAN_FLAGS_DELETED should only be set if the channel is to be removed from the entire network. As mentioned in a previous commit, channel_pageflags could be set to PAGE_REMOVED but still leave living clones on other sites.
2014-04-07 16:10:43 -07:00
friendica
7e160a7b04
undo one of yesterday's changes - if a channel was deleted we want to mark the hubloc deleted - but not the xchan. The channel might be alive at another hubloc. We should only mark the xchan deleted when removing a channel from the entire network - e.g. there are no hubs left to service it.
2014-04-07 13:13:00 -07:00
friendica
10167fdf51
prevent follows of and notifications to deceased channels
2014-04-07 02:55:00 -07:00
friendica
1108eaaed0
source routing stuff
2014-03-29 21:53:50 -07:00
friendica
a6d8668a5f
try and sort out the item delete mess
2014-03-27 20:28:48 -07:00
friendica
8594d069a1
new connection notification
2014-03-27 18:03:19 -07:00
friendica
ed14c1f224
more work on firehose
2014-03-26 18:45:01 -07:00
friendica
50a7e9ce8f
this should improve queue performance dramatically.
2014-03-24 19:40:36 -07:00
friendica
944d051e45
create_sys_channel during setup bypasses our check when creating the first account that there is a site keypair. Esnure that a site keypair is created before any sys channels are created.
2014-03-23 18:12:32 -07:00
friendica
6d37e41fc3
found what I believe is the root cause of issue #230 , but don't yet have a workable solution. This one is hard.
2014-03-20 22:08:16 -07:00
friendica
1156b141db
increase log info to track down source of ownership failures
2014-03-20 16:45:19 -07:00
friendica
8c177fbc4b
cleanup
2014-03-18 16:50:46 -07:00
friendica
8c7e076dae
bring friends back
2014-03-06 01:29:42 -08:00
friendica
86d60f572f
change flags for one-way connections from hidden to unconnected so we can still use hidden for - well hiding connections
2014-03-04 14:35:42 -08:00
friendica
3d49bf0320
directory sync issues
2014-03-03 21:00:42 -08:00
friendica
7baeb45183
some anomolies found when viewing connections in various cases.
2014-03-02 19:40:59 -08:00
friendica
5b4e3f46bc
minor stuff, some doco, auth cleanup, and make "unknown" more translateable by context.
2014-02-22 14:58:12 -08:00
friendica
8367a92214
fix login weirdness for accounts that need to be approved
2014-02-20 18:38:52 -08:00
friendica
6eb971656e
believe i found the issue which was causing hundreds/thousands of identical hublocs to be created
2014-02-20 01:35:08 -08:00
friendica
70526915c8
several things were not working correctly w/r/t community tagging. The preference vanished from settings at some point, and we also weren't updating the original post timestamp so that the changed taxonomy would propagate correctly as an edit.
2014-02-16 16:04:46 -08:00
friendica
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
friendica
59094cda51
reversed args in update_modtime, incorrect ud_guid and ud_hash
2014-02-10 20:38:26 -08:00
friendica
74fb7d158b
Check for the correct DB name before pushing.
2014-02-10 19:20:55 -08:00
friendica
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
friendica
c7ffae03d8
perform remote discovery on abook sync of nomadic clones if remote channel (xchan) is unknown
2014-02-09 19:45:22 -08:00
friendica
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
friendica
c9879edb3e
break delivery loop if an item is deleted twice
2014-01-10 12:37:48 -08:00
friendica
196b3022bd
Merge branch 'master' into movejs
...
Conflicts:
version.inc
2014-01-06 02:37:06 -08:00
friendica
d920e212ac
typo in import_directory_profile
2014-01-05 15:51:44 -08:00
friendica
0c85c97480
move js files from core
2014-01-04 03:58:21 -08:00
friendica
152ed96379
issue #230 - deletion failure in multiple delivery chains
2013-12-26 00:14:17 -08:00
friendica
fe00e9b261
extend the directory profiles a bit more
2013-12-25 01:57:04 -08:00
friendica
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
friendica
38577cf26c
issue #225
2013-12-05 18:17:16 -08:00
friendica
d8903f09f5
include re-organisation and more doco, post_to_red fix ampersands in categories
2013-12-04 00:19:29 -08:00
friendica
7187c493e1
add hooks to zot-finger and import_xchan
2013-12-03 17:55:10 -08:00
friendica
9f2efb0291
ensure that every imported channel has a primary hubloc
2013-12-02 23:55:57 -08:00
friendica
94c293f2c6
doco
2013-11-28 18:46:59 -08:00
friendica
eae3327584
item store hooks
2013-11-28 18:10:04 -08:00
friendica
8e0d3c2d6f
doco
2013-11-28 17:47:33 -08:00
friendica
fafba385c1
only list undeleted hublocs in zot_finger
2013-11-28 16:46:47 -08:00
friendica
ff91541cfd
zot doco
2013-11-28 16:13:09 -08:00
friendica
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
friendica
3e0ac769aa
white screen
2013-11-21 17:23:14 -08:00
friendica
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
friendica
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
friendica
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
friendica
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
friendica
06e0272db8
populate some posts when somebody is granted "read stream" permission
2013-11-17 16:50:32 -08:00
friendica
613ff90e6a
silence a warning
2013-11-14 19:33:28 -08:00
friendica
727e8cc298
don't store update records if we're not a directory server of some kind
2013-11-04 20:43:32 -08:00
friendica
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
friendica
8da4da37cc
access policy and directory mode were crossed on site table creation
2013-10-30 01:30:37 -07:00
friendica
ed8f14549f
send rpost requests from remote sites back to yours.
2013-10-29 21:49:10 -07:00
friendica
75ba7ae116
rpost bbcode tag
2013-10-29 18:46:51 -07:00
friendica
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
friendica
89378fb12a
update even if no change
2013-10-14 22:20:14 -07:00
friendica
a13ab4ee9b
sql wrong number of args
2013-10-14 21:09:39 -07:00
friendica
e1fb45bc4a
bring back photo shadows (via theme settings)
2013-10-02 22:59:58 -07:00
friendica
78a8d176ac
post signatures
2013-10-02 21:04:48 -07:00
friendica
6e2695f94a
that would've messed it up
2013-10-02 04:13:35 -07:00
friendica
de9aee8a07
block forgeries
2013-10-02 02:50:02 -07:00
friendica
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
friendica
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
Olaf Conradi
0497c441df
ret_secret is not used
2013-09-30 09:59:22 +02:00
friendica
edc5566f79
structure for channel unions
2013-09-26 16:25:28 -07:00
friendica
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
friendica
00e5ded1c8
populate the new fields in the directory updates table
2013-09-24 20:13:53 -07:00
friendica
cdfb5f9dc7
adult channel setting
2013-09-22 20:38:24 -07:00
friendica
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
876a9d1850
missing hash
2013-09-19 21:13:45 -07:00
friendica
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
friendica
a5656c350d
trim commas from keywords
2013-09-19 01:45:06 -07:00
friendica
e4d2e2200e
add "tiered" access policy, add tagcloud to directory pages
2013-09-18 17:47:26 -07:00
friendica
d3aa31be4d
site sellpage links
2013-09-17 22:27:51 -07:00
friendica
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
friendica
4b5d91ccb5
found it
2013-09-15 23:02:18 -07:00
friendica
4decbacda1
more logging
2013-09-15 22:19:24 -07:00
friendica
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
friendica
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
friendica
053893b067
some fixes to directory keyword searches
2013-09-14 17:20:24 -07:00
friendica
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
friendica
cf87653a92
need to figure out what's causing this
2013-09-12 22:50:41 -07:00
friendica
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
friendica
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
Michael Meer
82f4b1767e
delete logger line; was the wrong place.
2013-09-11 14:05:33 +02:00
Michael Meer
2228264772
flag failed auth attempts in DB table hubloc
2013-09-11 13:59:45 +02:00
friendica
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
friendica
5e230edb85
well that really stuffed things up...
2013-09-10 22:45:04 -07:00
friendica
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
Michael Meer
fd540cd596
just a typo
2013-09-09 10:30:37 +02:00
friendica
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
friendica
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
friendica
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
friendica
c8e27b54ec
update hubloc_timestamps
2013-08-27 17:08:59 -07:00
friendica
31b934eb5e
clone sync was trying to update xchan info in the abook loop.
2013-08-26 20:58:07 -07:00
friendica
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
friendica
e9125ce065
try to fix bad addresses that got into the network
2013-08-25 20:17:45 -07:00