Socialhome v0.6.0 Release Notes

Release Date: 2017-11-13 // over 4 years ago
  • 0.6.0 (2017-11-13)

    โž• Added

    Profile "All content" streams now include the shares the profile has done. (#206)

    ๐Ÿ’ป Streams API now has endpoints for profile streams to match the profile streams in the UI. (#194)

    • /api/streams/profile-all/{id}/ - fetches all content by the given profile (including shares), ordered by created date in reverse order (= new stuff first).

    - /api/streams/profile-pinned/{id}/ - fetches pinned content by the given profile, ordered as set by the profile owner.

    ๐Ÿ†• New fields added to Content API:

    • is_nsfw, boolean value, true if the content text has the tag #nsfw in it.

    - share_of, if the content_type is share, this will contain the ID of the shared Content.

    If an incoming share references a remote target that doesn't yet exist locally, it and the author profile will be fetched and imported over the network. (#206)

    ๐Ÿ‘€ There are now Docker files for doing development work for Socialhome. See the docs here.

    ๐Ÿ”ง Third-party applications can now be added to enhance Socialhome or replace some of the core functionality, using configuration. The following new settings are available:

    • SOCIALHOME_ADDITIONAL_APPS - List of additional applications to use in Django settings.
    • SOCIALHOME_ADDITIONAL_APPS_URLS - Additional third-party URL's to add to core url configuration.

    - SOCIALHOME_HOME_VIEW - Override the home view with another view defined with this setting.

    Content API now has a new shares endpoint. (#206)

    This allows retrieving all the shares done on a Content.

    ๐Ÿฑ We now have a logo โœŒ


    ๐Ÿ‘€ The logo also comes in a light version, for dark backgrounds. See brand for details.

    ๐Ÿ”„ Changed

    ๐Ÿ”ง Logging configuration changes:

    • Removed separate logfile for the federation loggers. Now all logs go to one place. Setting SOCIALHOME_LOGFILE_FEDERATION has been removed.

    - Added possibility to direct Django and application logs using a defined level to syslog. Adds three settings, SOCIALHOME_LOG_TARGET to define whether to log to file or syslog, SOCIALHOME_SYSLOG_LEVEL to define the level of syslog logging and SOCIALHOME_SYSLOG_FACILITY to define the syslog logging facility. See configuration documentation.

    Important! The file to place configuration environment variables has changed to .env.

    โš  This is a more standard file name for environment variables than the previous env.local. For now we'll still load from the old file too, but a warning will be displayed to rename the file.

    ๐Ÿ’ฅ Breaking change. API Content serialization now returns list of tags as name of tag, not ID as before. The names do not contain the character "#".

    Content API replies endpoint now includes all the replies on the shares of the Content too.

    ๐Ÿ‘‰ Use modified timestamp for created timestamp when federating out to remote nodes. (#314)

    ๐Ÿ‘ This makes edits federate more reliably to some remote platforms that support edits.

    Stream grid item reply icon changed from "envelope" to "comments". (#339)

    ๐Ÿ›  Fixed

    ๐Ÿ›  Fix various issues with OpenGraph tags parsing by switching to self-maintained fork of python-opengraph.

    Share button is no longer visible if not signed in (#325)

    ๐Ÿ›  Remote profile image urls that are relative are now fixed to be absolute when importing the profile from remote (#327)

    ๐Ÿ›  Fix poor performance of fetching replies.

    ๐ŸŽ When adding replies of shares to the collection of replies fetched when clicking the reply icon in the UI, a serious performance regression was also added. Database queries have now been optimized to fetch replies faster again.

    When editing a reply, the user is now redirected back to the parent content detail view instead of going to the reply detail view. (#315)

    ๐Ÿ›  Fix regression on visibility of remote replies on shares.

    ๐Ÿš€ Replies inherit the parent object visibility and share visibility defaults to non-public in the federation library. Diaspora protocol removed the public property from shares in a recent release, which meant that we started getting all shares as non-public from the federation layer. This meant that all comments on the shares were processed as non-public too.

    0๏ธโƒฃ With a change in the federation layer, Diaspora protocol shares are now public by default.

    Fixed Streams API content user_is_author value always having false value.