aboutsummaryrefslogtreecommitdiffstats
path: root/boot.php
Commit message (Collapse)AuthorAgeFilesLines
* ok heads up - potentially destabilising change. I've tried to sort out all ↵friendica2014-11-041-1/+1
| | | | | | | | | | 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).
* configurable visual alerts/notificationsfriendica2014-11-041-0/+16
|
* Pixelbit restored. Going forwards, we probably want to add a checkThomas Willingham2014-11-021-0/+1
| | | | | | that a directory is returning something in find_upstream_directory() since this was spotted by a new install who thought *they* were broken.
* Remove pixelbits from directory fallback - blocked public searches provideThomas Willingham2014-11-021-1/+0
| | | | no results.
* move all theme initialisation to one place - just after calling module_init. ↵friendica2014-10-201-6/+10
| | | | Revert if there are serious issues, but please note the issues in as much detail as possible so we can work through them.
* mark signature forgeriesfriendica2014-10-161-0/+1
|
* this is the reason Diaspora forum tagging was brokenfriendica2014-10-141-1/+1
|
* allow custom role permissions and fix site timezone.friendica2014-09-291-4/+2
|
* diaspora private mail seems to work now - but there's an obfuscation leak ↵friendica2014-09-231-0/+1
| | | | via the conversation structure that needs to be dealt with.
* If a short ping causes lots of issues, and anyone who has been hereThomas Willingham2014-09-181-2/+2
| | | | | a while tends to have a longer ping, we should probably have a longer ping
* change platform name to redmatrix (lowercase, one word) for use in meta tags ↵friendica2014-09-151-1/+1
| | | | and stuff, move yet another oauth1 library to library instead of having it in plugins where we'll end up with a white screen if we re-use it in another plugin; which I plan to do.
* allow the site to designate an admin channel that's visible to the outside ↵friendica2014-09-141-1/+2
| | | | world (via siteinfo/json). Otherwise we'll use the default channel of any accounts that have the account admin role.
* remove this hub from fallback serversmarijus2014-09-131-2/+1
|
* correct item author for feeds with multiple or different authorsfriendica2014-09-111-0/+2
|
* This is long overdue - use a symblic constant NULL_DATE instead of the ↵friendica2014-09-081-3/+3
| | | | easily mis-typed sequence '0000-00-00 00:00:00'
* set the default items-per-page for the entire app to 60friendica2014-09-071-1/+1
|
* implement service class for feed polling frequenecy, fixed a service class ↵friendica2014-09-031-0/+1
| | | | bug, moved service class stuff from plugin to account.php where it belongs and load that by default instead of on demand
* store diaspora meta info in the item table. It has to go there or it will ↵friendica2014-09-031-1/+1
| | | | kill us with complex joins. We can phase out the sign table once this all checks out.
* get out the sunniesfriendica2014-08-311-1/+1
|
* Ability to close comments at a certain date/time - needed for loom.io ↵friendica2014-08-281-1/+1
| | | | emulation (and many other uses)
* mind numbing drudgery continued...friendica2014-08-271-1/+1
|
* place to store multiple choice and select items for extensible profilesfriendica2014-08-261-1/+1
|
* more hard workfriendica2014-08-261-1/+1
|
* We really can't do this without a hubloc. I was hoping we could, but ↵friendica2014-08-221-1/+1
| | | | notifier is setup to take hublocs, not xchans.
* verified that chatroom expire is working, so doing away with the second ↵friendica2014-08-201-5/+0
| | | | | | function to do the same thing. If you have a problem with chatroom expiration, check that it was created with cr_expire set to 120 (minutes). Chatrooms created during the first couple of days of the chat feature didn't have this. You can set the DB value manually.
* some more work on realmsfriendica2014-08-171-1/+1
|
* provide backend storage and declaration of directory realmfriendica2014-08-161-1/+6
|
* provide an expert option to opt out from user zoom on mobile devicesmarijus2014-08-131-0/+5
|
* item table upgrade for storing post visibilityfriendica2014-08-061-1/+1
|
* db tables for extensible profile fieldsfriendica2014-08-021-1/+1
|
* block channel removal for 48 hours after changing the account password, ↵friendica2014-07-291-1/+1
| | | | since the password is required to remove a channel. Somebody looking at an open session on somebody else's computer can simply change the password and then proceed to maliciously remove the channel. This change gives the owner 2 days to discover that something is wrong and recover his/her password and potentially save their channel from getting erased by the vandal. This is most likely to happen if a relationship has gone bad, or something incriminating was found in your private messages when you left your computer briefly unattended.
* Chatroom lines are deleted after MAX_CHATROOM_HOURS or the chat becomes slow ↵Paolo Tacconi2014-07-291-0/+5
| | | | to load
* provide a specific permission for liking profiles (reuse the obsolete ↵friendica2014-07-171-2/+2
| | | | bookmark permission), also remove the unused 'unconnected contacts' view for now.
* provide os_mkdir to workaround permission issues with php mkdirfriendica2014-07-161-0/+9
|
* fix rename_system_url() for the case of somebody who has no local xchan_url ↵friendica2014-07-151-11/+21
| | | | (was cloned from elsewhere and is not primary)
* move smarty compiled files to store/[data]/smarty3 - which puts all ↵friendica2014-07-101-6/+8
| | | | writeable areas of the server except the config file and logs under the "store" directory. We'll do logs at a future time.
* finish implementing email verification. Currently it only applies if ↵friendica2014-07-091-1/+1
| | | | REGISTER_OPEN is in effect.
* minor optimisationfriendica2014-07-011-1/+1
|
* one more...friendica2014-06-301-1/+2
|
* add zottel dir serverfriendica2014-06-291-1/+2
|
* prevent mis-configured servers from leaking cookiesfriendica2014-06-241-2/+10
|
* ability to like thingsfriendica2014-06-231-1/+1
|
* honour the admin censored flag in the directory, and some slow progress on ↵friendica2014-06-221-1/+1
| | | | extended likes
* likes table for liking things besides posts and commentsfriendica2014-06-221-1/+1
|
* Implements a new permission level PERMS_PENDINGAlexandre Hannud Abdo2014-06-191-0/+1
| | | | | | | | | | | | | | | | With this a user can allow some action to any user which connects to them, even before they've connected back. Ref. https://mobiliza.org.br/display/478d9e71eaf55748dc646d3990651d6d34cfb7db5c38360538ec730ca3ccf908@zothub.com Also some code cleanup and an alternative logic for handling notifications of permission changes in zot.php. This assumes that private posts are still restricted to people in your addressbook. Regardless of your global permissions, a pending channel won't get private posts, even if the post only has a deny clause not matching the pending channel.
* load main.js lastfriendica2014-06-131-0/+4
|
* cleanup dead directory entries. This was a real b#tch, so keep your eye out ↵friendica2014-05-281-0/+1
| | | | for issues - which you shouldn't see until next weekend when this is scheduled to run. We're only setting flags, so if anything goes wrong we should be able to recover without too much pain.
* implement 'requires' on personal appsfriendica2014-05-221-1/+1
|
* try to recover from bad updatefriendica2014-05-201-1/+1
|
* add optional context to translationsfriendica2014-05-201-1/+0
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-27 10:43:34 +0000