Hubzilla on wikipedia

As it is apparently hard to create a new page on wikipedia, here is the draft version of hubzilla page. A draft could be deleted and as this page is not bad and could be copy just in case.

https://en.wikipedia.org/wiki/Draft:Hubzilla

Hubzilla (formerly known as Redmatrix) is a community management platform that is designed to mesh with other instances running the same software. It is considered a platform for federated networking, and is compatible with both Diaspora and Friendica. Hubzilla is notable for combining aspects of social networking, blogging, forums, cloud storage and content management all into one application.

Hubzilla
Original author(s) Mike Macgirvin
Developer(s) Hubzilla community
Stable release 1.3. / March 2016
Written in PHP
Operating system Cross-platform
Platform Apache, Nginx
Type community management platform
License MIT License
Website [1]

 

Development History

In 2012, Mike Macgirvin of the Friendica project stepped down[1], and formed an experimental communication platform named Friendica Red. This system existed for exploratory purposes, and was designed based on lessons learned from developing Friendica.

Much of the design concepts for the new platform would be based on ideas about user identity management and privacy permissions. It leverages a unique federation protocol named Zot, which acts as the design successor to Friendica’s DFRN protocol.

As time went on, Friendica Red was rebranded RedMatrix, before the name Hubzilla was decided on. On December 24th, 2015, Hubzilla 1.0 was officially launched[2].

Features

Hubzilla can be defined as a decentralized communication and publishing platform. Any server running Hubzilla is defined as a hub, which can function independently of any other hub in the network.

Channels

Channels are a core concept for the platform – in short, each channel is an activity stream of objects that can represent a specific action, such as a posting a status or uploading a photo. This stream can show both public and private activities, and an ACL permissions system determines which users can access a given entry. Each channel also contains a unique Webfinger address, for example https://example.com/channel/bob would be represented as bob@example.com

A Channel can be created for the following use-cases:

  • A Social Stream
  • Blogging
  • Branded Product Streams
  • Group Forums

A user is assigned their first channel upon registration, but they can create as many different channels as their hub allows. Each channel in turn can connect to another channel as a contact. This mechanism will allow a user to interact with posts, as well as post on the wall of other channels as themselves. Private messages and statuses can also be passed back-and-forth from one connected channel to another.

MagicAuth

MagicAuth is a type of in-browser encryption that grants access permissions on remote hubs. In a sense, it is a workaround to a long-standing problem in federated social networks: ordinarily, users couldn’t visit each other’s profiles and directly interact with them if both people are connected through different servers. MagicAuth exists as a means of granting access permissions to visiting users. The use-case works like so:

  1. Bob’s channel is on https://example.com/channel/bob, with the channel address of bob@example.com
  2. Bob visits Alice’s channel at https://othersite.com/channel/alice, ie, alice@othersite.com
  3. When Bob visits, his browser session performs a cryptographic handshake with Alice’s channel
  4. Bob is allowed to comment and like posts on Alice’s channel while he is visiting.
  5. Bob will also see private posts meant for him when visiting.
  6. If Alice allows people to make posts on her wall, Bob will be able to do that as well.

Cloud Storage

By default, each channel is given DAV access for file storage. This storage includes uploaded photo albums, and can allow for videos and other documents. Cloud storage can be accessed through a DAV client, and in some instances be integrated into the desktop file manager itself.

Web Pages

Channels are allowed to create web pages based on a templating system.

Directories

Themes and Layouts

Plugins

OpenID

Hubzilla can also function as an OpenID provider, allowing users to log into OpenID-enabled sites with their Hubzilla channels.

See also

References

 

 

  1. Macgirvin, Mike. « Hubzilla (1.0) release ».

External links

How to install Diaspora on Debian

Installing Diaspora / postgress

Just type this command

apt-get install diaspora-installer

Installing Diaspora / mysql

apt-get install diaspora-installer-mysql

 

Have fun

redmatrix

The RedMatrix (aka « red ») is an open source webapp providing a complete decentralised publishing, sharing, and communications system. It combines communications (private messaging, chat and social networking), and media management (photos, events, files, web pages, shareable apps) with enough features to make your head spin.

 

What makes the RedMatrix unique is what we call « magic authentication » – which is based on our groundbreaking work in decentralised identity services. This ties all RedMatrix sites and channels together into a single super-network where the boundaries between different websites are blurred or seemingly non-existent; where « who you are » has nothing to do with « what computer you’re connected to », and where website content can adapt itself according to who is viewing it.

 

Warning: After experiencing magic authentication and nomadic identity, you may find it disconcerting and a bit « primitive » to go back to the old internet. You shouldn’t need hundreds of different passwords to use the web … or be totally isolated from your friends and family because a server or router in another country is having « issues« .

 

