#Socialhome v0.4.0 released

The focus of work lately has been implementing missing features for proper daily usage. One of these is allowing users to share content created by other people. This is now partially possible. Remote shares are now processed and users are able to create shares, but shares are not yet themselves taken into account when creating a stream. Will write another post related to the status with shares and how they will function.

Check out the release here: https://github.com/jaywink/socialhome/releases/tag/v0.4.0

Try it!

Registrations are open at https://socialhome.network . Please be aware some features are still missing, but otherwise the software is very stable. Let us know what you think if you decide to try it!

Participate

Are you a #Django, #Python or #VueJS coder? Want to build a social network? Check out the contribution guide and get in touch!

Changelog

Update notes

This release contains long running migrations. Please allow up to 10 minutes for the migrations to run, depending on your database size.

Added

• Allow user to change profile picture. (#151)

  Profile menu now has an extra option "Change picture". This allows uploading a new picture and optionally setting focus point for cropping a picture that is not square shape.

• Federate local profiles to remote followers on save. (#168)

• Process remote profiles entities on receive.

  Remote profiles were so far only created on first encounter. Now we also process incoming Profile entities from the federation layer.

• When following a remote profile, federate profile to them at the same time.

• It is now possible to expose statistics from a Socialhome node. This includes counts for users (total, 30 day, 6 month), local content and local replies. These will be exposed via the NodeInfo documents that for example the-federation.info node list consumes.

  By default statistics is off. Admins can switch the counts on by setting environment variable SOCIALHOME_STATISTICS=True and restarting Socialhome.

• Add user API token view. Allows retrieving an API token for usage in clients and tools. Allows also regenerating the token if it has been lost or exposed.

• Added bookmarklet to easily share external pages. The bookmarklet can be bookmarked from the 'Create' page. (#138)

  Sharing with the bookmarklet will copy the page url, title and optionally selected text into the create content text area. The bookmarklet is compatible with Diaspora, so for example the Firefox sharing service will work.

• Support receiving 'Share' entities. Show amount of shares on content. (#206)

• Show replies to shares on the original shared content. (#206)

• Add share endpoint to Content API. This enables creating and removing shares via the API. (#206)

• Allow sharing content. Clicking the share counter icon exposes a 'Share' button which when clicked will create a share. (#206)

• Allow unsharing content. Clicking the share counter icon exposes an 'Unshare' button (assuming the user has shared the content) which when clicked will remove the share. (#206)

• Federate local shares to remote nodes. (#206)

• There is now a 'My content' stream link in the navbar 'Streams' dropdown. This goes to your own profile all content stream.

• Add user preference for the new stream refactoring. If enabled, all streams that have a new version in progress will be rendered with the new frontend code based on Vue.js. (#202)

  Warning! The new frontent code doesn't have all the features of the current on yet.

• Content API has three new read only fields available:

  • local, boolean whether the content is local or remote.
  • reply_count, count of replies (including replies on shares)
  • shares_count, count of shares

• Make email notifications nicer by using HTML templates in addition to the plain text version. (#206)

  In addition to reply and follow notifications, send also when own content is shared.

Changed

• Breaking change. Content API results now return visibility as a string ('public', 'limited', 'site' or 'self'), not an integer.

Fixed

• There was no notification sent out when a local user followed a local user. This has now been fixed.

Removed

• Breaking change. Removed Content, Profile and Users API LIST routes. For now these are seen as not required for building a client and allow unnecessarily easy data mining.

• Removed content modal. Clicking timestamp in grid now directly loads the content detail view. (#162)

  Loading the content in a modal was an early experiment and didn't end out very usable.

• Removed reply button from replies. Technically, threaded replies are possible but the UI implementation is not done. Replying to a reply will be back once UI and federation layer will handle threaded replies properly.

#thefederation #federation