aboutsummaryrefslogtreecommitdiffstats
path: root/include/items.php
Commit message (Collapse)AuthorAgeFilesLines
...
* 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.
* enable network/matrix expiration, this should be functional but the options ↵friendica2014-03-031-27/+23
| | | | have been reduced/restricted so we're only looking at network posts and ignore anything that is filed, starred, or is resource_type 'photo' (which should not be possible in non-wall posts, but we just want to be sure). Will require the adventurous tester(s) to set 'channel_expire_days' in their channel record.
* minor stuff, some doco, auth cleanup, and make "unknown" more translateable ↵friendica2014-02-221-1/+1
| | | | by context.
* title missing in private mention postsfriendica2014-02-201-3/+1
|
* project "snakebite"friendica2014-02-171-2/+48
|
* Merge pull request #316 from dawnbreak/masterfriendica2014-02-171-20/+0
|\ | | | | Make asset icons work in subdir installs as well.
| * removed unused function posted_date_widgetKlaus2014-02-161-20/+0
| | | | | | This functions seems not to be used anywhere. include/widgets.php contains widget_archive($arr) which has the same functionality.
* | several things were not working correctly w/r/t community tagging. The ↵friendica2014-02-161-0/+7
| | | | | | | | preference vanished from settings at some point, and we also weren't updating the original post timestamp so that the changed taxonomy would propagate correctly as an edit.
* | strip hard-wired zids from posted links as they will have the wrong identity ↵friendica2014-02-161-1/+10
|/ | | | when somebody tries to view the link
* fix tag delivery default permissions (use channel_allow_cid rather than ↵friendica2014-02-131-11/+11
| | | | allow_cid etc.)
* better bookmark escapingfriendica2014-02-101-2/+3
|
* don't add bookmark tags to naked links inside code blocksfriendica2014-02-101-0/+9
|
* fix the "every other link gets messed up" problemfriendica2014-02-091-1/+3
|
* fix wall photosfriendica2014-02-091-0/+9
|
* that's betterfriendica2014-02-081-0/+2
|
* make all naked links bookmark-ablefriendica2014-02-061-1/+1
|
* add bookmark tag to naked links if they're red sites. We can do this because ↵friendica2014-02-061-1/+1
| | | | red links are linkified when the post is submitted. Can't do this for other naked links because they only get linkified during display and won't have a taxonomy object attached to the message.
* notification bug - don't use $r, we already set it to something else that we ↵friendica2014-02-061-2/+4
| | | | need further on.
* cleanup - nothing morefriendica2014-02-051-3/+3
|
* fix auto-add of bookmarks to find sender correctly and optionally auto add ↵friendica2014-02-051-4/+10
| | | | bookmarks for self
* This would be about the 75th attempt to try and prevent duplicated email ↵friendica2014-02-051-1/+10
| | | | notifications for comments. Eventually we'll find something that works.
* bookmarkingfriendica2014-02-041-0/+15
|
* transmit, receive, and parse bookmarksfriendica2014-02-031-2/+8
|
* provide some interesting new options to channel sourcesfriendica2014-01-311-2/+2
|
* some tweaks to items_fetch for the apifriendica2014-01-251-2/+5
|
* Merge pull request #284 from cvogeley/masterfriendica2014-01-251-5/+10
|\ | | | | API changes
| * API My wall postsChristian Vogeley2014-01-251-3/+5
| |
| * Add $since_id to items_fetchChristian Vogeley2014-01-221-2/+5
| |
* | try to reduce the number of simulaneous deliveries of the same post when ↵friendica2014-01-221-13/+20
|/ | | | dealing with owner relays that have more than one channel instance. If things melt down in the next few hours and I'm not available please revert this. I've reviewed a few times and think it's OK, but this part of the delivery code is traditionally touchy.
* dav: throw exception if channel for requested DAV directory is deletedfriendica2014-01-151-2/+4
|