For the average person, the biggest advantage of decentralised identity is that you decide who you want to share your stuff with, and if somebody isn’t on your list, they’re not going to see it. It’s all under your control (we’re big on privacy). Use the RedMatrix as a social network or a business website or for personal cloud storage or media publishing – or any number of other uses; limited only by your imagination.

why it is not easy for decentralized social networks

A New Kid on the Block

Conditions for a Successful Market Entry of Decentralized Social Networks

 

diaspora, hubzilla, gnusocial

EdgeRank and Content Filtering

Facebook has gotten a lot of press recently over its "EdgeRank" feature. This is basically a filter that sits between you and your friends. Facebook decides what to allow through the filter so that you can see it.  Current estimates are that you only see about 15% of the posts made by your friends. How and why they do this are interesting topics. It seems mostly to be a way to get advertisers to pay more money to get in your face. There's also a claim that seeing all posts and activities would quickly get tedious and therefore you should only be able to see stuff that's "interesting". Since Facebook knows you so well, they're evidently able to decide without a doubt what you'll find "interesting". They don't need to ask you. 

Regardless, wasn't the point of "social networking" so that you could communicate with your friends? A service which claims to provide this, yet somewhat arbitrarily blocks communication between you and your friends would seem to be an anachronism. It kind of takes the "social" out of "social networking" if you're just sending your posts into space and all your friends are prevented from seeing them.

In a world where you have lots of incoming information streams from lots of different sources, you really do need a way to "cut to the chase" and quickly locate information of relevance. This could be in the form of search tools and the ability to view specific streams from your catalogue - rather than the entire firehose.

Here on the free web, the concept of a communications service deciding what communications to allow is an alien and very strange concept.  We think this should be in your hands, under your control. Actually we think that all your online activities should be under your control - so you don't appear in one of your friends' pages pitching vacation packages and toiletries without your knowledge. 

Friendica lets you decide what and how much to see. We've got lots of different "search modes" on your stream to slice and dice the firehose any way you desire. Our next generation project ("Red") adds an entirely new dimension to this - allowing you to "zoom in and zoom out" from your close friends to your most distant acquaintances dynamically.

Is the free web a good match for you? I can't say. You could ask your friends, but chances are they won't ever see the question.

 

Until next time, this is Commander Zot - saying over and out.

 

An introduction to the protocol that powers Hubzilla

The world is full of protocols. Some are loosely defined by society, and some are rigidly defined by their architects. In many urban environments, for example, there is a protocol for how you ride an escalator: if you choose to stand, you stand on the right side so that those who choose to step can get past on the left. If you ignore this protocol, you may get some annoyed looks but you will still get where you are going. More rigid protocols, such as the hypertext transfer protocol (HTTP) that governs most communication on the web, can be much stricter and more elaborate. If your browser puts one semicolon in the wrong place you can forget about seeing those cute cat videos.

 

Read more

Riot.im

Riot is a place to chat. But it brings much more than just a chat room. You can chat with one to one or add people or  join chat room or create chat room.

All is federated and you have a name like user:server.com So you can add people from other servers. The first server is matrix.org.

Additionaly you can share files, images and make audio or video calls. And you can add widget like etherpads for example

This alternative can easily be used like watsapp or such centralised app. You have to know that watsapp belong to facebook and all is heard by NSA or other surveillance services.

If you are not convinced, all is very secure decentralised and encrypted end-to-end. And of course this is opensource. Try it on riot.im/app/

 

You can use application on your smart phone too of course.

If you want to try go to riot.im

 Interview of Jason Robinson of Socialhome

Sean Tilley wrote an interwiew of Jason Robinson about Socialhome.

Read the article on medium.com

He created the project the-federation.info  that makes statistics with Diaspora, Friendica, Hubzilla and Socialhome and others social networks. The idea was to offer a few words about each project and provide links to their project pages, in addition to showing some numbers.

 

From the start the idea was to create a library that abstracts multiple protocols under a common API. Not quite there yet, but now that ActivityPub is mature, the plan is to add support for that within the early months of 2018. The library will never be a one-to-one mapping to Diaspora or ActivityPub, but rather an opinionated API for both.

With Socialhome I’ve tried to take the best features of all the platforms I’ve used and merge them together into my own dream platform. It has a (up to) 4 column grid layout like Pinterest, which supports visually rich content and reading through lots of content fast. It supports lengthy Markdown (and HTML/JS/CSS for trusted users) formatted blog post like content, but also works totally fine for micro-blogging. One of the key features that will be added will be highly customizable streams like for example Tweetdeck has for Twitter. I also want to enhance the blogging features for things like anonymous comments, allow full text searching and other neat tools not available in many existing platforms.

