aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* remote post module so that from anywhere on the web or at least within the ↵friendica2013-10-271-2/+2
| | | | matrix you'll be able to share content or we can have apps on other sites that post status updates on your wall. All with your permission of course as you'll have to click "share" to actually post it.
* a bit more progress on DAV driverfriendica2013-10-271-3/+27
|
* put comanche widgets in their own file. Added a category tagcloud widget - ↵friendica2013-10-273-10/+41
| | | | but the entries aren't going to link to anything until we have a webpage search ability. But this will be a way to exercise and test widget arguments.
* include/reddav.php is the glue between Red attachments and the SabreDav ↵friendica2013-10-261-0/+154
| | | | interfaces. Much work remains beofre we're ready to actually use this interface. Think of it as a conceptual outline and I'm starting to fill it in from the top down.
* create update record for accounts on directory server itself during profile ↵friendica2013-10-244-8/+31
| | | | changes, re-queue failed directory sync packets, fix account_id index in queue creation, be more selective about updating hubloc_connected (only when we're talking to the associated site). But we still need a way to flag dead accounts and these mechanisms won't cut it, because it isn't a requirement that channels communicate with anybody, except for contacting the directory when the account is created. I think we need to make every channel ping the directory once a month. Then we can find those that have not done so (after syncing with other directories). We can't have the directory just flag dead accounts as this would create a way for an anti-social attacker to become a directory server and mark all the accounts dead.
* Optionally pass a prepared "top level" item into conversation(). This will ↵friendica2013-10-242-5/+17
| | | | eventually be used by the photos module where the "top level item" of the conversation is a photo with editing and album navigation controls and doesn't look anything like a post.
* passing vars to widgets in Comanche - !this breaks existing widget declarations!friendica2013-10-241-4/+13
| | | | See the wiki for updated syntax but basically it's now [widget=name][var=varname]varvalue[/var]...[/widget]
* link to source - if it's on the display page link to original source ↵friendica2013-10-203-6/+11
| | | | (probably on a different site). All other conversations link to 'llink' which is a local copy and may provide a richer possibility of interactions, especially if you're logged in locally and it's your own copy of the post.
* prevent posts from floating to the top after minor editsfriendica2013-10-191-1/+6
|
* remove "via wall-To-Wall" text as it's soooo Facebook and is out of place in ↵friendica2013-10-191-0/+1
| | | | derived/sourced channels. It's now just "$author via $xyz".
* doc - complete hook list, still need detailed functional descriptions with ↵friendica2013-10-181-1/+2
| | | | parameters and examples for each
* Put a status editor on the display page if you're logged in. This fixes ↵friendica2013-10-181-1/+1
| | | | issue #113 and also provides the ability to reshare from that page.
* oauth wasn't logging in properly, also fixed api status_show to return last ↵friendica2013-10-152-4/+13
| | | | public post, not the last private post
* directory sync optimisations to save redundant processingfriendica2013-10-152-1/+20
|
* update even if no changefriendica2013-10-141-0/+8
|
* why do these have invalid id's?friendica2013-10-142-2/+2
|
* extra loggingfriendica2013-10-142-2/+5
|
* sync tweaksfriendica2013-10-141-1/+1
|
* don't update old entries with no addressfriendica2013-10-141-1/+1
|
* sql wrong number of argsfriendica2013-10-141-0/+1
|
* sql typo in directory syncfriendica2013-10-141-1/+1
|
* linkify post categoriesfriendica2013-10-141-1/+8
|
* template and icons for categories and "file as"friendica2013-10-141-46/+46
|
* attachment icons revisitedfriendica2013-10-131-28/+50
|
* turn off endless scroll if we have no more content to load - currently for ↵friendica2013-10-131-0/+1
| | | | mod_display, need to add to other content modules
* directory sort links on sidebarfriendica2013-10-131-0/+11
|
* provide config for preferred directory serverfriendica2013-10-131-0/+3
|
* preserve the source owner when creating a delivery fork so that we can ↵friendica2013-10-132-6/+31
| | | | uplink back to them without any ambiguity.
* fix alt_pager to work if item count is higher than page['itemspage'] (threads)zottel2013-10-111-1/+1
|
* more icon tweaks - this could be going on for some time; try to get icon ↵friendica2013-10-101-1/+1
| | | | code (and all theme stuff) out of main code and into templates, but on the short term provide both so nothing breaks.
* more redbasic icon workfriendica2013-10-091-4/+8
|
* nav iconsfriendica2013-10-091-2/+2
|
* replace a bunch of graphic icons with vector iconsfriendica2013-10-082-3/+3
|
* The check for f*cked database (which otherwise sends out zillions of update ↵friendica2013-10-041-3/+3
| | | | failed emails) interferes with install. So what else can we do about f*cked databases which open successfully but don't actually read/write data? It would of course be nice if we didn't have to deal with them, but apparently we do. For now we're not doing anything until I can figure out how to take the site offline when it happens without affecting install.
* fix a bunch of post editing bugs - though this consolidates some disparate ↵friendica2013-10-041-23/+33
| | | | code and may create some new bugs due to regression
* bring back photo shadows (via theme settings)friendica2013-10-021-1/+2
|
* post signaturesfriendica2013-10-024-46/+114
|
* that would've messed it upfriendica2013-10-021-1/+1
|
* directory sync typofriendica2013-10-021-1/+1
|
* block forgeriesfriendica2013-10-022-4/+19
|
* Merge https://github.com/friendica/red into zpullfriendica2013-10-011-2/+2
|\
| * Slightly modify reshares so they can be themed as a whole.Thomas Willingham2013-10-021-2/+2
| |
* | in probe diagnostic - note https failure as diagnostic info - this also ↵friendica2013-10-011-3/+3
|/ | | | changes zot_finger so you can tell it not to fallback. This could be useful in corporate environments that are off the grid or other high security situations (as much as anything could be considered high security which relies on SSL).
* add the auto form submit even though it doesn't seem to work. Will debug it ↵friendica2013-10-011-1/+1
| | | | later.
* Add possibility to use a block a channel menu (set channel_menublock to the ↵zottel2013-10-011-1/+1
| | | | | | lowercase title of the block without special chars) Fix comanche_block() SQL
* implement republish permission for use in sourced channelsfriendica2013-09-303-1/+14
|
* directory sync - this will either work, or it won't work, or it will ↵friendica2013-09-304-64/+192
| | | | | | | | | possibly recurse and blow up the matrix. Hard to say. Do you feel lucky? Well do ya' ... punk? Rule #1 - don't mess with anything unless it's blowing up the matrix. If it doesn't blow up the matrix, but doesn't work, just let it go and let's figure out what it is doing and what it isn't doing. The flow is as follows: Once a day go out to all the directory servers besides yourself and grab a list of updates. This happens in the poller. If we've never seen them before add them to the updates table. The poller also looks to see if we're a directory server and have updates that haven't yet been processed. It calls onedirsync.php to process each one. If we contact the channel to update and don't find anything (we're just doing a basic zot_finger), set a ud_last timestamp. If this is set we will only try once a day for seven days. Then we stop trying to update. This will probably cause a spike the first time through because you haven't seen any updates before, but we spread out the load over your delivery interval.
* there's no $a in comanche_block() (zottel)friendica2013-09-301-1/+2
|
* ret_secret is not usedOlaf Conradi2013-09-301-5/+0
|
* RSS feeds as channel sources. It's feasible and within reach, however ↵friendica2013-09-291-45/+35
| | | | | | | | there's a lot of work left to do. How bad does anybody want it? Let's find out...
generated by cgit v1.2.3 (git 2.25.1) at 2025-01-23 14:47:05 +0000