#federation

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

christophehenry (Christophe Henry)
christophehenry has 8 repositories available. Follow their code on GitHub.

Socialhome HQ

Dino in Debian experimental

What is Dino?

Dino is a modern IM client using XMPP (Jabber) with support for both OpenPGP and OMEMO. It looks very nice and can already be used for chatting and group conversations. It is, however, not yet stable nor feature-complete. If you are looking for something like Conversations (Android XMPP client), but for the desktop, Dino is for you. If you like to have something more stable and feature-complete, try Gajim instead. I use both! :~)

Dino

Dino is written in C and Vala, uses the GTK+ UI toolkit and looks best in Gnome, XFCE, or other GTK+ based desktops. I heard about planned versions for Windows and MacOS, too, but don't hold your breath.

How to install Dino on Debian?

Since yesterday, the Dino IM client is available in the official Debian repositories, but so far only in the "experimental" distribution. To install it, Debian users have to:

$ echo deb https://deb.debian.org/debian/ experimental main | sudo tee /etc/apt/sources.list.d/experimental.list
$ sudo apt update
$ sudo apt -t experimental install dino-im

This should work on nine official and five unofficial architectures for at least unstable and testing. Not sure about stable. I'm pretty sure, that oldstable will not work.

Why the "-im" suffix for Dino in Debian?

There used to be another program, an "integrated MIDI piano roll editor and sequencer engine", by the same name in Debian. Many references to the old program still exist, so it would be problematic to recycle the name for a different purpose.

Happy chatting!

#xmpp #debian #dino #jabber #openpgp #omemo #im #federation #chat

debacle@framasphere.org

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

Hello all,

Apologies to all diasp.cc pod users. Sidekiq had crashed and stopped sucking in all #Federation posts. Problem found, problem fixed and resource/config put in place to sidestep this sort of issue in the future.

diaspora* social network

podmin@diasp.cc

♲ ovigia@meld.de:

Social Cooling
What is Social Cooling?
#socialmedia #federation

[l]
<https: 04="" 2016="" 28="" new-study-shows-mass-surveillance-breeds-meekness-fear-and-self-censorship="" theintercept.com="">
<https: 03="" 2016="" 28="" mass-surveillance-silences-minority-opinions-according-to-study="" news="" the-switch="" wp="" www.washingtonpost.com="">
<http: corporate-surveillance="" crackedlabs.org="" en="">
https://motherboard.vice.com/en_us/article/mgbg7p/nsa-chilling-effect</http:></https:></https:>

Social Cooling
What is Social Cooling?»Social Cooling describes how big data is greatly increasing pressure to conform. Our data is turned into thousands of scores, which ...

Rikhard

Moving away from Twitter

Last Friday, I chose to honor the movement #WomenBoycottTwitter for a full day, not because I'm a woman, but because I've noticed browsing Twitter specifically puts me in a bad mood. This started a bout a year ago with the fateful election of Donald Trump to President of the United States of America and it slowly grew worse over time.

On the same platform, I blocked 3,920 accounts promoting tweets and muted 97 accounts I deemed uninteresting, numbers I would be hard pressed to match on the #Fediverse / #Federation. As long as I was otherwise enjoying the service I didn't mind too much, but now it just looks silly.

However, I have contacts I only have through Twitter, and I'm not ready to completely sever all my ties with them. As a temporary solution, I've enabled #Friendica's Twitter plugin to import my timeline from Twitter in my feed. It's going to increase the volume by about an order of magnitude, so I proceeded to weed out chatty contacts who only made sense on Twitter.

I still have an open account on Twitter, but at least I won't be using their clients, seeing their ads or being shown random offensive tweets on popular retweets. The only regret I have is about Private Messages that aren't compatible with Friendica's. I hope people I know will send me text messages instead but I know it won't happen unless I do it. It's an unfortunate side effect of leaving convenient platforms and I already have first-hand experience of this phenomenon after I was kicked from Facebook.

Thanks for reading!

Hypolite

We Distribute, Part I: The Road to Federation – We Distribute – Medium

#comms #federation #social