Thanks for joining us today, Jason! Could you take a moment to describe yourself, and what it is you do?

 

You started out in the space as a contributor to the Diaspora project. What kind of contributions did you make?

 

 

You run the-federation.info — could you tell us a little bit about that project and how it got started?

 

 

How did the social relay solution come about for Diaspora? What problem does it solve?

 

 

You’ve been working on a federation library in Python for almost two years now. Why Python?

 

 

What inspired you to start Socialhome? How is it different from Diaspora?

 

 

What kind of things are on your development roadmap?

 

 

What is the most challenging thing that you have worked on so far?

 

Do you have any advice for people in this space that might want to start their own project?

Don’t be afraid to start. Your project doesn’t have to be successful, or even something you end up using yourself. Start hacking, work on things you want and always ensure to have fun. Don’t listen to other people telling you what is good and how you should do something. Experimenting is key to learning.

 

Read the article on medium.com

In memory of Anthony Baldwin a.k.a. Tazman

Hubzilla 3.0

This release is dedicated to the memory of Tony Baldwin a.k.a. Tazman, a Friendica/Redmatrix/Hubzilla enthusiast and contributor, who passed away last week.


Before pointing out the notable changes in the 3.0 release, here is a summary of what we accomplished during the version 2 release cycle (2017). We released 4 shiny Hubzilla versions with about 3101 commits from 21 contributors. The main focus was on:

  • CalDAV/CardDAV integration
    In Q1 2017, we made a strong effort to merge CalDAV and CardDAV into Hubzilla as a native interface. This would allow easy federation with events and contacts amongst hundreds/thousands of existing utilities. Significant progress was made (and this led to several new features) but the effort stalled around March. We were not (at the time) able to resolve serious incompatibilities with nomadic identity, access control, server-to-server authentication, and rich-text support. Significant progress was made in all of these areas over the remaining course of the year however, and this integration effort is expected to resume in early 2018.
  • Consolidation of server roles
    Server roles were removed/merged early in the year. These were initially provided to solve incompatibilities between nomadic identity and external network federation (such as Diaspora, GNU-Social, and later Mastodon). The incompatibilities still exist. It was decided that network federation should be available to anybody who wants it; and they can decide how important channel backup and live mirroring is to them personally. If a hub administrator wishes to make that decision at a site level, they can do so by not installing the external network addons.
  • Communication protocols
    Once a resolution was reached regarding Server Roles, work proceeded in earnest upgrading and extending the external network protocol addons (Diaspora, OStatus, and later the emergent ActivityPub protocol). Each of these underwent huge development efforts. The Diaspora protocol was completely upgraded to the « new protocol ». Ostatus was extended to provide better compatibility with Mastodon and « conversation fetching » added to solve known issues with the OStatus delivery model. We had one of (if not) the first available working implementations of the ActivityPub protocol some time in June or July. It wasn’t officially released until Q3 2017, which was a couple of months after the first official Mastodon ActivityPub release.
    Our primary protocol (zot) has been in use for over five years. While still being well suited to its task, is starting to show signs of age. In 2016 it underwent a number of crypto improvements to help ‘future-proof’ it. Work began on Zot/6 in Q3 2017 to bring it up to the present state of the art. This work is ongoing and the full benefits won’t be seen until Q2 2018 (projected), but pieces of the new protocol are already in place and improving things right now. The first major piece was OpenWebAuth, which builds on HTTPSignatures to provide a streamlined and standards-based cross-domain authentication layer.
  • Theme and UI
    Project navigation and the notification system were the primary focus of UI/UX development. Navigation and the pre-existing ‘Apps’ feature were first integrated and then extended. Then the notification system was moved from the top ‘navbar’ to a dedicated page widget in the base theme, integrating it more closely with the content.
  • Media/Files
    Cloud storage and media management underwent signficant development, climaxing in Q4 2017. One of the first components of this work was to provide uploads of « unlimited » size across all the existing tools; instead
    of only through WebDAV. Processing of photos was also reworked to handle the larger images from state of the art digital cameras; which were causing memory issues in the original architecture. Finally a ’tile view’ was added to the cloud/file web viewer providing a more modern looking page.
  • Core
    Documenting all of the previous work and efforts required improvements in the Wiki and Webpage content features, and ‘Cards’ were added to provide interactive development documentation. We also provided the ability to create third-party Widgets and share them just like addons and themes, extending earlier work in this area. The project has been updated to work seamlessly with PHP7.2 and recent version of MySQL and Postgres. Many libraries have been moved to ‘composer’ (the PHP package manager) and the unit test system enhanced in a number of ways. Documentation has been improved dramatically (although this is a continued effort).

