friendica
0e4f318b71
php warnings
2014-11-02 19:22:18 -08:00
friendica
285d6f61e4
I'm going to try again with the conversation request packets. I've looked this over and tested a lot of edge cases, and thought about from every angle I can think of to prevent looping. I don't *think* this can loop. I also doubt that this is the problem at friendicared.de, but I don't know for sure what that problem might be.
2014-11-02 15:28:20 -08:00
friendica
4274a2d06c
add some more safety checks before turning the conversation request messages back on
2014-11-02 00:06:52 -07:00
friendica
50c16c394f
check that we have valid data
2014-11-01 01:52:27 -07:00
friendica
a659ac8952
disable request message response until we work through this
2014-11-01 00:36:21 -07:00
friendica
1cb45c30e9
document request packets a bit more
2014-10-31 06:24:14 -07:00
friendica
5637d07138
flag notify packets that are sent in response to a message_id request and prevent them from recursing
2014-10-31 04:59:30 -07:00
friendica
28a35261db
What this checkin does is catch the case where a comment arrived and there's a missing top-level post to match it with. So we'll send a request back to the sender that you've never seen this thread and please send a fresh copy of the entire conversation to date. We could soon have posts in the matrix from different platforms from days gone by, which have been migrated into the modern world. We'll be polite and not deliver these to everybody. However, if someone comments on one of these antique threads we wouldn't be able to see it in our own matrix because we won't have a copy of the parent post. So this rectifies that situation. Be aware that item deletion may need to change to keep "hard deleted" items indefinitely so that they don't keep coming back. We'll have to null out the important data of the former item to accomplish the deletion aspect.
2014-10-30 19:15:03 -07:00
friendica
fd492386bf
Tried this once before but had to revert. Basically prevent a comment from 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.
2014-10-19 17:31:10 -07:00
friendica
903f7e73fb
if a hubloc primary change results in an xchan primary change, create a directory update packet.
2014-10-13 21:44:46 -07:00
friendica
0057612a9f
figuring out how to bootstrap the change_primary procedure when all you have is inconsistent data which you think you trust.
2014-10-13 21:38:36 -07:00
friendica
19e1b95837
don't use cached data
2014-10-13 21:01:51 -07:00
friendica
bd4dd85fbb
there's the problem
2014-10-13 20:53:34 -07:00
friendica
1b0390af06
new function hubloc_change_primary()
2014-10-13 15:27:56 -07:00
friendica
718bea5d45
cleanup of sync_locations and better logging. There was one significant code change but it is unrelated to current issues, basically if no primary was set we were setting everything as primary.
2014-10-12 15:18:49 -07:00
friendica
f26cd5a636
ah yes, the redundant relay run was for the benefit of wall-to-wall posts issue #633
2014-10-10 15:17:32 -07:00
friendica
b5f91d7b40
missing source route after edit
2014-10-10 14:45:18 -07:00
friendica
cde244ef74
improvement in source route checking when handling complex *upstream* delivery chains, which were not adequately accounted for in the earlier checkin.
2014-10-10 00:13:46 -07:00
friendica
4634049549
allow (our own) ajax urls to pass through bbcode intact.
2014-10-09 20:59:33 -07:00
friendica
effc8960c3
OK this is important. So read it carefully.
...
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.
2014-10-09 18:12:53 -07:00
friendica
467c6c72f0
ability to pre-populate connections for new channels. e.g. "MySpace Tom"
2014-10-01 14:48:08 -07:00
friendica
b735961560
found the sucker
2014-09-22 16:23:59 -07:00
friendica
c4608d4c82
just mark dead hubloc deleted - don't remove them. This could cause problems. Also clean up fetch_url/post_url header option
2014-09-16 19:07:19 -07:00
friendica
bbc9e4427e
honour service class restrictions for total_identities, total_channels ("friends") and total_feeds both when importing channels and subsequently when syncing clones. Limits are based on the local system - additional entries are silently dropped.
2014-09-15 17:17:00 -07:00
friendica
0dc33900b6
provide a way to sync locations and get rid of bogus hublocs, now implemented
2014-09-14 22:19:19 -07:00
friendica
bcc9057d8c
pull the plug on the old location sync section of import_xchan - this has now been split off into its own function. Cross fingers because this is core functionality which was tried and true, well tested; and now it's a bit different.
...
Please revert this if the matrix breaks in the next few hours.
2014-09-14 18:09:16 -07:00
friendica
c27b60d981
more heavy lifting on the hubloc management and revocation infrastructure; don't rush me. This is going to become a fundamental part of zot. It deserves careful consideration.
2014-09-14 01:48:54 -07:00
friendica
0350b76d85
some backend work for the remaining missing bits of mod_hubman - this is still a fair ways from being complete and is not ready for prime time. Basically we'll let a channel send out a public message saying "these are my currently approved locations" and anything that isn't in the list will be marked deleted. We'll send out this message when locations change somehow - either through direct personal involvement (hub revoke, change primary, channel import) or during a system rename or "find bad/obsolete hublocs" activity. This way we won't have clones sending back location info we just got rid of and re-importing the bad entries.
2014-09-13 16:00:09 -07:00
friendica
e68185fc05
don't allow an xchan to be imported with an empty name. To avoid translation issues we'll just make it '-'.
2014-09-11 18:11:07 -07:00
friendica
c6d07feff5
This is long overdue - use a symblic constant NULL_DATE instead of the easily mis-typed sequence '0000-00-00 00:00:00'
2014-09-08 20:35:15 -07:00
friendica
1102499c71
realm detection logic reversed
2014-09-04 16:09:52 -07:00
friendica
2d0ad0625a
sql error in profile_activity
2014-08-31 16:24:05 -07:00
friendica
8a62b824f9
lots of little Diaspora issues
2014-08-28 21:49:13 -07:00
friendica
6a42d6fe3b
works one way sort of - now to go the other way - which will require fixing a whole slew of FIXMEs
2014-08-26 18:58:48 -07:00
friendica
eb8f194419
sort out some anomalies
2014-08-25 21:42:46 -07:00
friendica
9196c9eef0
We really can't do this without a hubloc. I was hoping we could, but notifier is setup to take hublocs, not xchans.
2014-08-22 21:37:08 -07:00
friendica
69d3e5468d
provide the site blacklist everywhere it is needed
2014-08-21 21:07:32 -07:00
friendica
4a76925787
some more work on realms
2014-08-17 19:06:56 -07:00
friendica
82eb265a20
add collections widget to connections page - and some more work on realms
2014-08-17 17:48:41 -07:00
friendica
20bdcb037f
provide backend storage and declaration of directory realm
2014-08-16 16:10:35 -07:00
zottel
d57fe0765c
don't block "public" messages with authenticated scope
2014-08-15 21:36:24 +02:00
friendica
802a5c2946
zot logging to figure out why we occasionally don't have an address on xchan_import - I suspect we don't have anything useful at all.
2014-08-12 20:46:33 -07:00
friendica
ad1472abf0
got the logic reversed on that one
2014-08-07 18:58:33 -07:00
friendica
f412f6a654
over-ride the private flag if we received a post that isn't completely public, but they didn't set the private flag.
2014-08-07 17:49:57 -07:00
friendica
2cff122d6f
public scope delivery issues
2014-08-06 21:16:24 -07:00
friendica
8da548344b
clone sync of "unfriend" actions
2014-08-05 17:47:17 -07:00
friendica
5a5190f2ff
add an encoding type to formatted zot communication structures so that we can later add alternate encodings.
2014-07-24 15:55:01 -07:00
friendica
9e988afa1f
ensure that we don't have permission settings issues due to version skew across sites.
2014-07-17 20:59:58 -07:00
friendica
437b0cb16e
collection sync issue
2014-07-17 15:53:07 -07:00
friendica
feb23fc9bc
collection sync
2014-07-16 21:18:28 -07:00
friendica
01491e7d61
limit fields to what we require
2014-07-14 21:52:20 -07:00
friendica
c398d556b3
index collection sync info by hash rather than id
2014-07-14 21:49:48 -07:00
friendica
1accf82bd1
clean up more code duplication
2014-07-14 21:21:24 -07:00
friendica
5ad76c4d0c
the sending side of clone syncing of collection/privacy_group information. The receiving side is not yet implemented.
2014-07-14 02:37:41 -07:00
friendica
b2abc51929
much better fix to problem yesterday of updates with the wrong ud_addr getting updated. Now we'll
...
pass in the update table row to import_xchan so we know exactly which ud_addr applies. We still need ud_flags passed in separately.
2014-06-30 21:17:19 -07:00
friendica
f64f84b5e9
control chars crept in.
2014-06-30 03:52:20 -07:00
friendica
71e8643bf6
ensure we have a unique guid for each address if one is generated.
2014-06-30 03:38:12 -07:00
friendica
4e8d10e269
update the update records for all addresses attached to this channel, not just the primary.
2014-06-30 03:34:37 -07:00
Alexandre Hannud Abdo
b20887995a
Implements a new permission level PERMS_PENDING
...
With this a user can allow some action to any user which connects
to them, even before they've connected back.
Ref.
https://mobiliza.org.br/display/478d9e71eaf55748dc646d3990651d6d34cfb7db5c38360538ec730ca3ccf908@zothub.com
Also some code cleanup and an alternative logic for handling
notifications of permission changes in zot.php.
This assumes that private posts are still restricted to people in
your addressbook. Regardless of your global permissions, a
pending channel won't get private posts, even if the post
only has a deny clause not matching the pending channel.
2014-06-19 15:13:32 -03:00
friendica
5c8359f976
note work still remaining
2014-06-17 17:36:41 -07:00
friendica
dafd3a9e43
sync profiles to nomadic clones
2014-06-17 17:34:51 -07:00
friendica
78609e9363
send new connection notification even if auto-perms are set
2014-06-12 17:31:42 -07:00
friendica
4fa3b420ab
duplicate birthday events showing up
2014-06-04 21:02:57 -07:00
friendica
2386bc4d00
bring back birthdays
2014-06-02 17:49:19 -07:00
friendica
9b5eabf108
Merge branch 'master' into newevent
...
Conflicts:
include/zot.php
2014-05-29 16:14:10 -07:00
friendica
2a6d7b6a07
cleanup dead directory entries. This was a real b#tch, so keep your eye out for issues - which you shouldn't see until next weekend when this is scheduled to run. We're only setting flags, so if anything goes wrong we should be able to recover without too much pain.
2014-05-28 21:42:46 -07:00
friendica
2f5bd7e1b3
add activity_received hook
2014-05-13 20:58:55 -07:00
friendica
1a4c99ec02
fix events until the new event subscription mechanism goes in, as shared events have been broken
2014-05-07 22:28:19 -07:00
friendica
a00103b7df
better event management
2014-05-07 22:23:43 -07:00
friendica
e22e94cd97
ok *now* shred works with alternate config files
2014-05-07 20:31:21 -07:00
friendica
769b0f6bc9
Often somebody will join the matrix with a dodgy cert and we'll sort that out but their profile photo will remain rainbow man (or the site default). However the photo_date has been updated so we won't try again. This checkin looks for such a failure and leaves the photo_date alone if the photo import failed.
2014-04-13 18:30:06 -07:00
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
friendica
7546117388
Try to ensure full paths don't leak into xchan_addr and hubloc_addr
2013-08-25 20:11:49 -07:00
friendica
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
friendica
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
friendica
5083aa3cbd
implement premium channel discovery
2013-08-21 17:34:04 -07:00
friendica
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
friendica
24b9799dca
convert all stored json calls to json_decode_plus()
2013-08-06 03:54:49 -07:00
friendica
85c7d7165f
yhis should fix the privacy leak - as well as non-private replies to private posts
2013-08-01 14:27:40 -07:00
friendica
0d22e1eefb
fix some privacy leakage in logs
2013-07-31 18:57:14 -07:00
friendica
7b3c29ebe6
fix bug #84 , make imported messages from your clones show up on your wall
2013-07-29 17:30:46 -07:00
friendica
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
friendica
53118a4352
add gz to access denied files to block rotated logs from public access
2013-07-26 03:50:46 -07:00
friendica
7f87da68ba
the rest of the heavy lifting on clone sync - now we're down to some log messages and a whole lot of testing
2013-07-25 22:57:06 -07:00
friendica
e822ab65d7
build_sync_packet was looking at stale channel info - load it fresh from the DB.
2013-07-25 20:10:53 -07:00
friendica
65c8100948
log the sync packets locally at LOGGER_DATA level
2013-07-25 19:50:55 -07:00
friendica
3d95fcb7cd
more work on clone sync
2013-07-25 16:00:04 -07:00
friendica
e45beccd5b
fix media uploads in api (specifically friendica for android)
2013-07-25 05:04:52 -07:00
friendica
9288c2e636
start saving site info
2013-07-23 22:33:56 -07:00
friendica
05612a8a77
make zot_finger more bulletproof
2013-07-21 22:39:21 -07:00
friendica
4680a818ea
improve logging zot_finger
2013-07-21 21:54:20 -07:00
friendica
9f1fa5aba2
improvements in delivery logging
2013-07-21 17:19:16 -07:00
friendica
4aff3d4217
validate input to import_xchan(), as we don't consistently check it prior to entering this function
2013-07-18 18:22:08 -07:00
friendica
4de52e601c
add channel_name to delivery logs because it is a bit more useful than an xchan_hash
2013-07-15 19:04:23 -07:00
friendica
f384695e3d
more diagnostics
2013-07-15 03:12:51 -07:00
friendica
9e28318e4d
more error checking
2013-07-14 20:42:06 -07:00
friendica
75af9b8cd1
more logging on hubloc import - figure out why it did not get stored.
2013-07-14 18:32:20 -07:00
friendica
6e012839c9
more work on bug #59 - hope this doesn't hork everything. Also some tweaking of the theme for the new radius control, which produced some surprising results when expert mode was toggled.
2013-07-08 22:01:57 -07:00
friendica
fd74c5b2ce
really, truly fix the age missing in directory bug
2013-07-02 22:41:17 -07:00
friendica
2ecd5a7632
missing comma
2013-07-02 22:29:24 -07:00
friendica
23d7eab761
age was not syncing to the directory
2013-07-02 22:22:13 -07:00
friendica
b86253c655
issue #65
2013-07-01 19:41:11 -07:00
friendica
72f6edd595
add age to directory profile - requires updating on each birthday and that part is still missing
2013-06-30 00:38:02 -07:00
friendica
b9466941e7
more work on channel sync
2013-06-26 17:31:02 -07:00
friendica
5e235fba78
make manual image scaling work - even if auto scaling kicks in.
2013-06-23 23:13:07 -07:00
friendica
2971ee9a4c
hopefully this won't screw up everything - if it does, revert. Otherwise this should work at delivery time to check tag deliveries and bounce the message before it's stored if the channel doesn't allow you to post and you aren't allowed to tag deliver either. Previously this was handled after the post was already stored so you needed posting permission as well as tag deliver permission to get past the checks.
2013-06-16 00:57:39 -07:00
friendica
1f921a51ae
typo in auto permissions
2013-05-19 20:16:05 -07:00
friendica
75461355ff
extend delivery reports to mail
2013-05-16 20:43:24 -07:00
friendica
cb0a90d628
small updates
2013-05-08 21:30:54 -07:00
friendica
72a770ae36
change the way profiles are imported
2013-04-30 18:16:51 -07:00
friendica
641e69ef7f
fix broken profile syncing
2013-04-29 18:47:34 -07:00
friendica
04170328b1
add some debugging - update times are changing much faster than they're supposed to. Log what has changed.
2013-04-29 18:21:23 -07:00
friendica
72e83f69bc
photo driver abstraction
2013-04-25 20:01:24 -07:00
friendica
7621bd3bb1
reverting to fancybox for "save to file" selection box until we find a better way - prettyPhoto just isn't working for this and I really need this functionality ATM until we can figure out how to make prettyPhoto work properly here.
2013-04-21 22:12:18 -07:00
friendica
ca605a8c83
more doco
2013-03-26 19:53:04 -07:00
friendica
abd58bce68
set hidden flags on new directory entries, not just existing ones
2013-03-26 19:37:33 -07:00
friendica
884812bcba
doco
2013-03-25 21:32:12 -07:00
friendica
ddf5bf8968
rename 'uri' (and parent_uri) to 'mid' (and parent_mid) since these no longer remotely resemble uri's and are actually message_id's. This change is potentially destabilising because it touches a lot of code and structure. But it has to get done and there's no better time than the present.
2013-03-21 18:25:41 -07:00
friendica
4b22c6e531
update
2013-03-21 02:21:44 -07:00
friendica
580acc5445
update modification time whenever a directory related attribute is changed
2013-03-13 17:27:17 -07:00
friendica
e7b6669dc3
update xchans on url change
2013-03-12 17:39:35 -07:00
friendica
f988213af8
fix typos
2013-03-11 18:22:40 -07:00
friendica
b86277b0ff
dangerous typo that removes all your hublocs, fix reshare formatting
2013-03-11 16:13:09 -07:00
friendica
952b2ef2ab
.
2013-03-10 18:45:58 -07:00
friendica
3d299f066e
fix comment permissions on display (again) and clean up an error seen in the logs
2013-03-06 18:52:42 -08:00
friendica
a7efec2b51
edits might really work now
2013-02-28 18:59:03 -08:00
friendica
a2a2ae2dd2
this might make edits update across the wire, or it might not
2013-02-28 18:20:42 -08:00
friendica
8275f14cea
mail recall - just set mail_flags = mail_flags & MAIL_RECALLED and tell the notifier. We'll need a special button for this. Also should probably report whether it was seen or not. Will do that another day.
2013-02-27 20:38:33 -08:00
friendica
ea3940c4b0
start formatting for Doxygen
2013-02-25 17:09:40 -08:00
friendica
24eac8c656
the heavy lifting is done for location migration aka channel import - now it's just connecting all the dots. Don't get impatient, there are a lot of dots.
2013-02-19 17:13:23 -08:00
friendica
ec3d387a65
public scope
2013-02-15 14:13:58 -08:00
friendica
b4057cfeb4
use our own CA bundle as authoritative for backend communications. This avoids OS dependent CA validity mismatches.
2013-02-13 20:09:30 -08:00
friendica
d1e5337c72
recursion and typo in rmagic with zid
2013-02-13 00:14:01 -08:00
friendica
71cfa66193
I think we're finally done with import_xchan_from_json - everything has been converted to import_xchan now
2013-02-07 20:06:01 -08:00
friendica
ce2fd23461
this should fix the auto-friend stuff
2013-02-07 14:49:09 -08:00
friendica
ed277f82f4
searchable flag logic reversed
2013-02-02 03:11:23 -08:00
friendica
3cf3f7437e
It's really not supposed to be quite this chatty on the network - ah that's why. Oops.
2013-01-28 20:51:37 -08:00
friendica
95415bff69
delete item should now mostly work
2013-01-28 19:24:36 -08:00
friendica
3e096e4a42
better handling of failures to lookup remote authors
2013-01-26 15:50:31 -08:00
friendica
50433d857a
quick-n-dirty wall-to-wall detection, wasn't working at all - this may be overboard or it may still not work at all.
2013-01-24 20:43:33 -08:00
friendica
566dd55146
turn down the log noise a bit
2013-01-24 19:45:08 -08:00
friendica
cb5a20ba2c
uncomplicate item deletion and fixup all the other linked tables
2013-01-24 16:44:10 -08:00
friendica
beb3301d43
security fixes related to directory access and sites that are off the grid
2013-01-22 02:56:32 -08:00
friendica
bda4ca4c0d
hidden directory entries
2013-01-22 00:20:25 -08:00
friendica
5949607d17
magic auth - it's mostly done or at least all the code bits are written and it looks in theory to be pretty secure and it doesn't white screen. Getting it to actually work(?), well we won't know how hard that will be until we get it on a couple of systems and try it. Magic auth on one box is a no-op because you're already authenticated.
2013-01-21 19:16:21 -08:00
friendica
debf7f5f26
more work on magic auth
2013-01-21 15:39:05 -08:00
friendica
127b605f32
preserve event item[uri] if present
2013-01-20 15:36:04 -08:00
friendica
af066d7383
mopping up the events issues so I can move on to other stuff
2013-01-16 03:18:32 -08:00
friendica
a9f4a47a35
import events (not just event posts) from zot
2013-01-16 00:59:43 -08:00
friendica
f24ce35603
implement "finger" command
2013-01-12 15:55:37 -08:00
friendica
fa642b36ff
fix double-encoding
2013-01-11 14:53:14 -08:00
friendica
529451a4e5
start rewrite of notification system delivery backend
2013-01-05 18:08:06 -08:00
friendica
78a65c7c1b
remove the country autofill declaration
2013-01-04 19:56:00 -08:00
friendica
d14c211341
debugging directory profiles
2013-01-04 19:47:03 -08:00
friendica
70b6f989dd
fix the contorted update logic on the network page
2013-01-04 19:24:17 -08:00
friendica
e03f6cb975
more debugging - looks like michameer.dyndns.org is throwing 500s so cannot test further
2013-01-03 16:39:22 -08:00
friendica
6a42d3708c
change precedence of bitwise operation
2013-01-03 16:30:35 -08:00
friendica
05d8faf5e1
provide delivery report on both sides, local and remote
2013-01-03 02:21:35 -08:00
friendica
4aae0ac948
issue with abook creation
2013-01-03 01:53:22 -08:00
friendica
32a97d5065
zome issues registering new hubs
2013-01-02 16:28:47 -08:00
friendica
a824a87d80
foreach issue
2013-01-02 01:44:50 -08:00
friendica
4d7fe15d3b
more poco discovery
2013-01-01 02:06:41 -08:00
friendica
6accc190d4
ensure all delivery result possibilities are logged and communicated to the sender
2013-01-01 00:45:44 -08:00
friendica
f2a4ea7254
add individual message delivery reporting
2012-12-31 21:33:11 -08:00
friendica
791302f317
more delivery diagnostics
2012-12-31 14:45:26 -08:00
friendica
abc271a0e7
more progress on onepoll
2012-12-30 22:41:53 -08:00
friendica
8eee37e1fa
more logging, some debugging of group membership page
2012-12-30 15:28:13 -08:00
friendica
cb329b9fb4
no hub - well doh, no wonder; we were looking for array['hub'] and it's actually array['url'].
2012-12-29 23:45:06 -08:00
friendica
dda4d689bb
This was bloody hard to sort out.... but now it's sorted and we can move forward again. Put back xtag for efficient keyword searching, use it in conjunction with xprof['keywords'] to avoid a SQL triple join and group_concat (which simply won't scale on a directory server), figured out how best to work timezone corrected birthdays into the protocol. The directory can even provide an age if one was provided to it. Both of these things need some more work, but we have the mechanisms and a plan how to do it right instead of "how the !@#$ are we going to do pull this off?"
2012-12-27 23:33:37 -08:00
friendica
55e77a57d0
get rid of xtag
2012-12-27 14:36:06 -08:00
friendica
a2c6f8c965
master/standalone directory profile update
2012-12-26 19:39:37 -08:00
friendica
d80f299dd4
more progress on directory import
2012-12-26 18:18:56 -08:00
friendica
ce0d389696
profile messages for directory synchronisation
2012-12-22 04:33:32 -08:00
friendica
893ba371a9
set_baseurl issue, more cleanup
2012-12-19 16:48:17 -08:00
friendica
a0a8cde201
do zot_finger/import_xchan on zid requests so we get the info cached locally
2012-12-06 20:05:42 -08:00
friendica
6ed27f9503
contact photo issues
2012-12-06 15:52:37 -08:00
friendica
1c6f301d8f
y'all got mail
2012-12-05 16:44:07 -08:00
friendica
7b4a92146f
local delivery
2012-12-02 20:54:20 -08:00
friendica
7f1a4a3060
auto-friending for forums and stuff is almost trivial now. But we will need a page to set the permissions on the "self" abook record. These will be the default permissions for anybody we wish to connect with.
2012-12-01 22:37:41 -08:00
friendica
f7ff2de132
add pending check on group queries
2012-11-29 23:06:03 -08:00
friendica
7082d198c2
Now if you follow somebody it will create an abook entry on the other site with blocked,ignored, and pending set. No "friend notifications" yet.
2012-11-29 18:15:13 -08:00
friendica
2fe2de1d5a
got comments going back and forth - we really need local_deliver now since even local deliveries are going through zot and that isn't necessary or desirable in the long term
2012-11-27 17:09:01 -08:00
friendica
f3fdbb6021
tracking through comments
2012-11-27 03:08:26 -08:00
friendica
941c554031
You've got mail! (actually a post, mail is for another day)
2012-11-26 21:20:16 -08:00
friendica
d79d698beb
more heavy lifting on delivery - now we can find all the recipients on the system who have any acceptable permissions for receiving a post. Next we just need to process edits and deletes, and otherwise store the message - yay. Still a lot of work, but we've come a long way baby.
2012-11-26 16:48:04 -08:00
friendica
ccf44f2514
more but slow progress on deliveries. The b*tch is trying to match permissions
2012-11-25 23:18:11 -08:00
friendica
cd4e381aa1
"heavy lifting" - zot messages flowing, now just need to be parsed and stored at the other end.
2012-11-19 20:45:12 -08:00
friendica
194ef02c28
DATABASE: outq additions, delivery now getting the notify across to the other side
2012-11-19 16:51:15 -08:00
friendica
db77309bc3
For private messages, use hush-hush ultra top-secret mode by default
2012-11-18 19:19:16 -08:00
friendica
71dc132f42
more infrastructure changes
2012-11-14 19:27:16 -08:00
friendica
9bfff0bca1
ensure we update the correct abook record
2012-11-13 01:42:08 -08:00
friendica
5bf3ddfcf6
got zot
2012-11-12 20:59:18 -08:00
friendica
b4c603cdac
one could say we've sort of got zot - at least there are two-way communications for channel meta info, don't yet know if it's working
2012-11-12 16:16:37 -08:00
friendica
f4ac91a8bc
typo
2012-11-11 19:13:38 -08:00
friendica
9fd2c2dd8a
hush-hush ultra top-secret mode
2012-11-11 19:12:20 -08:00
friendica
093ab7177a
rework a couple of zot basics
2012-11-10 23:26:12 -08:00
friendica
dd00fcc7bb
starting to get into the hairy parts of zot - identity, location, and permission synchronisation. After this, messaging should be a piece of cake.
2012-11-10 20:08:07 -08:00
friendica
295b865d06
"follow" now creates an address book entry, which means we can start tying that into the "connections" module - still have to turn the "contact edit" page from a mockup to real code, but it's all starting to flow.
2012-11-06 18:13:47 -08:00
friendica
aca2e3b52a
add key passing and verification to targeted discovery
2012-11-02 15:34:35 -07:00
friendica
8ae77d2984
verify all the signatures before adding contact
2012-11-02 01:44:27 -07:00
friendica
83cf11dd95
fixed the hash, now onward & upward
2012-11-02 00:19:04 -07:00
friendica
37653a3760
grrr... hashes aren't matching.
2012-11-01 22:23:13 -07:00
friendica
77c30972cb
network discovery on follow
2012-10-31 21:42:20 -07:00
friendica
78f64c90a3
get permission discovery working - guid sigs were getting truncated in db
2012-10-31 20:53:02 -07:00
friendica
2a0ff2b542
merge zperms functionality into zfinger
2012-10-31 17:38:22 -07:00
friendica
ff43d62e44
add hash to channel structure for consistency/redundancy
2012-10-04 03:13:57 -07:00
friendica
fbafd92f7f
moving a lot of structure around. 'entity' is now 'channel'
2012-09-25 17:57:20 -07:00
friendica
5ff6e9348b
a few minor changes
2012-08-26 23:05:00 -07:00
friendica
2140c2ea37
basic hub registration
2012-08-21 23:11:27 -07:00
friendica
26e29d7f88
zot basic comm structure (real basic)
2012-08-09 20:31:06 -07:00
friendica
9a39d4ade2
moving forward again
2012-08-08 18:50:04 -07:00
friendica
c673c70c25
updates
2012-08-05 21:41:58 -07:00
friendica
7a08942872
remember that the main thing is to keep the main thing the main thing...
2012-07-31 17:55:27 -07:00
friendica
4824e5b8b8
birthdays and events are now notifications
2012-07-29 18:29:27 -07:00
friendica
2ae0076ae2
move today's events into a ping notification
2012-07-28 17:21:42 -07:00
