Pour rappel Hubzilla est une plate‐forme décentralisée de partage de contenu et de réseau social. Elle offre des facilités d’utilisation et d’identification et un socle très robuste pour des fonctions de réseau social (interopérable avec Diaspora, GNU-Social, Mastodon et gérant le chiffrement de bout en bout), de partage de fichiers et de photos (accessibles en WebDAV, à la Nextcloud / Owncloud), d’agenda et de serveur de calendrier CDAV, de carnet d’adresses et de serveur de contacts CardDAV et de wiki. De nombreuses extensions sont disponibles, du jeu d’échecs au partage de fichiers pair à pair via Webtorrent…
@kris Make that #ActivityPub. #ActivityPump was the original name for #Pump.io, back when EvanP was first trying to develop a lower-resource-use federated social server. (There was never an explanation for the name change, either. I always thought AP was a better name.)
Avant de parler du futur il est important de bien décrire la situation actuelle de 2017. Aujourd'hui nous avons deux grands super réseaux. D'un coté nous avons un réseau de réseaux qu'on qui est la fédération et qui se repose sur le protocole de Diaspora. D'un autre nous avons un deuxième super réseaux le Fédiverse qui est basé sur Ostatus le protocole de Statusnet qui est le Père de Gnusocial. #federation #fedivers #activitypub
Something that separates identity, message distribution, and message content. An earlier criticism of #ActivityPub by @mike was quite reasonable. The one in this thread suggests he has a drinking problem.
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.
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.
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.
I filed a bug for #ActivityPub, which is exactly about Person's freedom to choose (and actually, change) an instance/server of a global social network without loosing his/her identity, including historical data. Moving from one instance of a federation to another is a normal case, just like having user accounts at several servers. And #ActivityPub specification should explicitly allow this. See https://github.com/w3c/activitypub/issues/260 @fuzboleroxv @citizenphnix @cwebber @gargron @deadsuperhero @mmn @lnxw48a1
Interesante charla de Alex Jordan (mantenedor principal de #pumpio) en el pasado #LibrePlanet sobre los nuevos estándares (concretamente #ActivityPub, sobre el cual creo que interviene también el propio @cwebber desde el público) que están surgiendo para aunar e interconectar todo el contenido producido socialmente en las redes libres federadas. No solo las de formato típico que usamos para publicar notas (#Diaspora, #Mastodon, #GNUsocial, etc.), sino también para otros servicios paralelos como #MediaGoblin, para el que, según dice, ya se ha desarrollado un prototipo que permite a los usuarios comentar (o suscribirse a) contenidos de otras instancias, con lo cual mejoraría muchísimo el servicio...
so basically we have to wait for #mastodev to dictate to the rest of the #federation what the new federated groups implementation is going to look like
Hi, I'm @mmn, maintainer of GNUsocial. I reacted when it was written that "many people on gnusocial are angry" and wish to say that !GNUsocial has only love and appreciation for #Mastodon and #ActivityPub.
I believe cooperation is important for libre software and the federated social web. I believe our plural and diverse community should embrace and encourage contributors and development. Any progress we want to make - regardless of anyone's preferred technology - is impeded by hostility and empowered by friendship.
So I want to say thank @cwebber @gargron et al. for all the hard work you actively put into ActivityPub. It's awesome that so many users get in touch with !fs via open protocols.
@usbhump Evan P's Status\.Net startup lost its funding. Around the same time, he was trying to get the developers of the underlying protocols that compose #OStatus to agree to make changes to their protocols to enable enhanced privacy. Among the organizations he was trying to motivate was Google, which had recently introduced #GPlus and was no long interested in the open web.
In a hurry to cut costs, he developed the #Pump.io software and protocol to be simpler to develop and cheaper to operate, and to offer some additional privacy built into the protocol. And also to be independent of the progress some of these protocols.
Pump was built with the idea that most federated networks would switch protocols to be compatible. That did not happen. But the hope is that its descendant #ActivityPub will unite the disparate networks.
@gargron Don't oversell AP. If you start to sound like a used car salesperson, people will become suspicious of your motives and the veracity of your claims.