During the course of all of this development work, we’ve continued to listen to suggestions and issues which have been encountered by members, and have cleaned up and fixed many other areas that were lacking.

Notable changes in Hubzilla 3.0

  • The remote home link (the « Take me home » menu button in your personal menu on other websites of the hubzilla network) now does not bring you to channel home anymore but only to the domain root. This will bring you to the Activity app by default if you are logged in or to the login page if you are not logged in at your home hub anymore.
  • The techlevel for new accounts will be raised from 0 to 1 automatically after some active participation (connecting to other channels, creating posts, etc.).
  • We implemented chunked uploads for the photos and cloud modules in addition to wall uploads where we had this feature quite a while already.
  • A filter for notification to show new posts only has been added
  • Live updates and notifications updates have been reworked. We now first do the live update and then update the notifications.
  • We now have a system config option for minimum registration age
  • We implemented a tile view for the cloud module and added thumbnail generators for the most popular file types
  • A new experimental startpage module (hq) has been introduced. This provides a simple page with the latest toplevel post, notifications and the possibility to create a new post. You can make this your default startpage via the startpage addon.
  • We now provide the ability to pin apps to the navbar
  • Private forums have been added to the forum widget
  • We added another delivery control parameter (queue threshold) for sites which had issues with too many immediate deliveries at the same time. This parameter defaults to 300 which is quite conservative. Admins should adjust this setting according to what their hardware can handle.
  • Hubzilla is now ready for PHP 7.2
  • The js_upload addon has been removed. We now handle multiple file uploads natively.
  • We removed the Firefox social plugin – it was deprecated and removed in Firefox version 57

Hubzilla 3 release cycle preview

  • Continued integration of CalDAV/CardDAV
  • Continued implementation of Zot/6
  • E-Commerce solution

 

 

Source Hubzilla support forum

A Basic Introduction to GNU social and Mastodon Social

The future of the Federated social network

What is the today’s situation ?

At present, there are two supernetworks in the federated social communication space, and they run on different protocols. They are known as The Fediverse, and The Federation. Le’t look at a shema. A picture is often much more understandable that lot of words.

 

 

 

You have in one side Diaspora with diaspora protocol and Gnusocial with Ostatus protocol.  Mastodon who use Ostatus protocole can talk with Gnusocial user.

What is the Fediverse?

The Fediverse has historically operated as a microblogging network, and uses the OStatus protocol for servers to communicate with one another. In all, it pulls together six different platforms: GNU Social, postActiv, Pleroma, Mastodon, Friendica, and Hubzilla. StatusNet was eventually pivoted into the GNU Social project, where development has continued at a steady pace. It has been forked into the postActiv project, which aims to clean up the system’s backend and user interface. Mastodon was initially developed as a Ruby on Rails-based OStatus implementation, and can also connect to these other networks. Finally, the Pleroma project started as an alternative frontend for GNU Social, but now has its own backend written in Elixir

 

What is The Federation?

The Federation is an interop network consisting of 278 different connected servers that communicate using the Diaspora federation protocol. This is a different communication standard from OStatus, and allows four distinct platforms to all communicate with one another: Diaspora, Friendica, Hubzilla, and Socialhome.

What is the future ?

.At the moment, several projects in the space are working to adopt new supplementary protocols ActivityPib, with the intent of building better bridges between one another.

We can see on this diagram that Friendica, Hubzilla and PostActiv has an advantage aver other application.

Read more in medium.com

 

Do you own your data

I don’t have any need or desire to use Facebook or Twitter. I don’t need Nextcloud or MediaGoblin or Drupal or Diaspora or GNU-Social or Mastodon or WordPress. I’ve got all of the features from those applications that I want – right now, without needing those applications. I’ve got as much privacy as I want or need – up to top secret messages between top secret friends if I need that level of privacy. I can share photos from my photo albums and videos from my library with selected friends and *only* those selected friends. I’ve got 16 years of my online life literally in my pocket. Everything I need to keep from my online life over those years. I can spin it up on any server in the world at any time and have all my friends and all my content intact if the datacenter serving my stuff gets hit by a nuclear warhead. I can spin it up right now and keep it all synced between servers as I add new content – and switch to another server at any time; for just a few minutes or a few years. My server is my social network, even though I’m the only person with an account on it. My friends have their own servers and these all work together. It’s my personal cloud and my file sharing app. If I allow you to see my videos you can see them. If I don’t – you can’t and there’s nothing you can do about it. You don’t need a password on my machine to do this. You just be yourself and do your own thing, and if you can see them you’ll see them. I don’t see targeted ads. My dead friends don’t recommend products for me to buy (this actually happened to me once on Facebook). I don’t get spam from Twitter begging me to login and let them analyse me.

