aboutsummaryrefslogtreecommitdiffstats
path: root/include/diaspora.php
Commit message (Collapse)AuthorAgeFilesLines
* make sure we honour the disable_discover_tab preffriendica2015-01-281-1/+5
|
* allow diaspora posts to be delivered to the discover channel unless ↵friendica2015-01-281-1/+5
| | | | prohibited from doing so.
* friendica commenters are currently shown using "Diaspora" app. Try and fix ↵friendica2014-11-201-1/+6
| | | | this where we can.
* change logging of some troublesome or noisy bits so we can figure out what ↵friendica2014-11-191-1/+1
| | | | is really going on
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-11/+10
|\ | | | | | | | | | | | | | | | | | | | | | | Conflicts: boot.php include/dba/dba_driver.php include/diaspora.php include/follow.php include/session.php include/zot.php mod/photos.php mod/ping.php
| * logging changes, untranslated stringfriendica2014-11-051-1/+1
| |
| * ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-041-10/+9
| | | | | | | | | | | | | | | | | | | | the default connection permissions for those who don't have a predefined (or therefore have a "custom") permissions role. Unfortunately this includes most people that were using this software more than a month ago. The real changes are that the SELF address book entry no longer holds "auto-permissions" but instead holds your "default permissions" (if you have a pre-defined role, the defaults will be pulled from the role table). The auto permissions have moved to a pconfig (uid.system.autoperms). A DB update will move these settings into their new homes. What used to be the "Auto-permissions settings" page is now the "default permissions settings" page and a checkbox therein decides whether or not to apply the permissions automatically. A link to this page will only be shown when you have the "custom" role selected. With luck nobody will notice anything wrong. But at least for the next few days, please review permissions that have been assigned to new connections (either automatically or manually) and make sure they make sense (e.g. they aren't "nothing"). You still need to take action when seeing a message "permissions have changed but not yet submitted" as we always let you review and perhaps adjust the settings _before_ a connection is established (unless you have autoperms turned on).
* | PostgreSQL support initial commitHabeas Codice2014-11-131-2/+2
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* back to wrestling with the !@#$ diaspora recursive reshare from hellfriendica2014-10-141-3/+8
|
* diaspora_send_status() - recalculate markdown translation to pickup any ↵friendica2014-10-121-1/+1
| | | | later message changes after original submission like wall-to-wall attributions for instance. Normally this would've come from our cached version which was stored prior to tag_deliver being run and therefore isn't yet aware that wall-to-wall status may have changed after delivery.
* remove remnants of old signing structure - now using diaspora_metafriendica2014-10-101-7/+0
|
* reset route to parent route on Diaspora comments flowing upstream so they ↵friendica2014-10-101-3/+5
| | | | won't be rejected going downstream
* make sure diaspora comments get the correct routefriendica2014-10-101-0/+4
|
* don't double-encode hashtagsfriendica2014-10-081-4/+4
|
* log the recursive reshare from hell at logger_debug until we get through ↵friendica2014-10-071-3/+3
| | | | this mess.
* Make a best guess at how to pull the attribution from the recursive reshare ↵friendica2014-10-061-0/+4
| | | | from hell.
* found one bug trying to fetch the recursive reshare from hell. I still think ↵friendica2014-10-061-2/+2
| | | | there's a problem with attribution but we'll have to wait and find that once we have some content to track. Also in private messages, on the message list page, change the text from delete message to delete conversation, because that's what we're really doing.
* attempt to deal with the diaspora recursive reshare from hell (Bob reshared ↵friendica2014-10-051-10/+40
| | | | Nancy's reshare of George's reshare of Lilly's reshare of Nathan's post). The attribution may be wrong so this is still a work in progress.
* send dislike activities to diaspora as comments, also send likes and ↵friendica2014-10-051-13/+5
| | | | dislikes of comments as additional comments. We won't go into why this is necessary for a service that claims to support activitystreams.
* diaspora share not rendering issue - still have one remaining (the recursive ↵friendica2014-10-051-1/+1
| | | | share from hell)
* issues with diaspora comment signatures on relayed comments that are relayed ↵friendica2014-10-021-0/+3
| | | | through a redmatrix site (parent post is redmatrix) and involve a private post.
* diaspora private mail seems to work now - but there's an obfuscation leak ↵friendica2014-09-231-10/+11
| | | | via the conversation structure that needs to be dealt with.
* d* little fixesfriendica2014-09-231-10/+4
|
* d* PM cont.friendica2014-09-231-1/+10
|
* more work on d* private messagesfriendica2014-09-231-6/+18
|
* private mail from d* to r# seems to work with these edits. - Now have to go ↵friendica2014-09-221-10/+7
| | | | back the other way.
* try to sort out walltowall translation for diaspora recipientsfriendica2014-09-191-4/+4
|
* still some old Friendica database queries in diaspora_signed_retractionfriendica2014-09-161-17/+15
|
* provide a way to sync locations and get rid of bogus hublocs, now implementedfriendica2014-09-141-0/+6
|
* fix diaspora_retractionfriendica2014-09-141-7/+4
|
* doc updates and a couple of issues spotted in the logs (diaspora likes, feed ↵friendica2014-09-121-1/+1
| | | | author import)
* possible solution to diaspora walltowall mistaken attributionfriendica2014-09-101-4/+0
|
* encrypt diaspora_meta since it may contain private message contentsfriendica2014-09-101-14/+30
|
* fix the like signatures to the "new ordering" - inbound and outboundfriendica2014-09-101-20/+12
|
* don't include plus-sign in the stored term for imported mentionsfriendica2014-09-101-1/+3
|
* this should be the final piece of the puzzlefriendica2014-09-091-0/+14
|
* Did I ever mention how much I HATE hacking crypto? If you've got a protocol ↵friendica2014-09-091-1/+12
| | | | doc that says how you sign something, you damm well better sign it that way.
* some fixes for auto-perms across networksfriendica2014-09-091-9/+9
|
* reduce log level of inbound d* posts until we get through some of the more ↵friendica2014-09-091-1/+1
| | | | serious federation issues
* put back old pointerfriendica2014-09-091-1/+1
|
* fix empty reshared contentfriendica2014-09-091-2/+2
|
* d* friending vsprintf errorfriendica2014-09-091-1/+1
|
* heavy lifting on diaspora likes. Still needs much more work - especially as ↵friendica2014-09-081-67/+56
| | | | we're ignoring signatures at this time
* diaspora_like - sql errorfriendica2014-09-081-22/+15
|
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-1/+1
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* attempt to format diaspora reshares correctly. This might be an iterative ↵friendica2014-09-081-24/+21
| | | | process.
* support the recent (2 years ago) changes to diaspora photo embedsfriendica2014-09-061-0/+6
|
* sort out some of the bb2d madnessfriendica2014-09-031-66/+23
|
* this is turning into a wretched mess. It's going to get worse before it gets ↵friendica2014-09-031-11/+20
| | | | better, but I'm trying to do this incrementally so I don't break the whole shebang for a few days. It will get better once all the bbcode translation is done in a single place (cross fingers), and we can just sign the post once when we submit it and be done with it. If Diaspora ever implements editing of existing posts we'll have to go back and do the whole wretched mess over again.
* store diaspora meta info in the item table. It has to go there or it will ↵friendica2014-09-031-27/+27
| | | | kill us with complex joins. We can phase out the sign table once this all checks out.
generated by cgit v1.2.3 (git 2.25.1) at 2024-07-03 01:43:00 +0000