Long overdue, this release brings a few long awaited features and privacy related improvements. A total of 105 commits went into this release by two authors, changing 175 files (4476 insertions, 1958 deletions).
This release makes #Socialhome and #GDPR friends. Users can now delete and export their data, and admins can publish terms and privacy documents.
Other main features include support for limited content, notifications on mentions, admin improvements, tag search and the new local content stream. See below highlights for more details.
Highlights
Limited content is now supported 🙈 💪
Limited content can now be created using the web create form. Note, API does not currently allow creating limited content (except replies to limited content). Once create form is ported to the API, things should be refactored there, right now had no bandwidth to ensure both work.
Limited content is shown in the stream with a lock symbol. The create shows some extra fields for limited content. These include “recipients” and “include following”. Recipients is a comma separated list of target profile handles the limited content will be sent to. Include following will populate recipients (on save) with all the profiles that one follows. Later on we will add contact lists for better targeting.
Limited content visibilities can be edited. If someone is removed from the target recipients, a retraction will be sent to try and delete the content remotely from the target recipient.
Currently recipients must already be known to the server, in the future a remote search will be done if the profile is not known. Any known remote profile can be targeted - it is up to the receiving server to decide whether to accept it or not. For local profiles, those of visibility SELF (ie hidden) cannot be targeted.
There is also a new stream “Limited” available. It shows all limited content visible to you.
Add “Local” stream which contains only content from users registered on the same server.
Mentions are now parsed out of incoming remote content and locally created content.
Currently the only syntax supported is the #Diaspora mentions syntax, ie @Name. Currently Socialhome users can create mentions by using the syntax manually. UI layer will be added later to choose people using the standard @ syntax to trigger search.
Searching for hashtags is now possible using the global search
Admins can now add Terms of Service and Privacy Policy documents to the site. Default templates are provided in the admin. These can be published as is or modified to suit the site.
Users can export their data from the account settings. In addition to user and profile data, this export contains a list of profiles followed, content (including shares and replies) and a zip file of image uploads. An email notification will be sent to the user once the export is ready for download from the account page.
Add possibility to delete user account. Deletion is permanent and will delete all created content including uploaded images. Delete request for profile and related content will be sent to remote servers.
Admin pages are now linked to from the new navbar cogs dropdown menu. New admin pages have been added for content and profiles.
Many fixes to stabilize the resource usage of streams precaching.
Limited content initial support was one of the goals of this release, and that has now been done. One of the other most wished for features has been the possibility to follow tags. This will most likely be included very soon for the next release.
The one major feature that has been postponed for a long time is #ActivityPub support. To finally move this forward, it is likely that no other large features will be worked on for the next release other than following tags and adding ActivityPub support to the federation layer.
Source code hosting
This release will most likely be the last release done exclusively through #GitHub. Migration will soon happen to a #Gitlab instance. While development will happen through Gitlab, there will be mirroring to the current GitHub repository, so that contributing through that will also be possible.
What is Socialhome?
Socialhome is best described as a #federated personal profile with social networking functionality. Users can create rich content using #Markdown. All content can be pinned to the user profile and all content will federate to contacts in the federated social web. Currently federation happens using the Diaspora protocol. Federating using existing protocols means Socialhome users can interact with tens of thousands of other users.
Please check the official site for more information about features. Naturally, the official site is a Socialhome profile itself.
Want to work on a #Django and #Vue.js powered social network server? Join in the fun! We have easy to follow development environment setup documentation and a friendly chat room for questions.
#litepub's minimalist approach (less is more) helps to create a more secure social networking environment for everybody.
it gives users more control over the objects they publish by requiring object fields always be referenced by IRI. this means that users who want to keep some posts outside public view are better protected, such as marginalized users.
simplification of #activitypub messages makes mitigating spam and other issues more easy from a programmatic viewpoint.
simplification of the #activitypub S2S protocol makes implementation easier, which provides for a more robust ecosystem. the planned extension system allows for rapid iteration of extensions in a way that is compatible with #activitypub, allowing for development of features such as E2E encryption in objects.
Trying to drum up support for adding #ActivityPub to #Ghost#CMS, we are quickly moving up the list of 'Ideas' and currently at 6th place in view count on their idea tracker in a matter of a few days.
@z428 these are solvable problems. #Hubzilla allows full portability of accounts between hosts using the #NomadicIdentity aspect of their #Zot protocol. At the moment we are using #fediverse 1.0. Once all the codebases have #ActivityPub support rolled out, and added all the features that makes available we will get to fediverse 2.0. Full portability of accounts between hosts will come with a fediverse 3.0, based on a protocol set that either extends AP or replaces it.
@GeekDaddy Yeah, that's sad. Unfortunately the FOSS, git based code hosting platforms seem to be dragging their feet on federation.
Personally I can't wait for #Gitea or #Gogs or #Gitlab or similar to federate via #ActivityPub. Personally I feel that will be a defining moment for the #FOSS community in taking back out sovereignty from #GitHub / #Microsoft.
@switch@artsyhonker yes, "podcasting" began as Apple-speak for 'delivering audio blogs by #RSS' before it became a generic buzzphrase ;P But like YT does for video, iTunes does more than just delivery, it's also a place to discover new content and new creators. We've had #FreeCode tube site stacks for years (#Plumi, #MediaGoblin etc), but #PeerTube is a game changer because is allows federated search across multiple independent tube sites via #ActivityPub.
ActivityPub is still very young, only a couple months old.
Its great to see so much enthusiasm and new projects.
The network effect applies just as it does to traditional silo'd social media platforms.
It's just a matter of time for the fediverse to grow and become mainstream enough to sustain that model while providing a superior experience. #activitypub
GNU Social is joining #ActivityPub side of the #fediverse thanks to the hard work of @up201705417! Federate all the things! Standards are powerful things!
My hero in this regard is @Gargron. He built a huge community and revitalized the fediverse at a crucial time and I don't think he gets the credit he deserves.
He is very open to feedback and despite some criticism, has moved the fediverse forward in the best interest of the users and not some VC funded company.
It is in the best interest of the fediverse that we work together. #activitypub#fediverse