aboutsummaryrefslogtreecommitdiffstats
path: root/include
Commit message (Collapse)AuthorAgeFilesLines
* ok *now* shred works with alternate config filesfriendica2014-05-071-0/+4
|
* add message_id to reshared items so that we can eventually notify the ↵friendica2014-05-051-0/+6
| | | | original poster via an activity that their item was shared.
* Fixed some wrapping problems when the user has set a larger font size. And ↵jeroenpraat2014-05-051-8/+8
| | | | some UI love for the file permissions page (as requested by Mike ;) and changed the position of the file properties link on the cloud page.
* UI for deleting chatroomsfriendica2014-05-041-0/+3
|
* issue #432 permission changes lost editing webpage (and other non-post items)friendica2014-05-041-2/+0
|
* more easter eggsfriendica2014-05-031-0/+6
|
* make folks from certain other networks feel more at home herefriendica2014-05-021-0/+8
|
* allow birthdays with just a year (no month or day).friendica2014-05-011-5/+10
|
* bring the posted-date selector widget up to date. There are no longer two ↵friendica2014-05-011-1/+1
| | | | different styles.
* 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-302-22/+1
| | | | clutter. Bookmarks can always be saved manually if desired.
* clean up the webpage list a bitfriendica2014-04-291-22/+32
|
* Unfortunate omissionfriendica2014-04-261-3/+1
|
* basic chatterbot support - though these would still require additional ↵friendica2014-04-261-0/+41
| | | | functionality in the API to maintain presence as they'll get kicked out of the room if they don't ping it regularly.
* A useful hookfriendica2014-04-251-0/+5
|
* Set a default directory server from a hard-wired list if one was not ↵friendica2014-04-253-17/+26
| | | | previously chosen.
* A future "comanche UI" is going to need lists of available building blocks. ↵friendica2014-04-251-0/+25
| | | | Some of these are pretty easy to assemble, others are a bit more difficult and will have to go through a registration procedure. This checkin create such a registration procedure for page templates and their associated flavours and their assignable regions. The array itself is extensible since I don't know for sure at this stage what the front-end UI for this feature will ultimately require or even if there ever will be a front-end UI as this community still seems to believe that software writes itself and just magically appears, working perfectly.
* 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
|
* We know why third party zids didn't work now, so don't use hackyThomas Willingham2014-04-181-4/+1
| | | | workarounds anymore.
* 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-172-15/+13
| | | | already received. Incidentally I discovered why we had the meltdown replying to discover channel items the other day - but can't fix it easily.
* tag anyonefriendica2014-04-151-17/+3
|
* better mapping of visible connectionsfriendica2014-04-141-8/+6
|
* Better handling of restricted /channel and /profile permissions. We will ↵friendica2014-04-142-17/+25
| | | | show the name, profile photo and a 'connect' button if appropriate on these pages regardless of permissions. A blank page makes it difficult for folks to figure out how to connect and if it is their real life friend 'x' or not. It also matches our overall policy (adopted from Facebook's lessons learned) that the channel name and default profile photo are always visible and can't really be blocked without messing up the usability of the entire network. This also makes sure that a connect button can be found somewhere besides the directory - where the entry could be blocked; and avoid somebody having to figure out the webbie and find the link to "follow" (another related issue).
* until we can figure out how to allow commenting on the discover page without ↵friendica2014-04-131-0/+7
| | | | killing the matrix, just turn it off.
* Often somebody will join the matrix with a dodgy cert and we'll sort that ↵friendica2014-04-132-12/+26
| | | | out but their profile photo will remain rainbow man (or the site default). However the photo_date has been updated so we won't try again. This checkin looks for such a failure and leaves the photo_date alone if the photo import failed.
* remove extra tag loggingfriendica2014-04-121-1/+1
|
* don't match quote remnantsfriendica2014-04-121-1/+5
|
* let normal hashtags be quoted strings alsofriendica2014-04-121-1/+12
|
* Merge branch 'master' into prvtagfriendica2014-04-121-13/+13
|\
| * Ooops, replaced too manyThomas Willingham2014-04-121-2/+2
| |
| * Revert to prepare_text, use bbcode only for withThomas Willingham2014-04-121-15/+15
| |
* | 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.
* make sure we can find that functionfriendica2014-04-111-0/+1
|
* we also need a loop breakerfriendica2014-04-111-0/+6
|
* Merge pull request #405 from beardy-unixer/masterRedMatrix2014-04-122-17/+18
|\ | | | | A few little fixes
| * Don't count deleted channels when figuring out where to send a user on login.Thomas Willingham2014-04-111-2/+3
| |
| * Bring BBCode to profilesThomas Willingham2014-04-111-15/+15
| |
* | Merge pull request #404 from git-marijus/masterRedMatrix2014-04-122-3/+9
|\ \ | | | | | | bootstrapify aclselector
| * | bootstrapify aclselectormarijus2014-04-112-3/+9
| |/
* / soft revert 9bb7811 until we can look at it more closely.friendica2014-04-111-4/+5
|/
* add the message-id to delivery reports. This _could_ allow an enterprising ↵friendica2014-04-101-14/+14
| | | | developer to collect the delivery reports for a given post and store them in a DB table so that the sender could track and verify where a message had been sent on a web page and verify the success or failure of those attempts without requiring admin access. (To be fair this would also need an extra flag which hasn't yet been implemented to indicate that a channel created a second delivery chain of the message).
* Discover page: when importing public items, alter the item so that it has ↵friendica2014-04-101-0/+19
| | | | the characteristics of one that was sourced by the sys channel instead of just being stored under the sys channel uid. This should allow comments and likes to flow upstream if permissions allow and may fix issue #398. Permission may still be denied by the original poster, but without this the comment/like is treated as a forgery and is blocked from transmission.
* 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-102-6/+1
| | | | 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.
* Merge https://github.com/friendica/red into pending_mergefriendica2014-04-091-4/+3
|\
| * Merge pull request #399 from git-marijus/masterRedMatrix2014-04-101-4/+3
| |\ | | | | | | change the way jot tools are displayed/hidden
| | * use $showacl to show/hide acl in jot.tpl - remove $pvisit and repair ↵marijus2014-04-091-2/+1
| | | | | | | | | | | | editblock and editlayout which still depended on it.