This is what we mean by « own your data ».

 

Mike Macgirvin wrote this thinking at Hubzilla

What is a nomadic identity

Nomadic identity is not easy to understand. This is a new concept.. Hubzilla is a decentralisated community publication plateform that use nomadic identity. Mike Macgirvin explain with a simple example what is nomadic identitiy

 

 

I’ve had to answer a lot of questions about nomadic identity recently. It’s not that hard. Let me try and bring it to an easier conceptual level.

For our example we’ll start with email since it’s a concept many people sort of understand.

You’ve got a friend named Bob. Bob has two email accounts. He has a home account at bob@home.server, and he has a work account at bob@work.server . Now most people instinctively know that if they get an email from either address, that they’ve received an email from Bob. They usually don’t even think about what server he is using.

Nomadic identity just means that when we send an email, we will send to both of Bob’s addresses any time we send an email to Bob. This way he’ll get the message no matter if he’s at home or if he’s at work.

Simple enough? Good, let’s continue.

Now let’s take this into the decentralised social networking space such as provided by Hubzilla. What’s different? The only thing is that if Bob posts a picture while he’s at work, his work server send a copy to his home server so he’ll have the same picture in his photo albums in both places. If he makes a new friend, the friend will be added on both servers so he has the same friends no matter where he goes.

Now if Bob loses his job and his account gets removed from work.server, Bob’s onlife life still goes on and he still knows the same people and still can post the same things. He’ll just use home.server; and then when he gets a new job, he can send you stuff from bob@newjob.server. Your software will instantly notice – « hey, this is my friend Bob! » even if it has never heard of newjob.server before and update some stuff internally to indicate that Bob can now be reached at newjob.server.

None of this matters to you, because as far as your software is concerned, it’s just ‘Bob’. You don’t care what server he uses or what job he has this week.

That’s what nomadic identity is all about..

Hubzilla 2.0

For Christmas a new version of Hubzilla is out.  One year after version 1, this version has now better database capability, a wiki that works well, a new twitter API and lots of User Interface bahaviour improved. Hubzilla with the nomadic identity is really a software that goes where anyone has gone.

Here is a somary writen by Mike the founder of Hubzilla

 

The database driver has now been converted to PDO, which was the last remaining work to be done to bring the project up to what we call an « enterprise grade » architecture and began exactly a year ago. In the process of doing this work, we fixed a lot of compatibility issues with postgres – which should now work reasonably well.

The wiki and help pages (project documentation) had a number of usability issues and all of the known issues have been addressed. Wiki pages can now be created in bbcode, which is much more expressive in its ability than markdown.

The API was redesigned and many of the base functions are now documented. The Twitter API was moved to a plugin so you can still use Hubzilla with hundreds of third-party apps and social clients.

The ‘hl’ (highlight) tag was added to our reportoire by request.

Lots of UI behaviour changes to streamline the flow and ease repetitive tasks. Too many to list individually. The « left side » menu was also made ‘sticky’ to ease navigation on lengthy and infinite content pages.

Zot, the base protocol was extended to allow negotiable encryption algorithms; allowing sites to create their own encryption stacks and harden their communications against state-sponsored actors.

Edited posts and comments will now appear on Diaspora (which does not support editing of posts and comments).  There were several other fixes for Diaspora protocol and communications issues.

Superblock was re-written entirely and it is now much easier to remove blocked channels from the blacklist. It is also much harder for their posts to appear in your stream anywhere, and they can never write on your wall; even if you have relaxed comment permissions.

In addition we fixed hundreds of bugs and fixed a lot of « little stuff » that nobody complained about, but we felt should be improved to make this a world-class app.

Since 1.0 – the entire project has been re-written and completely re-architected to provide an enterprise-grade software base going forward. All corporate and external dependencies have been moved to plugins. Most anything that was limited « by design » was reworked and the limitations removed; for example the permissions infrasrtucture. Along the way we introduced new functionality in most areas of the platform and continued re-working the UI to make it more consistent and usable. The project also supports three base modes (but this could be extended) to provide functionality tuned to different uses such as for federation or enterprise use. The list of individual changes since 1.0 is quite staggering. I haven’t done a count but I believe it probably represents around a half a million lines of code changed; possibly much more than that. The total amount of work is quite impressive given the small team and numerous distractions we faced from critics and trolls along the way.

Articles plus anciens «

» Articles plus récents