aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
...
* skip trying to come up with an intelligent way to decide what photos should ↵friendica2015-03-111-19/+1
| | | | get a status post - leave it manual.
* allow urls using the zot: or zots: URL schemes to exist without getting ↵friendica2015-03-101-1/+1
| | | | filtered away.
* Merge https://github.com/friendica/red into pending_mergefriendica2015-03-101-31/+58
|\
| * Fix SQL query for removing orphan hooks.Klaus Weidenbach2015-03-101-31/+58
| | | | | | | | | | initialize some variables before using them. commented out some unused variables.
* | Change logic of "don't create a status post for this photo upload" and turn ↵friendica2015-03-102-3/+3
|/ | | | it into a bona-fide on/off toggle. This takes up one more vertical line, but we have it to spare, and the single button (while concise visually) provided no feedback of the current state, or indicate whether a second click toggled it. Some addons use this setting so addons will need to be pulled when this is pulled in order to remain in sync.
* View upload photo button only if you have permission.Klaus Weidenbach2015-03-101-59/+54
| | | | | | | | | | Check if post_photos permission is available otherwise hide the photo upload button. Or should we show the button and just disable it with a title, about missing permission to upload photos? In comments we use the same icon, but just add [img] bb-code. Should we provide this if no permission to upload photos. Do we need different icons for [img] and photo upload buttons?
* diaspora's spammy permission model seems to have leaked through our ↵friendica2015-03-101-2/+5
| | | | firehose. Don't let it.
* more work on queue optimisationsfriendica2015-03-093-7/+39
|
* whitespacefriendica2015-03-091-2/+1
|
* make network page default options work more or less universally instead of ↵friendica2015-03-092-5/+6
| | | | just from the navbar, and fix some saved-search weirdness related to the delete-term icon
* Allow site to over-ride directory options. Bugger off.friendica2015-03-091-38/+31
|
* 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-083-3/+21
| | | | 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
* add reddress to profile - but all is not as it seems. Copy to clipboard is ↵friendica2015-03-071-4/+7
| | | | blocked because it isn't really a reddress and won't work if you copy it and try and use it somewhere. We should really convert the symbol back to '@' on copy and allow it to be copied, but this isn't as easy as it sounds and is left as an exercise for the community. If we just allow it to be copied we'll get a lot of bugs that making friends doesn't work. It does, but that isn't a legitimate reddress and even if we made allowances for it, Diaspora and Friendica and other webfinger based services wouldn't and would just say it can't be found or it's an illegal address. So if we block copy we'll just get bugs that it can't be copied. Eventually somebody will see this checkin and take it on themselves to figure out how to fix the address when copied to clipboard and then allow it to be copied. And there will be joy.
* when fixing "naked links" make sure not to double link double urls as seen ↵friendica2015-03-061-1/+1
| | | | in archive.org - which has the complete unescaped target url, scheme and all, as part of its own.
* major cleanup of directory optionsfriendica2015-03-051-2/+9
|
* straighten out some directory stuff, which required some Comanche structural ↵friendica2015-03-053-36/+59
| | | | changes
* Merge pull request #918 from dawnbreak/masterRedMatrix2015-03-061-1/+2
|\ | | | | RedDAV: fix renaming files.
| * RedDAV: fix renaming files.Klaus2015-03-061-1/+2
| | | | | | | | How can no one have spot this bug yet?!? Is no one using WebDAV? Took me 2 days to figure out it was not my RedDAV rewrite, but that this should have never worked. :-!
* | the link icon on comments now calls the link parsing tool (just like the ↵friendica2015-03-041-0/+1
| | | | | | | | main editor window). Eventually the link specific icons (image, link, audio, video) will all be handled by inserting a link using the link icon (here and in the main editor window) and the separate buttons will go away. We also need to tie this to oembed so that there's one place to insert a link - no matter what kind of link it is, and we'll try to find the best way to render that as content. Similarly upload will upload content, no matter what kind of content; and we'll likewise try and figure out the best way to present whatever content was uploaded (img, file, audio, video, whatever).
* | Deprecate the "wall uploads" photo album. Photo uploads (from any source) ↵friendica2015-03-041-1/+1
| | | | | | | | with no album specified will go now into an album based on YYYY-MM.
* | missing commafriendica2015-03-041-1/+1
| |
* | don't re-use $xfriendica2015-03-041-2/+2
| |
* | add queue priorityfriendica2015-03-041-0/+18
| |
* | parse_url: if url returns an image/audio/video file instead of a webpage, ↵friendica2015-03-041-0/+7
|/ | | | return the bbcode for the appropriate content type. This results in two web fetches of the url in question, but the first one is just a HEAD. This way we won't try and download and parse an entire video. TODO: img's are checked to see if they should be zid-ified, but audio/video currently are not.
* notes on what's needed to fix the queueing algorithms.friendica2015-03-041-0/+8
|
* enable sql_extra on pdl_selectorfriendica2015-03-031-2/+2
|
* Merge https://github.com/friendica/red into pending_mergefriendica2015-03-037-175/+174
|\
| * Some cleanups and documentation.Klaus Weidenbach2015-03-047-175/+174
| | | | | | | | | | | | | | 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.
* | I'm going to use the site_update timestamp to indicate whenever we ↵friendica2015-03-031-0/+15
| | | | | | | | successfully connect with a site. This way we can mark hubs dead on non-directory servers; but we have to wait before implementing this until we have a history of site_update being updated.
* | don't let a zot-finger bring a dead hub back to life unless it's the site ↵friendica2015-03-031-5/+7
|/ | | | we're currently talking to.
* tagcloud tweaksfriendica2015-03-021-2/+2
|
* make public delivery to contacts or any connections work againzottel2015-03-021-3/+2
| | | | $hash wasn't defined in this case
* increase the dynamic range of the tag clouds slightly.friendica2015-03-011-1/+1
|
* Nag hub admins with self-signed certs to fix them. Otherwise we'll just have ↵friendica2015-03-011-0/+1
| | | | | | to start marking them as dead sites.
* The never ending saga of parent = 0 bugs on Dreamhost.friendica2015-03-011-0/+10
|
* queue management actions. Still needs further work such as indication of ↵friendica2015-03-011-2/+3
| | | | last successful connection or indication that the hub was marked offline, but these are potentially expensive queries.
* Fix a couple of places where we weren't checking for dead hublocs. Add a ↵friendica2015-02-272-6/+24
| | | | function to mark a hubloc dead.
* Merge https://github.com/friendica/red into pending_mergefriendica2015-02-261-0/+3
|\
| * more fake null shenanigansHabeas Codice2015-02-261-0/+3
| |
| * Revert "more fake null shenanigans"Habeas Codice2015-02-261-23/+94
| | | | | | | | This reverts commit b57010e3da6c0521121a622c27013c8af7678132.
| * more fake null shenanigansHabeas Codice2015-02-261-94/+23
| |
* | loop breakerfriendica2015-02-261-0/+16
|/
* syntax - missing argfriendica2015-02-251-1/+1
|
* this may actually fix the deliver loop when deleting existing items. It's ↵friendica2015-02-252-1/+23
| | | | hackish but I don't see any other way out.
* Found the cause of the delete looping, and I can prevent it going forward. ↵friendica2015-02-253-15/+54
| | | | The issue remains what to do about comments which are already in the DB and have ITEM_ORIGIN incorrectly set. We can't exactly reset them because the "original" context has been lost. (Sorry but couldn't resist an insider pun that none of you will be able to follow anyway). Read the comments.
* call post_local hooks prior to storing a post that is going to be sourced. ↵friendica2015-02-252-0/+9
| | | | There are some fields in the actual stored item that may change when we start the second delivery chain so a few plugins may not deal with these items correctly. Since we only source public items these effects will be slight.
* solve some (hopefully most) missing delivery issuesfriendica2015-02-251-13/+55
|
* don't send deleted items upstream - only downstream.friendica2015-02-241-3/+6
|
* require access token to view, query, or join directories in private realms, ↵friendica2015-02-241-6/+12
| | | | if the realm is so configured.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-05 10:01:11 +0000