To understand what federation is and how it works, it’s important to first point out how it’s different from traditional networks. There are differences in opinion over how the idea itself should be implemented, but generally most people agree on what the idea is.

https://medium.com/we-distribute/we-distribute-part-i-the-road-to-federation-207b61daa38

We Distribute, Part I: The Road to Federation – We Distribute – Medium
In the beginning, there was Laconica, which later became known as StatusNet. A massive amount of the work that went into this is due to…

Rikhard

💡 An idea for #federation that I came across in #fediverse

TL;DR: autofollow bot to improve the view of the federation of every instance

Reading GNU Social's manual... "Hashtags are somewhat limited in GNU social because your server does not have a complete view of the network. Suppose your server has 10 accounts on it. It knows about every post that those 10 people make. If each person follows 10 different people on remote servers, that’s 100 extra people. Now your server knows about the posts from 110 accounts. If you click on a hashtag on your server, it’s only ever possible to see posts from those 110 people."

...makes it clear that all networks have same ~~problems~~ tricks. If a user registers at a small instance (or runs one), they face the issue of an empty stream, or "the ghost town" as some users call it, until they subscribe to many users on different pods. In #Mastodon they came up with autofollow bot, like this one - and here it is at work on one instance, autofollowing Mastodon, GNU Social accounts (and probably other fediverse compatible instances). These bots are doing a good job of making the timeline of smaller instances more interesting. They also help make the fediverse more connected. (They are also used by some who try to collect subscribers in a twitter-ish fashion, following, then unfollowing -- but eh, that's inevitable human nature I guess :)

I haven't come across such bot for #diaspora. So thought it might be useful.

gled-rs/mastodon-autofollow
mastodon-autofollow - Autofollow bot for mastodon

lightone

#The #Federation

In the US, these things [#Facebook, #Twitter, #Google] are becoming pure Orwellian Evil and those are things that I am interested in for sure.

I am still uncertain on The Federation as the end goal.

<br>

Things do not always federate smoothly (with dropped posts, mis-ordered timelines, pods coming and going) -- and I often wonder how many of the pods are plopped in by security #agencies anyway...

<br>

Plus the actual usage is quite low.

The Federation [#Hubzilla, #diaspora, #socialhome, etc] claims more than 650,000 or so users; but that is just "I signed up once" users.

Actual use across this whole mess was 16k users last month. In total.

(It is actually kind of embarrassing to claim 650,000+ users given that).

<br>

So ... for me ... the jury is out on The Federation.

<br>


[Other #diaspora #nits](/posts/4017fe20166f0135bd7e4986d5cbec7f)

<br>

the federation - a statistics hub
Podlist and statistics for The Federation (diaspora*, Friendica, Hubzilla).

prep

Prosody 0.10.0 now in Debian unstable

Users of Debian unstable can now apt install prosody prosody-modules to get the latest version. I run the packages (so far without issues) on a Debian stable system. The "clean" way would be to wait for a backport, but at the moment, it is not strictly necessary.

#debian #prosody #xmpp #federation

debacle@framasphere.org

Finally got myself a sane #logging setup. Previously I've been struggling to make any use of my file based logs, which has led to impossibility in debugging production problems in #Socialhome. Basically what I was doing was setting a few rotating log files and logging to them from all processes. What that means is that the log files just rotate so fast (due to many processes) that you don't really have time to catch problems.

While trying to keep things simple, I was losing a lot of valuable information. More users in the system means more unexpected stuff happening.

So now I've moved to sending all application logs from all processes via #rsyslog to an external service. Right now trying Loggly, which wasn't as easy to set up as they claimed, but is quite nice once done. Good filtering, easy to narrow down on interesting stuff. Great improvement, can squash those random #federation payload processing bugs now :)

Any good recommendations on logging services or good self-hosted logging aggregator apps to set up?

#sysadmin #selfhosted

Jason Robinson

Why does diaspora not accept announcements@project.hubzilla.org as a user to search for? Is there some equivalent way to get the information at https://project.hubzilla.org/channel/announcements via Diaspora?

#question #hubzilla #diaspora #federation

torpcoms@diasp.org

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

jaywink/socialhome
socialhome - A federated social home.

Socialhome HQ