aboutsummaryrefslogtreecommitdiffstats
path: root/include/network.php
Commit message (Collapse)AuthorAgeFilesLines
* Let Diaspora hublocs come back by allowing discover_by_webbie() to carry on ifThomas Willingham2014-12-131-3/+2
| | | | | | and look for a hubloc even if an xchan is found. You'll probably need to loop through the missing ones manually.
* PostgreSQL support initial commitHabeas Codice2014-11-131-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* this bug has been there for a *long* time. First time I've ever seen it ↵friendica2014-10-131-1/+1
| | | | triggered.
* z_post_url_json() added to easily deal with JSON post APIs; without getting ↵friendica2014-09-161-0/+17
| | | | content-type unknown warnings/errors. Also added a debug option to z_get|post_url so you could track and log some of these nasty little buggers.
* just mark dead hubloc deleted - don't remove them. This could cause ↵friendica2014-09-161-11/+4
| | | | problems. Also clean up fetch_url/post_url header option
* doco correctionfriendica2014-09-091-11/+5
|
* syntax error in dba driver, document z_post_urlfriendica2014-09-091-0/+29
|
* allow stuff with Diaspora authors to federate in zot conversations even if ↵friendica2014-09-041-1/+1
| | | | the local site has diaspora disabled. This way it won't look like folks are talking to themselves.
* feed removal issuefriendica2014-09-021-5/+7
|
* use feed title for channel name before checking author, make feed items ↵friendica2014-09-021-5/+7
| | | | shareable (they're private to the channel so they won't be shown in searches), try and handle Diaspora mentions a bit more elegantly. (Bug: we don't convert mentions to Diaspora's format on outbound at all!)
* use feed icon as default avatar for rss connectionsfriendica2014-09-011-2/+5
|
* rss feed discoveryfriendica2014-08-311-20/+162
|
* sort out some anomaliesfriendica2014-08-251-2/+3
|
* Add d* folks to address book. WARNING - DO NOT ATTEMPT THIS. LEAVE IT THE ↵friendica2014-08-241-292/+364
| | | | FRUCK ALONE until the feature is stable. I won't help you if you try this and end up with a borked site. You are completely on your own.
* diaspora discoveryfriendica2014-08-241-0/+113
|
* move Friendica photo migrator to addons, bring back a few XML scraping ↵friendica2014-08-201-1/+165
| | | | functions that we're going to require (unfortunately)
* some work on network discoveryfriendica2014-08-191-95/+149
|
* optionally allow zrl usage from specific markdown sourcesfriendica2014-07-011-9/+9
|
* logging: include target url when reporting z_fetch_url and z_post_url errors.friendica2014-05-271-4/+4
|
* This should be a slight improvement in setting ciphers - we'll punt on ↵friendica2014-03-251-8/+4
| | | | RedHat but open up the list just for openssl distros which seem to have all the problems at the moment.
* that should fix it.friendica2014-03-241-2/+2
|
* that didn't work out wellfriendica2014-03-241-2/+2
|
* ssl ciphers - be liberal in what we accept, conservative in what we generatefriendica2014-03-241-12/+24
|
* add curl error text to mod/probe so we can remotely diagnose communication ↵friendica2014-03-231-2/+4
| | | | issues from other sites.
* improve curl error loggingfriendica2014-03-231-1/+3
|
* clean up logger commands. Placed apostrophs at the end from some comments to ↵Michael Meer2014-01-301-8/+2
| | | | keep the syntax highlighting in vi working
* attempt with fix URL for testing worksMichael Meer2014-01-301-3/+9
|
* make default profile photo configurable - should be functional but needs ↵friendica2013-12-191-1/+1
| | | | admin ui
* htmspecialchars_decode only takes one argument.zottel2013-12-121-1/+1
|
* more htmlspecialchars sanitisationfriendica2013-12-121-1/+1
|
* some work on modularising the default profile photo so we can make them site ↵friendica2013-12-091-1/+1
| | | | selectable. Also red != friendica so we don't need all these friendica logos taking up space
* trimmed style.css by a few hundred lines. Needs many more such effortsfriendica2013-12-011-103/+0
|
* get rid of deprecated post_url() functionfriendica2013-12-011-102/+2
|
* get rid of fetch_url - post_url will be a bit harder as several plugins need ↵friendica2013-12-011-153/+5
| | | | to be updated
* deprecate a->get_curl_code() and $a->get_curl_headers()friendica2013-12-011-180/+12
|
* set default charset of email_header_encode, add ud_flags to indicate which ↵friendica2013-09-181-1/+1
| | | | (directory sync) updates have been processed in some way.
* z_fetch_url - include curl debug info in return array and log it (at ↵friendica2013-09-101-0/+10
| | | | | | logger_data level) on failure This should probably be at a lower log level, but unsuccessful connections could happen a lot on a busy production site so we'll try to keep the log noise down unless somebody really needs to track this info.
* make manual image scaling work - even if auto scaling kicks in.friendica2013-06-231-7/+13
|
* photo driver abstractionfriendica2013-04-251-2/+3
|
* odds and ends in prepearation for photo abstraction, plus red-to-friendica addonfriendica2013-04-251-25/+25
|
* turn all Red links into zrls (not the old zrls, the new bbcode zrl which ↵friendica2013-04-151-1/+1
| | | | means we can zidify them)
* more Friendica removalsfriendica2013-04-141-5/+4
|
* update manage table and some documentationfriendica2013-03-271-1/+30
|
* initial docofriendica2013-02-261-36/+49
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* more groundwork for channel importfriendica2013-02-141-16/+16
|
* use our own CA bundle as authoritative for backend communications. This ↵friendica2013-02-131-0/+9
| | | | avoids OS dependent CA validity mismatches.
* Tweak behavior of redirect for http codesOlaf Conradi2012-12-261-7/+6
| | | | | | | | | | | | Not every webserver supports 308 redirects with POST correctly. Most sites are already configured using 301 or 302 redirects. This only effects POST, GET behavior is unmodified. Most calls to POST are under control by friendica not the end user, so should not be a problem ni general. GET with 301, 302, 303, 307 and 308 are redirected as GET POST with 301, 302, 307 and 308 are redirected as POST POST with 303 is redirected as GET
* Same applies for 307Olaf Conradi2012-12-261-2/+3
| | | | 308 spec mentions 307 must not rewrite POST to GET
* POST redirects to POST on 308 onlyOlaf Conradi2012-12-261-2/+10
| | | | | POST redirects to POST on 308 only, 301-307 to GET. Side-effect is that POST params get dropped for GET.
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-04 13:03:04 +0000