« Changelog History


Socialhome v0.7.0 Release Notes

Release Date: 2018-02-04 // about 6 years ago

  • 0.7.0 (2018-02-04)

    🆕 New Vue.js frontend

    The work that started at a small hackathon in Helsinki in July 2017 is finally finished! The old buggy and hard to maintain Django template + jQuery based frontend has been completely rewritten in Vue.js. This provides a modern frontend code base, making it possible to add new features faster and to spend less time fixing bugs in the spaghetti code.

    A huge thanks goes out to @christophehenry doing most of the work in pushing this rewrite through!

    ➕ Added

    Possibility to skip adding an OEmbed or OpenGraph preview to content. (#364)

    There is a new checkbox on content create that allows skipping adding a link preview to the content.

    ➕ Add maintenance job to groom precache information from Redis. This ensures Redis memory usage stays stable.

    Important for server admins. There is a new process to run that is responsible for scheduling these maintenance jobs. The process is executed as a Django management command ie python manage.py rqscheduler.

    • If you already use the provided Circus configuration to run Socialhome, you don't need to do anything. When you restart Socialhome, the updated Circus configuration will automatically be used and the scheduler process started by Circus.
    • If you have a custom setup, preferring to run all processes manually, ensure one rqscheduler process is running at all times to ensure maintenance jobs and other future scheduled jobs are executed.

    A new configuration item SOCIALHOME_STREAMS_PRECACHE_SIZE is available to set the maximum size of precached stream items per user, per stream. This defaults to 100 items. Increasing this setting can radically increase Redis memory usage. If you have a lot of users, you might consider decreasing this setting if Redis memory usage climbs up too high.

    🌲 It is now possible to use email for log-in. (#377)

    ➕ Added a Code of Conduct document. All contributors to Socialhome are expected to honour these simple rules to ensure our project is a safe place to contribute to.

    Read the Code of Conduct here.

    Profile API has 4 new read only fields:

    • followers_count - Count of followers the given Profile has. For remote profiles this will contain only the count of followers on this server, not all the followers the profile has.
    • following_count - Count of local and remote profiles this Profile is following. For remote profiles this will contain only the count of profiles following this profile on this particular server.
    • has_pinned_content - Boolean indication whether the local profile has pinned any Content to their profile stream. Always false for remote profiles.

    - user_following - Boolean whether logged in user is following the profile.

    👀 There is now a management command to generate dummy content for development environment purposes. See development pages.

    👀 Installation docs now have an example SystemD service configuration, see installation-other-systemd. (#397)

    Content API has a new read only field has_twitter_oembed. This is true if the content text had a Tweet URL and a fetch for the OEmbed code has been successfully made.

    Content create page now has an option to disable federating to remote servers when saving the content. (#296)

    ⚡️ The content will still update to local streams normally. Federating the content can be enabled on further saves.

    If signups are closed, the signup link will now stay active but will point to a list of Socialhome nodes. (#354)

    🔧 By default this URL is https://the-federation.info/socialhome, but can be configured by the server admin.

    🔄 Changed

    When processing a remote share of local content, deliver it also to all participants in the original shared content and also to all personal followers. (#206)

    👍 Allow creating replies via the Content API.

    Replies are created by simply passing in a parent with the ID value of the target Content. It is not possible to change the parent value for an existing reply or root level Content object once created. When creating a reply, you can omit visibility from the sent data. Visibility will be used from the parent Content item automatically.

    ✂ Removed Opbeat integration related configuration. The service is being ramped down. (#393)

    ⚡️ If as a server administrator you have enabled Opbeat monitoring, it will stop working on this update.

    🆕 New VueJS stream is now default o/ (#202)

    0️⃣ Old stream can still be accessed using the user preferences or by passing a vue=0 parameter in the URL. All existing users have been migrated to use the new VueJS streams by default.

    🛠 Fixed

    📌 Redirect back to profile instead of home view after organize pinned content save action. (#313)

    🛠 Fix searching of an unknown remote profile by handle using uppercase letters resulting in an invalid local profile creation.

    🛠 Fix Content querysets not correctly including the 'through' information which tells what content caused a share to be added to a stream. (#412)

    This information was already correctly added in the streams precalculation phase, but if the cache started cold or a viewing user cycled through all cached content ID's and wanted some more, the database queries did not return the right results.

    Attempt to fetch OEmbed and OpenGraph previews of URL's in content in the order of the links found. (#365)

    Previous behaviour lead to fetching previews of urls in random order, leading to a different url preview on different Socialhome servers.

    🛠 Fix remote profile retrieval from remote servers which don't support legacy Diaspora protocol webfinger. (#405)

    🆕 New version of federation library defaults to trying the new style webfinger with a fall back to legacy.