aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* removeme sort of works for a single channel - lots of loose ends to deal ↵friendica2013-11-121-22/+36
| | | | with but it's a start
* Fix missing argument warningOlaf Conradi2013-11-121-1/+1
|
* ability to use other ciphersfriendica2013-11-111-0/+5
|
* localise js ui strings for e2eefriendica2013-11-111-7/+9
|
* looks more structured this waymarijus2013-11-111-0/+1
|
* turn safemode into a proper widgetfriendica2013-11-111-0/+1
|
* change wording on feature to "even more encryption" because otherwise it ↵friendica2013-11-111-1/+1
| | | | sounds like we don't have any at all - and we certainly do.
* display encrypted text inlinefriendica2013-11-111-2/+5
|
* Merge https://github.com/friendica/red into zpullfriendica2013-11-101-1/+1
|\
| * More safe search - since the default is one, toggle only works afterThomas Willingham2013-11-111-1/+1
| | | | | | | | | | an initial xconfig is set - the first one will turn safe search on (ie, do nothing from a users point of view). Fix that.
* | e2eefriendica2013-11-102-0/+3
|/
* Didn't finish it. Gotta' pee.friendica2013-11-101-9/+2
|
* too much privacy on get_plink() which is left over from Friendica daysfriendica2013-11-101-1/+1
|
* Stray lineThomas Willingham2013-11-091-3/+0
|
* Clean upThomas Willingham2013-11-091-1/+1
|
* Bring safe search to the UIThomas Willingham2013-11-091-0/+18
|
* we should probably only expire things once...friendica2013-11-071-1/+4
|
* update smiliesfriendica2013-11-071-0/+2
|
* more e2ee infrastructure - at this point if somebody wants it they're going ↵friendica2013-11-071-2/+39
| | | | to have to work for it.
* provide expire feature on post and comments as well as private messages. ↵friendica2013-11-073-4/+14
| | | | This requires a feature setting and is currently unmaskable - if the author says it's gone, there's not a lot you can do to stop it or try and save it. It's gone.
* allow private mail sender to set an expiration on their messages. Once ↵friendica2013-11-063-4/+20
| | | | expired the message is destroyed at both ends (subject to the granularity of the polling interval) and is gone. Officially it takes some form of language independent string like 2013/11/22, but English speakers can use anything that strtotime() understands, like "+30 minutes" or "next Tuesday".
* more work on channel removal - it might sort of work now but I'm expecting ↵friendica2013-11-051-4/+22
| | | | lots of issues. Hence there is still no code in chanman to start the process rolling and make it happen. Will need a barrage of test cases.
* fix private group deliveryfriendica2013-11-051-3/+4
|
* don't store update records if we're not a directory server of some kindfriendica2013-11-041-0/+5
|
* make the storage permissions tweakable for hosted environments where they ↵friendica2013-11-041-2/+2
| | | | may require tweaking.
* solid progress on attach_mkdir - but we need to figure out where to store ↵friendica2013-11-041-11/+73
| | | | default file permissions. This should be separate from post/item permissions and we won't be able to set permissions from the DAV interface so if we want something private we have to provide these permissions in our preferences.
* tag notifications for private posts contain obscured data - they should be blankfriendica2013-11-041-1/+1
|
* private tagged posts weren't creating second delivery chain - they were ↵friendica2013-11-041-1/+14
| | | | incorrectly being marked as "in a reshare" due to being obscured.
* add attach_mkdir()friendica2013-11-031-0/+71
|
* Merge https://github.com/friendica/red into zpullfriendica2013-10-301-3/+7
|\
| * Use only one regex for title matching in rpost tagzottel2013-10-311-6/+5
| |
| * Allow setting of title in rpost tag with [rpost=title]body[/rpost]zottel2013-10-301-1/+6
| |
* | issue #189 - show post edited time on relative date hovertipfriendica2013-10-302-0/+2
| |
* | allow zot public providers to list their location, as a non US-based server ↵friendica2013-10-301-3/+7
|/ | | | could be a strong selling point.
* access policy and directory mode were crossed on site table creationfriendica2013-10-301-1/+1
|
* send rpost requests from remote sites back to yours.friendica2013-10-291-2/+2
|
* rpost bbcode tagfriendica2013-10-292-3/+21
|
* docofriendica2013-10-281-0/+18
|
* Comanche documentation and some cleanup of layout page (including link to ↵friendica2013-10-282-2/+13
| | | | doco) and a few other webpage related cleanups
* implement monthly directory pingsfriendica2013-10-282-3/+34
|
* 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".
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-14 04:16:30 +0000