#activitypub

Socialhome v0.6.0 released

.. and we have a logo!

The logo, which highlights both the "home" and the "grid" aspects of #Socialhome, is contributed by lightone - thanks a million! <3 The documentation brand page has an SVG and various PNG's for download.

Major changes

Other user facing changes in this release include the following:

  • Profile "All content" streams now include the shares the profile has done.
  • Unknown shared content shared by a contact is now fetched from remote if it doesn't exist locally.
  • Modified timestamp is now used for when federating out to remote nodes. This makes edits federate more reliably to some remote platforms that support edits.
  • Fixed various OpenGraph related issues.
  • Fixed poor performance of loading replies. This regression happened when introducing replies for shares.

Additionally there are some #API changes and various other tweaks mainly interesting for people who run or would like to customize a Socialhome server. See the full changelog.

For developers, #Docker files now exist to do development without installing all the complex components required. See the developing with Docker documentation.

Release statistics

A total of 7 authors contributed to this #release which is a record so far! #Hacktoberfest helped bring in a few authors. A total of 77 commits were made, affecting 134 files, contributing to 3864 insertions and 865 deletions.

Up next

Right now there is still a lot of work being done on the #VueJS streams, thanks to Christophe Henry again for working on these. Current estimate is that the next release will replace the current #jQuery based streams with the new rewritten ones. This will introduce some feature updates, but mostly it will be an internal rewrite. What it does do though is open up more features to be added. The current streams code is not going to be expanded expect to fix bugs.

Once the Vue streams work is shipped, we're looking to work on long standing missing features like tag streams and limited visibility content. #ActivityPub federation will likely be pushed to early months of 2018.

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.

Official site: https://socialhome.network.

Contribute

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.

#changelog #news #socialnetwork #thefederation #selfhosting

lightone

Socialhome HQ

https://twitter.com/dustyweb/status/926097230389538816

#activitypub #federation


Jason Robinson

Found good use for the new Diaspora URI scheme. For the federation library I need some kind of global identifier when #ActivityPub support is added. A GUID doesn't work since it doesn't define have a location. I was already writing code for <guid>@<domain.tld> format when I saw the Diaspora URI scheme - which fits this usage perfectly 👍 This gives each entity a globally unique URI ID, regardless of protocol.

#devdiary #federation #diaspora

jaywink/federation
Python library for abstracting social federation protocols

Jason Robinson

Enabled #ActivityPub on my Hubzilla server today. Curious as to what I can currently do with it.

Sean Tilley

Socialhome version 0.5.0 released

Approximately one month since the previous release, #Socialhome 0.5.0 is out with 102 changed files, 2870 insertions and 999 deletions by 2 contributors.

For users there are only a few features added in this release, most of the work being internal refactoring and work in preparation for future features.

Please see the full changelog here.

New features

A few notes on feature highlights.

Shares in streams

Shares are now pulled up to the "Followed" stream. What this basically means is that when a person you follow shares something authored by a person you don't follow, the post will be pulled up in your stream by the share action.

Generally, you should only see a single post once. If you follow the author whose content was shared, that content has already been in your stream, and thus a share will not repeat it. Note however that since stream pre-calculation is a new thing, it is possible that content seen in the stream before this feature was added will pop up in a new share once more.

There are still some things to do for shares, these are being tracked in this issue.

Stream precaching

Related to "shares in streams", there was a lot of refactoring work to create the new base for how all streams function. This includes unifying lots of code and rewriting it so that in addition to pulling content out of the database, we can "precalculate" streams. This is done to ensure streams load super fast even if the calculations on what content the stream has are heavy.

The only stream that is currently precached is the "Followed" stream. Precaching means it will load as fast as the public stream even though we now include shares by non-followed users and include them only once - which would be a heavy calculation to do without precaching. The real benefit will come when custom user defined streams are available.

How would you like to configure the content in your stream?

GIF uploads

Yes, we love GIF's <3

Links in content

All links in content (whether textual, markdown or HTML) are now treated equally. They will all be used as candidates for OEmbed/OpenGraph fetches and all will be processed to add a target="_blank" to the link, forcing it to open in another tab/window.

Stream URL changes

All stream urls now live under /streams/, so for example followed stream is /streams/followed/. The old url's should still work until they are needed for something else.

Features coming up

Vue.js streams

Christophe Henry has been hard at work rewriting the current Django template + #jQuery based streams in #VueJS. The status of that work can be tracked here. We're hoping to replace the current stream frontend with the Vue streams within the coming months. This will drop a lot of legacy code and speed up development of new features, and will also mean our #API is fully complete for the stream features.

ActivityPub protocol support

This is still something we want to do as soon as some of the basic features are first implemented. Currently it looks like having it before the end of the year is slightly optimistic, but federating with for example #Mastodon using #ActivityPub will be a strong priority to get early next year.

Docker images

There has been some work on #Docker images to run a Socialhome instance. Will post more info as they are ready.

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.

Official site: https://socialhome.network.

Contribute

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.

#changelog #news #socialnetwork #thefederation #selfhosting

Rewrite streams in Vue.js · Issue #202 · jaywink/socialhome
See high level description at http://socialhome.readthedocs.io/en/latest/roadmap.html#vue-js-app-s Streams currently implemented features below which need to be replicated on the Vue.js side. Tick ...

Socialhome HQ

#Mastodon launches their #ActivityPub support, and a new CR! -- ActivityPub Rocks!

https://activitypub.rocks/news/mastodon-ap-and-new-cr.html

#federation

Jason Robinson

♲ Gargron@mastodon.social:

Mastodon v1.6 is live!

☑️ Easier sharing & discovering content across servers
☑️ Improved first-time user experience
☑️ Fresh new W3C standard #ActivityPub
☑️ Better profiles & pinned toots
Mastodon and the W3C – Eugen Rochko – Medium

[l]

Mastodon and the W3C – Eugen Rochko – Medium
The Pub is Now Open, ActivityPub that is!

Steffen K9

https://twitter.com/dustyweb/status/900090268891975680

#activitypub #federation


Jason Robinson

Really nice to see also #Red/#Hubzilla side getting an #ActivityPub plugin. Many of the important players are actively working on an implementation or at least participating in discussion. Where is #Diaspora? :P

Hopefully the biggest issues will be ironed out soon, like whether to have signatures or use other delivery verification methods. This is the most important thing not yet decided imho, but there is strong pressure to do so due to implementers wanting it defined. I wish this discussion had been done earlier, but I guess not enough of the right people were participating.

https://macgirvin.com/channel/mike/?f=&mid=fa0d8d0d529d2be81878d3f3928b049739fd496c59f1091e951bfa8bd0362218@macgirvin.com

#thefederation #fediverse

Jason Robinson