aboutsummaryrefslogtreecommitdiffstats
path: root/version.inc
Commit message (Collapse)AuthorAgeFilesLines
* rev updatefriendica2014-10-031-1/+1
|
* issues with diaspora comment signatures on relayed comments that are relayed ↵friendica2014-10-021-1/+1
| | | | through a redmatrix site (parent post is redmatrix) and involve a private post.
* ability to pre-populate connections for new channels. e.g. "MySpace Tom"friendica2014-10-011-1/+1
|
* allow site specific templates, css, js, whateverfriendica2014-09-301-1/+1
|
* implement a "powered-by" but leave it turned off until somebody with a good ↵friendica2014-09-291-1/+1
| | | | eye for layout can figure out where best to put it.
* some background work for import/export of things and liked things/profilesfriendica2014-09-271-1/+1
|
* doc updates, clean up buttons on PM edit template to match other edit buttonsfriendica2014-09-261-1/+1
|
* optionally include wall items (posts) in import/exportfriendica2014-09-251-1/+1
|
* just an experiment - don't do anything with this until I'm finished with it.friendica2014-09-241-1/+1
|
* more work on d* private messagesfriendica2014-09-231-1/+1
|
* private mail from d* to r# seems to work with these edits. - Now have to go ↵friendica2014-09-221-1/+1
| | | | back the other way.
* feeds with '@' in the URL were being handled as webfinger addresses and ↵friendica2014-09-211-1/+1
| | | | didn't fall through to RSS discovery. Issue #599
* fix empty likesfriendica2014-09-201-1/+1
|
* try to sort out walltowall translation for diaspora recipientsfriendica2014-09-191-1/+1
|
* repeated content collapse on update from display page under rare conditions ↵friendica2014-09-181-1/+1
| | | | (when the conversation hasn't changed)
* implement permission roles - the backend should be done except for maybe a ↵friendica2014-09-171-1/+1
| | | | couple of small tweaks. Now we just need to define the rest of the roles and create a chooser for them. Adam started on this some time back but I don't know where that has gone.
* use the more portable encoded_item format for exported items - but with ↵friendica2014-09-161-1/+1
| | | | added attributes so we can use it as a reasonably complete item backup. The encoded_item format gives us extended author and owner information in case we need to probe them to bring the entry back. It also contains taxonomy entries. Importing and/or recovering will best be accomplished in chunks. It could take some time and some memory to chew through this.
* rev updatefriendica2014-09-151-1/+1
|
* more heavy lifting on the hubloc management and revocation infrastructure; ↵friendica2014-09-141-1/+1
| | | | don't rush me. This is going to become a fundamental part of zot. It deserves careful consideration.
* some backend work for the remaining missing bits of mod_hubman - this is ↵friendica2014-09-131-1/+1
| | | | still a fair ways from being complete and is not ready for prime time. Basically we'll let a channel send out a public message saying "these are my currently approved locations" and anything that isn't in the list will be marked deleted. We'll send out this message when locations change somehow - either through direct personal involvement (hub revoke, change primary, channel import) or during a system rename or "find bad/obsolete hublocs" activity. This way we won't have clones sending back location info we just got rid of and re-importing the bad entries.
* doc updates and a couple of issues spotted in the logs (diaspora likes, feed ↵friendica2014-09-121-1/+1
| | | | author import)
* issue #588 can't add feeds to collections using connedit page group sidebar ↵friendica2014-09-111-1/+1
| | | | widget
* don't include plus-sign in the stored term for imported mentionsfriendica2014-09-101-1/+1
|
* d* friending vsprintf errorfriendica2014-09-091-1/+1
|
* import_profile_photo array warningsfriendica2014-09-081-1/+1
|
* Diaspora actually puts the account full name into the "nickname" field of ↵friendica2014-09-071-1/+1
| | | | the vcard. They don't put the nickname into the vcard at all. One wonders why even have a nickname field since the fullname is already presented in the next line. This hasn't caused us a problem with Friendica because I'm guessing nobody actually uses this line, though the number of class tags on it makes it seem somewhat important.
* ajax workfriendica2014-09-061-1/+1
|
* doc updatesfriendica2014-09-051-1/+1
|
* allow stuff with Diaspora authors to federate in zot conversations even if ↵friendica2014-09-041-1/+1
| | | | the local site has diaspora disabled. This way it won't look like folks are talking to themselves.
* outbound feed issuefriendica2014-09-031-1/+1
|
* updated compatibility notesfriendica2014-09-021-1/+1
|
* honour the feed_contacts settingfriendica2014-09-011-1/+1
|
* sql error in profile_activityfriendica2014-08-311-1/+1
|
* insecure network filterfriendica2014-08-301-1/+1
|
* doc updatefriendica2014-08-291-1/+1
|
* make blocks, webpages, and layouts postable (pre-filled forms if supplied ↵friendica2014-08-281-1/+1
| | | | from elsewhere). The only serious issue is with ordering - you have to process and save a named layout before you can save a webpage that uses that layout name. Otherwise it will get unset during the save.
* compatibility notesfriendica2014-08-271-1/+1
|
* take off the kid glovesfriendica2014-08-261-1/+1
|
* re-obscure item body if localize_item() changes it. It's already flagged as ↵friendica2014-08-251-1/+1
| | | | obscured so we need it to actually be obscured.
* diaspora discoveryfriendica2014-08-241-1/+1
|
* switch everything over to crypto_encapsulate()friendica2014-08-231-1/+1
|
* rev updatefriendica2014-08-221-1/+1
|
* abook-edit-me class lost during some edit - we need this to reset the ↵friendica2014-08-211-1/+1
| | | | permission fields
* greatly simplify consume_feed() - a lot of this was friendica specific and ↵friendica2014-08-201-1/+1
| | | | somebody may want to put some of it back in, but we'd be much better off building a zot compatible feed for friendica (hint,hint) - even if it didn't support the other protocol bits. Special purpose feed handlers for things like likes, dislikes, events, and community tags are better handled as zot arrays. We have all those handlers. We just need to pass them a JSON message instead of an XML/Atom message. Handlers for statusnet follow messages are another casualty. That's easy to bring back - but we need to keep driving nails into the XML coffin or the damn zombies will get out.
* diaspora - crazy amount of work remainingfriendica2014-08-191-1/+1
|
* nav channel selectionfriendica2014-08-181-1/+1
|
* add collections widget to connections page - and some more work on realmsfriendica2014-08-171-1/+1
|
* provide backend storage and declaration of directory realmfriendica2014-08-161-1/+1
|
* doc updatefriendica2014-08-151-1/+1
|
* put an indicator (*) in the message subject line for notification emails ↵friendica2014-08-141-1/+1
| | | | when the message body has been suppressed