aboutsummaryrefslogtreecommitdiffstats
path: root/include/items.php
Commit message (Collapse)AuthorAgeFilesLines
* implement max_import_sizefriendica2014-08-091-1/+7
|
* booboofriendica2014-08-091-1/+2
|
* a couple of "not quite public" fixesfriendica2014-08-081-10/+6
|
* cleanup some text where we said "public" or "visible to anybody on the ↵friendica2014-08-071-1/+1
| | | | internet" when that isn't necessarily true.
* a bit more cleanup and a bug fix or two for the new private post security modelfriendica2014-08-071-8/+15
|
* public scope delivery issuesfriendica2014-08-061-2/+5
|
* basic 'notpublic' bits workingfriendica2014-08-061-6/+28
|
* first step first - just store the public_policy data, don't do anything with ↵friendica2014-08-061-0/+12
| | | | it yet.
* add an encoding type to formatted zot communication structures so that we ↵friendica2014-07-241-0/+2
| | | | can later add alternate encodings.
* clean up more code duplicationfriendica2014-07-141-1/+1
|
* remove some code duplicationfriendica2014-07-141-18/+4
|
* when deleting items, delete linked events and photos during stage1friendica2014-07-041-13/+13
|
* minor optimisationfriendica2014-07-011-8/+4
|
* notification being sent for comments from blocked connections on same site.friendica2014-06-261-0/+1
|
* process profile like removals with normal low_level drop_itemfriendica2014-06-231-0/+9
|
* Implements a new permission level PERMS_PENDINGAlexandre Hannud Abdo2014-06-191-6/+8
| | | | | | | | | | | | | | | | 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.
* access control modification functions (item specific - we may need these for ↵friendica2014-06-171-0/+35
| | | | several data types)
* issues with editing webpage permissionsfriendica2014-06-151-2/+4
|
* webpage permissions weirdnessfriendica2014-06-141-6/+8
|
* poke notificationsfriendica2014-06-041-0/+28
|
* Make tag delivery work when channel name differs from profile nameAlexandre Hannud Abdo2014-05-211-5/+5
|
* zrlify (turn into zmg) any relevant img tags in a post.friendica2014-05-131-0/+25
|
* issue #432 permission changes lost editing webpage (and other non-post items)friendica2014-05-041-2/+0
|
* posted_dates() needs a re-write so we can make a much prettier archive widgetfriendica2014-04-301-1/+41
|
* Remove automatic bookmarking - it was a bad idea and just leads to menu ↵friendica2014-04-301-21/+0
| | | | clutter. Bookmarks can always be saved manually if desired.
* A useful hookfriendica2014-04-251-0/+5
|
* ability to unset a layout and subthread is probably close to working again.friendica2014-04-231-8/+24
|
* this should fix mention notification that aren't plus taggedfriendica2014-04-191-4/+20
|
* more optimisations for discovery mode of zotfeedfriendica2014-04-171-2/+6
|
* improve zotfeed for discover channel so it will send updates to posts you've ↵friendica2014-04-171-7/+7
| | | | already received. Incidentally I discovered why we had the meltdown replying to discover channel items the other day - but can't fix it easily.
* no this is the way to do itfriendica2014-04-111-2/+2
|
* Use @+ to tag a forum and also restrict the post to the forum, this leaves ↵friendica2014-04-111-2/+2
| | | | @! tags private - period.
* move the deleted flag setting to encode_item_flags() where it belongs now ↵friendica2014-04-101-4/+3
| | | | that we aren't giving deleted posts special treatment.
* Include the entire original item when notifying other channels of deletions ↵friendica2014-04-101-5/+0
| | | | as it contains important routing and scope information. Previously we were only sending a couple of critical fields like the message-id, flags, and creation date. The thinking was that it is deleted, let's not resend the deleted contents anywhere. But in order to route this through the same path the original post took we really need the entire original post with all of its baggage attached.
* wrong var name in add_source_routefriendica2014-03-311-2/+2
|
* crank up loggingfriendica2014-03-311-0/+2
|
* community tags don't show up in the tagged posts because we removed the ↵friendica2014-03-311-0/+1
| | | | displayed list of hashtags at the bottom (which are usually redundant since hashtags are usually present in the message text). This brings them back, but only for tags which aren't currently present in the message body (e.g. community tags)
* Merge branch 'route'friendica2014-03-311-1/+33
|\
| * docofriendica2014-03-311-0/+5
| |
| * finish up the source route storage so we can prevent messages from flowing ↵friendica2014-03-311-17/+10
| | | | | | | | upstream in complicated delivery chains
| * source routing stufffriendica2014-03-291-0/+34
| |
* | issue #378, failure to correctly link tags where one tag contains a ↵friendica2014-03-301-0/+1
|/ | | | substring of the other (depends on the order they are discovered).
* try and sort out the item delete messfriendica2014-03-271-14/+51
|
* need includefriendica2014-03-261-0/+2
|
* there's the problemfriendica2014-03-261-4/+5
|
* more work on firehosefriendica2014-03-261-1/+1
|
* allow zotfeed to create a firehose of a site.friendica2014-03-261-11/+20
|
* cheange encode_item() logging to logger_data because it's way too noisy and ↵friendica2014-03-231-1/+1
| | | | had no loglevel set
* cleanupfriendica2014-03-181-13/+15
|
* Red API: /api/red/item/new ; which is like /api/statuses/update except it ↵friendica2014-03-041-2/+2
| | | | uses Red semantics and returns success/failure indication.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 17:03:25 +0000