aboutsummaryrefslogtreecommitdiffstats
path: root/include/follow.php
Commit message (Collapse)AuthorAgeFilesLines
* separate permission_update notification into permission_create and ↵redmatrix2015-10-181-1/+1
| | | | permission_update, since some networks send out a notification for duplicate share requests even if connected.
* re-organise the protocol disabled logicredmatrix2015-10-181-8/+18
|
* more work separating Diaspora from coreredmatrix2015-08-031-19/+8
|
* convert the abook fieldsredmatrix2015-06-141-8/+6
|
* diaspora disallowed by defaultredmatrix2015-06-101-2/+0
|
* toggle diaspora protocol on a per-channel level in addition to the existing ↵redmatrix2015-06-091-0/+9
| | | | per site setting. Default is enabled if the site setting is enabled.
* Fix missing value in insert for default closenessAlexandre Hannud Abdo2015-03-091-1/+1
|
* change default affinity (abook_closeness) to 80 for all new connections ↵friendica2015-03-081-1/+7
| | | | going forward (was 99). This way it can be adjusted down later without requiring you to change all your existing connections upward (since your existing connections are likely all sitting at 99 at the moment). The default setting is also configurable with a pconfig system.new_abook_closeness
* local_user => local_channelfriendica2015-01-281-1/+1
|
* rework the new connection stuff so we don't need a "permissions have been ↵friendica2015-01-251-14/+9
| | | | changed but not saved" message.
* undo these bits of trinidad - we're going to do things differentlyfriendica2015-01-051-1/+1
|
* initial trinidad checkinfriendica2014-12-291-1/+1
|
* Merge remote-tracking branch 'upstream/master'Habeas Codice2014-11-131-8/+2
|\ | | | | | | | | | | | | | | | | | | | | | | 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
| * some minor cleanup of unreported (and as yet undiscovered) issues with ↵friendica2014-11-051-2/+3
| | | | | | | | permissions toggling. No smoking guns and no obvious issues discovered here. Repeated and tried to duplicate zottell's issue as described without seeing any obvious problems.
| * ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-041-8/+2
| | | | | | | | | | | | | | | | | | | | 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-4/+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)
* the default permissions for new connections when using a custom role is ↵friendica2014-10-281-1/+5
| | | | inadequate. Until we can make it configurable start off with something like a public social role. We're typically taking the person straight to the connection editor so they can change it before any privacy damage is done
* several unrelated things - auto_follow wasn't working for new accounts, ↵friendica2014-10-271-0/+2
| | | | error returned in private mention to a collection, and added auto-completion to photo tags; though it only matches people so the hover text is now wrong. Also made the photo edit form XHTML (XML) compliant.
* ability to pre-populate connections for new channels. e.g. "MySpace Tom"friendica2014-10-011-1/+1
|
* fix url mismatches of a single trailing slash for feed author/owner ↵friendica2014-09-231-0/+3
| | | | comparisons; update diaspora_compat
* feeds with '@' in the URL were being handled as webfinger addresses and ↵friendica2014-09-211-1/+1
| | | | didn't fall through to RSS discovery. Issue #599
* implement permission roles - the backend should be done except for maybe a ↵friendica2014-09-171-0/+13
| | | | couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
* allow feeds to be sourcedfriendica2014-09-041-1/+1
|
* allow stuff with Diaspora authors to federate in zot conversations even if ↵friendica2014-09-041-0/+6
| | | | the local site has diaspora disabled. This way it won't look like folks are talking to themselves.
* fix phantom attachments in feedsfriendica2014-09-011-1/+1
|
* logic invertedfriendica2014-09-011-1/+1
|
* honour the feed_contacts settingfriendica2014-09-011-0/+5
|
* get out the sunniesfriendica2014-08-311-2/+3
|
* service class check for feeds. Note limit is account based, not channel based.friendica2014-08-311-21/+33
|
* rss feed discoveryfriendica2014-08-311-5/+16
|
* Add d* folks to address book. WARNING - DO NOT ATTEMPT THIS. LEAVE IT THE ↵friendica2014-08-241-3/+14
| | | | 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.
* prevent follows of and notifications to deceased channelsfriendica2014-04-071-0/+6
|
* project "snakebite"friendica2014-02-171-61/+70
|
* follow and accept_follow hooksfriendica2013-11-211-0/+4
|
* Protocol: now set data['alg'] on all encapsulated encrypted packets, so that ↵friendica2013-11-201-1/+1
| | | | we can more easily retire 'aes256cbc' once it is no longer viable.
* add zid to connect_urlfriendica2013-08-221-1/+1
|
* premium/restricted channel connections implemented, configure at ↵friendica2013-08-211-1/+6
| | | | yoursite/channel/nickname - this basically redirects "follow" requests to a premium channel's sell page if it has one configured. You can still click through and create a connection request (introduction), but this provides a means for the channel owner to state their terms. If you don't abide by the terms, you will likely be blocked or the channel deleted. This facility is extensible in a number of ways.
* some sane permission defaults.friendica2013-08-181-2/+3
|
* some auto-friending cleanupsfriendica2013-05-191-1/+3
|
* add new connections to default group (if any)friendica2013-03-271-50/+11
|
* start formatting for Doxygenfriendica2013-02-251-1/+1
|
* start on channel_remove(), add some generic channel queries to the API layersfriendica2013-02-161-1/+1
|
* convert mod/follow to associative json and add more logging for when things ↵friendica2013-01-291-11/+23
| | | | go wrong
* cleanup bootfriendica2012-12-311-1/+1
|
* couple of fixes to follow, prepare for default connection permissionsfriendica2012-12-311-1/+9
|
* include/follow cleanupfriendica2012-12-251-7/+5
|
* prevent connecting to yourself or connecting to the same channel multiple timesfriendica2012-12-251-15/+40
|
* third param to zot_finger no longer neededfriendica2012-12-051-1/+1
|
* add pending check on group queriesfriendica2012-11-291-1/+1
|
* "follow" now creates an address book entry, which means we can start tying ↵friendica2012-11-061-2/+14
| | | | 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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 19:10:04 +0000