aboutsummaryrefslogtreecommitdiffstats
path: root/include/zot.php
Commit message (Collapse)AuthorAgeFilesLines
* this should improve queue performance dramatically.friendica2014-03-241-1/+2
|
* create_sys_channel during setup bypasses our check when creating the first ↵friendica2014-03-231-0/+2
| | | | account that there is a site keypair. Esnure that a site keypair is created before any sys channels are created.
* found what I believe is the root cause of issue #230, but don't yet have a ↵friendica2014-03-201-13/+21
| | | | workable solution. This one is hard.
* increase log info to track down source of ownership failuresfriendica2014-03-201-1/+1
|
* cleanupfriendica2014-03-181-12/+19
|
* bring friends backfriendica2014-03-061-10/+10
|
* change flags for one-way connections from hidden to unconnected so we can ↵friendica2014-03-041-5/+10
| | | | still use hidden for - well hiding connections
* directory sync issuesfriendica2014-03-031-8/+8
|
* some anomolies found when viewing connections in various cases.friendica2014-03-021-0/+21
|
* minor stuff, some doco, auth cleanup, and make "unknown" more translateable ↵friendica2014-02-221-4/+0
| | | | by context.
* fix login weirdness for accounts that need to be approvedfriendica2014-02-201-5/+0
|
* believe i found the issue which was causing hundreds/thousands of identical ↵friendica2014-02-201-9/+12
| | | | hublocs to be created
* several things were not working correctly w/r/t community tagging. The ↵friendica2014-02-161-5/+7
| | | | 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.
* implement a forced directory update mode where we unconditionally create a ↵friendica2014-02-111-6/+9
| | | | 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).
* reversed args in update_modtime, incorrect ud_guid and ud_hashfriendica2014-02-101-1/+1
|
* Check for the correct DB name before pushing.friendica2014-02-101-1/+1
|
* add channel_notify_flags to list of things which should *not* be synced ↵friendica2014-02-101-1/+1
| | | | across nomads. You probably only want one site to send you notification emails for the same events as opposed to all of them.
* perform remote discovery on abook sync of nomadic clones if remote channel ↵friendica2014-02-091-0/+27
| | | | (xchan) is unknown
* To be listed as a public site, you need to be an https site with a valid ↵friendica2014-02-071-0/+11
| | | | 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.
* break delivery loop if an item is deleted twicefriendica2014-01-101-1/+8
|
* Merge branch 'master' into movejsfriendica2014-01-061-1/+1
|\ | | | | | | | | Conflicts: version.inc
| * typo in import_directory_profilefriendica2014-01-051-1/+1
| |
* | move js files from corefriendica2014-01-041-2/+3
|/
* issue #230 - deletion failure in multiple delivery chainsfriendica2013-12-261-1/+4
|
* extend the directory profiles a bit morefriendica2013-12-251-1/+14
|
* issue #240 - we were using htmlentities instead of htmlspecialchars in ↵friendica2013-12-111-14/+14
| | | | 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.
* issue #225friendica2013-12-051-6/+28
|
* include re-organisation and more doco, post_to_red fix ampersands in categoriesfriendica2013-12-041-2/+21
|
* add hooks to zot-finger and import_xchanfriendica2013-12-031-0/+3
|
* ensure that every imported channel has a primary hublocfriendica2013-12-021-0/+16
|
* docofriendica2013-11-281-6/+21
|
* item store hooksfriendica2013-11-281-0/+9
|
* docofriendica2013-11-281-6/+41
|
* only list undeleted hublocs in zot_fingerfriendica2013-11-281-4/+7
|
* zot docofriendica2013-11-281-17/+96
|
* reduce the likelihood that a given channel will have 30-40 valid hublocs ↵friendica2013-11-271-22/+9
| | | | with the same hubloc_url.
* white screenfriendica2013-11-211-1/+1
|
* add aid to notifiy table which we may need to supress duplicate notify ↵friendica2013-11-201-3/+13
| | | | | | emails across your channels also try to handle the wretched mess of broken and duplicated hublocs that fred.cepheus.uberspace.de typically reports
* Protocol: now set data['alg'] on all encapsulated encrypted packets, so that ↵friendica2013-11-201-5/+5
| | | | we can more easily retire 'aes256cbc' once it is no longer viable.
* filter out duplicate recipients on local deliveries. We only need to deliver ↵friendica2013-11-171-1/+19
| | | | stuff once to any particular channel.
* pull in some posts when we first connect with a new channel (if allowed to) ↵friendica2013-11-171-2/+2
| | | | - if not allowed to, do it if that condition changes
* populate some posts when somebody is granted "read stream" permissionfriendica2013-11-171-1/+13
|
* silence a warningfriendica2013-11-141-1/+1
|
* don't store update records if we're not a directory server of some kindfriendica2013-11-041-0/+5
|
* allow zot public providers to list their location, as a non US-based server ↵friendica2013-10-301-3/+7
| | | | could be a strong selling point.
* access policy and directory mode were crossed on site table creationfriendica2013-10-301-1/+1
|
* send rpost requests from remote sites back to yours.friendica2013-10-291-2/+2
|
* rpost bbcode tagfriendica2013-10-291-0/+11
|
* create update record for accounts on directory server itself during profile ↵friendica2013-10-241-5/+8
| | | | 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.
* update even if no changefriendica2013-10-141-0/+8
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-13 11:45:45 +0000