aboutsummaryrefslogtreecommitdiffstats
path: root/include/socgraph.php
Commit message (Collapse)AuthorAgeFilesLines
* remove most legacy zot quirksMario2021-05-261-26/+14
|
* fix #1492Mario2020-11-211-0/+2
|
* deprecate \Zotlabs\Zot\Finger where apropriateMario Vavti2020-09-261-1/+1
|
* support zot and zot6 in social graph operations (suggestions, common friends)zotlabs2019-06-281-2/+19
| | | (cherry picked from commit 9def9a5cb7ab7799911013580c714605e9698122)
* fix some issues with friend suggestions on standalone sites with no ↵zotlabs2018-03-041-5/+8
| | | | 'suggestme' volunteers. This wrongly pulled up a site directory suggesting everybody on the site. While a better outcome than finding nobody, this does not fit with our ethical design goals. If there are no friends of friends, we will only suggest those who volunteer to be on the default suggestion list. Also do not attempt to load poco data from dead sites.
* db issue reported in hubzilla #953 - this does not do anything about the ↵zotlabs2018-01-101-1/+2
| | | | auth issue
* xlink_rating_text default valuezotlabs2017-12-091-1/+3
|
* don't include pending connections in pocozotlabs2017-11-181-1/+1
|
* include/socgraph - remove a few obsolete and long-deprecated functionszotlabs2017-06-011-71/+0
|
* reference to deprecated function import_author_diaspora in socgraph.phpzotlabs2017-04-021-9/+1
|
* even more backslashesredmatrix2016-10-031-20/+20
|
* turn the oft-repeated block_public ... check into a function ↵redmatrix2016-05-221-1/+1
| | | | observer_prohibited()
* finish updating zot_finger instancesredmatrix2016-05-211-5/+3
|
* static Appredmatrix2016-03-311-1/+1
|
* convert the abook fieldsredmatrix2015-06-141-9/+10
|
* more db structureredmatrix2015-05-191-10/+1
|
* Merge branch 'master' into tresfriendica2015-04-291-1/+1
|\ | | | | | | | | Conflicts: include/notifier.php
| * mod/branchtopic - move an off-topic comment to its own thread as a fresh ↵friendica2015-04-241-1/+1
| | | | | | | | wall-to-wall post and the same delivery permissions as its parent. No adjustments are made for complex delivery chains.
* | Merge branch 'master' into tresfriendica2015-04-231-36/+17
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/Contact.php include/ItemObject.php include/api.php include/attach.php include/diaspora.php include/dir_fns.php include/enotify.php include/event.php include/expire.php include/items.php include/notifier.php include/notify.php include/photos.php include/taxonomy.php include/text.php include/widgets.php include/zot.php mod/admin.php mod/channel.php mod/dirsearch.php mod/display.php mod/editwebpage.php mod/events.php mod/home.php mod/item.php mod/manage.php mod/mood.php mod/network.php mod/page.php mod/photos.php mod/ping.php mod/post.php mod/thing.php mod/viewsrc.php view/css/mod_events.css
| * commit 59828593c broke some important poco stuff, looks like the cat might ↵friendica2015-04-061-0/+20
| | | | | | | | have climbed over the keyboard and deleted something that wasn't intended to be deleted.
| * Some cleanups and documentation.Klaus Weidenbach2015-03-041-31/+15
| | | | | | | | | | | | | | Fixed some wrong variable names. Initialized some variables before using them. Removed some checks for STATUSNET_PRIVACY_COMPATIBILITY in include/security.php as it does not seem to be defined anywhere.
| * some ratings fixesfriendica2015-02-131-23/+0
| |
* | Merge branch 'master' into tresfriendica2015-01-291-1/+1
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: include/group.php include/text.php mod/acl.php mod/channel.php mod/connections.php mod/display.php mod/group.php mod/item.php mod/locs.php mod/network.php mod/photos.php mod/ping.php mod/starred.php mod/viewsrc.php
| * remote_user => remote_channelfriendica2015-01-281-1/+1
| |
| * local_user => local_channelfriendica2015-01-281-1/+1
| |
* | Merge branch 'master' into tresfriendica2015-01-271-6/+8
|\| | | | | | | | | Conflicts: include/socgraph.php
| * provide storage for directory based reputation in the xlink table by setting ↵friendica2015-01-261-6/+8
| | | | | | | | xlink_static = 1, so that xlink_static = 0 is traditional poco linkages
* | Merge branch 'master' into tres and add some work on the item_deleted flag ↵friendica2015-01-261-1/+210
|\| | | | | | | | | | | | | | | | | | | refactor Conflicts: include/attach.php include/onedirsync.php include/zot.php mod/locs.php
| * abstract poco into a single function in socgraph so we can provide different ↵friendica2015-01-251-0/+209
| | | | | | | | wrappers for it providing slightly different functionality.
| * don't set a rating of 1 on old sites that report poco rating as an array. ↵friendica2015-01-251-1/+1
| | | | | | | | Just set it to 0. It will be fixed whenever they upgrade.
* | working through the xchan table to remove bitfields, mostly complete except ↵friendica2015-01-201-8/+4
|/ | | | for updating the updater
* get rid of really old poco records once weeklyfriendica2015-01-201-0/+2
|
* poco rating variable getting over-written before local storage.friendica2015-01-191-1/+1
|
* validate poco chatrooms before storingfriendica2015-01-151-0/+3
|
* more backend work on poco ratingfriendica2015-01-151-2/+5
|
* PostgreSQL support initial commitHabeas Codice2014-11-131-26/+31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were 11 main types of changes: - UPDATE's and DELETE's sometimes had LIMIT 1 at the end of them. This is not only non-compliant but it would certainly not do what whoever wrote it thought it would. It is likely this mistake was just copied from Friendica. All of these instances, the LIMIT 1 was simply removed. - Bitwise operations (and even some non-zero int checks) erroneously rely on MySQL implicit integer-boolean conversion in the WHERE clauses. This is non-compliant (and bad programming practice to boot). Proper explicit boolean conversions were added. New queries should use proper conventions. - MySQL has a different operator for bitwise XOR than postgres. Rather than add yet another dba_ func, I converted them to "& ~" ("AND NOT") when turning off, and "|" ("OR") when turning on. There were no true toggles (XOR). New queries should refrain from using XOR when not necessary. - There are several fields which the schema has marked as NOT NULL, but the inserts don't specify them. The reason this works is because mysql totally ignores the constraint and adds an empty text default automatically. Again, non-compliant, obviously. In these cases a default of empty text was added. - Several statements rely on a non-standard MySQL feature (http://dev.mysql.com/doc/refman/5.5/en/group-by-handling.html). These queries can all be rewritten to be standards compliant. Interestingly enough, the newly rewritten standards compliant queries run a zillion times faster, even on MySQL. - A couple of function/operator name translations were needed (RAND/RANDOM, GROUP_CONCAT/STRING_AGG, UTC_NOW, REGEXP/~, ^/#) -- assist functions added in the dba_ - INTERVALs: postgres requires quotes around the value, mysql requires that there are not quotes around the value -- assist functions added in the dba_ - NULL_DATE's -- Postgres does not allow the invalid date '0000-00-00 00:00:00' (there is no such thing as year 0 or month 0 or day 0). We use '0001-01-01 00:00:00' for postgres. Conversions are handled in Zot/item packets automagically by quoting all dates with dbescdate(). - char(##) specifications in the schema creates fields with blank spaces that aren't trimmed in the code. MySQL apparently treats char(##) as varchar(##), again, non-compliant. Since postgres works better with text fields anyway, this ball of bugs was simply side-stepped by using 'text' datatype for all text fields in the postgres schema. varchar was used in a couple of places where it actually seemed appropriate (size constraint), but without rigorously vetting that all of the PHP code actually validates data, new bugs might come out from under the rug. - postgres doesn't store nul bytes and a few other non-printables in text fields, even when quoted. bytea fields were used when storing binary data (photo.data, attach.data). A new dbescbin() function was added to handle this transparently. - postgres does not support LIMIT #,# syntax. All databases support LIMIT # OFFSET # syntax. Statements were updated to be standard. These changes require corresponding changes in the coding standards. Please review those before adding any code going forward. Still on my TODO list: - remove quotes from non-reserved identifiers and make reserved identifiers use dba func for quoting - Rewrite search queries for better results (both MySQL and Postgres)
* illegal string offset warningsfriendica2014-09-051-1/+1
|
* fix the client side of pocofriendica2014-09-041-11/+20
|
* Set a default directory server from a hard-wired list if one was not ↵friendica2014-04-251-7/+1
| | | | previously chosen.
* that should fix it.friendica2014-03-241-0/+5
|
* vsprintf errorfriendica2014-02-261-1/+2
|
* put bookmarked chatrooms into pocofriendica2014-02-251-0/+28
|
* suggestion widgetfriendica2013-12-061-0/+4
|
* Issue #99Thomas Willingham2013-08-181-0/+1
|
* fine tuning the error checksfriendica2013-08-051-1/+6
|
* keep total of imported xchans correct - even if one or mail failures occurfriendica2013-08-051-4/+7
|
* more error checking in case import_xchan failsfriendica2013-08-051-0/+8
|
* use url part of arrayfriendica2013-08-051-1/+1
|
* prune old suggested channelsfriendica2013-08-051-0/+10
|
* populate initial suggestions (ultimately we want to do this at install time ↵friendica2013-08-051-84/+68
| | | | as well as from the poller so that new sites have friend suggestions when they create their first channel).