Hubzilla 1.1

One month after the version 1.0 a new version comes today.

The bigest change is situated in the administration panel that is improved.

here is the announcement of Mike
Greetings and Happy New Year. The Hubzilla developers are pleased to announce the immediate release of Hubzilla 1.1, our decentralised community platform specialising in cross-domain identity and privacy

Changelog:

Hubzilla 1.1

Rewrote and simplified the Queue manager and delivery system
Rewrote and simplified the outer layers of the Zot protocol
Use a standard version numbering scheme in addition to the snapshot tags
Provide a channel blacklist for blocking channels with abusive or illegal content at the hub level
Make the black/white lists pluggable
Update template library
Support for letsencrypt certs in various places
Cleanup of login and register pages
Better error responses for permission denied on channel file repositories
Disabled the public stream by default for new installs (can be enabled if desired)
Cleanup of API authentication and rework the old OAuth1 stuff
Add API « status with media » support compatible with Twitter and conflicting method for GNU-social
Rework photo ActivityStreams objects to align better with ActivityStreams producers/consumers
Several minor API fixes to work better with AndStatus client
Invitation only site – experimental support added, needs more work
Fix delivery loop condition due to corrupted data which resulted in recursive upstream delivery
Provide more support for external (git) widget collections.
Extend the Queue API to 3rd-party network addons which have experienced downtime recently.
Regression: Inherited permissions were not explicitly set
Regression: « Xyz posted on your wall » notification sent when creating webpages at another channel
Regression: Custom permissions not pre-populated on channel creation with named role.
Provide « Public » string when a post can be made public, instead of « visible to default audience »
Allow hub admin to specify a default role type for the first channel created, reducing complexity
Ability for a hub admin to set feature defaults and lock them, reducing complexity
Change default expiration of delivery reports to 10 days to accomodate sites with reduced
resources

Addons/Plugins:
Pageheader addon ported from Friendica
Hubwall (allow admin to send email to all accounts on this hub) created
GNU-social – queueing added
Diaspora – fixes for various failures to update profile photos, updates to queue API
Cross Domain Authenticated Chess (Andrew Manning’s repository)

And… the normal « lots of bugs fixed, translations updated, and documentation improved »

more information …

How to federate hubzilla and gnusocial

Prerequisite : You should have an account on a hub that allow gnusocial protocol. For that the admin has to activiate the PubsubHubBub protocol and then activate the gnusocial protocol

If it is done you have to activate the activate the gnusocial protocol

settings > Feature/addon Settings > GNU-Social Protocol Settings (Just activate it)

Now it is ready for communication with gnusocial. Go to your connexion list and add the gnusocial.

 

 

Your gnusocial contact should add your Zot Id as well,

Tell me if it works for you or not.  The federation is on the GO

 

Création d’un compte totalement ou partiellement caché

Si vous avez un compte friendica, peut être voulez vous rendre publique certaines notices et pas d’autres. Vous pourriez par exemple écrire des notices publiques comme si vous écriviez sur votre blog (Friendica sera alors votre blog) mais, vous pourriez en plus écrire des notices privés visible seulement à un groupe (votre famille, vos amis proches etc…) ou seulement à une seule personne.

Voici la marche à suivre pour que tout ceci fonctionne bien:
Allez dans réglages (la petite roue) > Réglages > Compte

Vous arrivez par défaut de toute façon sur cette page.

La première partie Compte ne concerne qu’un changement de mot de passe, vous avez ensuite Réglages basiques puis Réglages de sécurités et vie privée. c’est cette partie qui va nous intéressé.

Cacher les détails du profil aux visiteurs inconnus? : Il faut répondre NON

La compréhension de cette traduction n’est pas facile à comprendre. Si vous répondez OUI, votre profile sera visible uniquement aux personnes connectés. Il faudra donc répondre NON pour que ce que vous voulez publier publiquement soit visible à tous les visiteurs.

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.

So what does that have to do with Hubzilla? And for that matter, what is Hubzilla anyway? Hubzilla is free and open source software designed to support your freedom and privacy; anyone can run it on their own server and inspect the code to learn how it works. It is an advanced platform for online communications and content publishing that provides decentralized access control. That last bit is the critical difference between Hubzilla and all the other blogging platforms, social networking sites, and messaging systems that dominate the web today, and it is precisely the motivation for inventing Zot instead of choosing from the plethora of existing communication protocols. To appreciate what is so innovative about Zot, we need to explain first what « access control » means and then why « decentralized » makes the problem of access control challenging.

Like protocols, the world has no shortage of access control. Does your house have locks on the doors? Do you let everyone watch you take a shower, or do you prefer to control access to that activity? How about conversations about your finances? I bet you publish those on billboards, right? Of course not! We all constantly control access to things for many reasons.

And sometimes you want to have a private conversation with someone that no one else should read.

Electronic publications and communications are no different. You may want to publish an article like this one for the whole world to read, but you may also want to participate in a restricted access forum online where members of your neighborhood can discuss community issues. And sometimes you want to have a private conversation with someone that no one else should read.

The traditional centralized solutions to these problems have existed for many years and are what virtually everyone currently uses online. This is because it is relatively easy to manage access control when you have one central authority acting as the gatekeeper to content. Facebook is the most influential example of this model. If you send a message to a select group of friends, only they have access to it because Facebook (1) authenticates them by identifying who they are based on their knowledge of their secret account password and (2) authorizes them to access the message by verifying that they are on the message’s access control list (ACL), which is the technical term for what you created when you « sent » them the message.

There are several fundamental and serious problems with this centralized model. Arguably the biggest problem is that you do not own your identity. But that’s absurd, you might immediately retort, of course I own my identity! Well, let’s consider what ownership means. Ownership of identity means, for one thing, control. If you own your identity, you control it somehow. With Facebook and similar centralized services, they alone have the power to create and delete your online identity. They grant you access to your identity when you log in. As the years roll by and you share all sorts of content with all the people you have connected with, you may be alarmed to discovered that you need the centralized service. If you want to leave, all of that shared content and all those connections vaporize. What’s worse, you can’t even share something privately with people unless they also allow their identities to become hostage to the platform. It’s like some kind of pyramid scheme.

They grant you access to your identity when you log in.

Now we can begin to appreciate some of the benefits of decentralization in our online communications. When you register an account on a “hub” — a server running Hubzilla — you can make connections with other people and share things even when they are on completely independent hubs operated by different companies or organizations. This is the essence of what it means when we say Hubzilla is a decentralized network. We like to call the network of Hubzilla-powered websites “the grid”. There is no single entity that controls the network or, by extension, you. It is ironic that this needs explanation, because the most ubiquitous and long-lasting online communication system — email — is a shining example of decentralization. Anyone can run an email server and exchange emails with other people, even if they are using an email server hosted by a separate business or university. As robust as email has been historically, however, it lacks a lot of capabilities that we want in modern communication. It is designed for passing small messages back and forth; it is not designed for controlling access to published content hosted on a modern website using secure encryption methods. This is what Hubzilla is designed to do. Hubzilla lets you do things like share photos privately with only your family and friends, or publish news articles only to paying subscribers, even if none of these people have an account on the server hosting the content.

What makes Hubzilla truly unique is combining the ideas of decentralized access control and identity ownership. The result is something that is frankly revolutionary: it’s called nomadic identity.

To be clear, providing decentralized access control is an impressive feat per se. There are only a few other platforms available that provide this capability on the « standard » internet of websites accessible by browsers over HTTP. What makes Hubzilla truly unique is combining the ideas of decentralized access control and identity ownership. The result is something that is frankly revolutionary: it’s called nomadic identity. Truly owning your online identity means that you maintain your contacts and access to the things people have shared with you even if you change accounts on different servers. It means that you can have clones of your identity on independent hubs allowing you to maintain your online presence and continue communicating even when one of your servers is unavailable (temporarily or permanently). No other platform provides this level of robust identity ownership.

Visit http://hubzilla.org to learn more about what Hubzilla can do for you…

The first web site

Do you know the first web site of the world.  It was http://info.cern.ch In Switzerland

Even today you can browse it as it was in 1991.

 

 

Osada is abandoned

6 month after his launch. The project Osada is abandoned by his creator.

Osada will be spun off (separated from Zap) and officially abandoned. If you want to take over the project, go for it. The implementation of Zot6 there is now frozen because future Zot6 work (and Zot8 – more on that in a moment) will not be compatible with ActivityPub. At all. As far as I know Osada is the only viable ActivityPub server for events and groups, but Friendica and Hubzilla aren’t very far off.

For those of you who don’t remember, Osada was a new platform with a UI reminiscent of Hubzilla that was specifically developed to support both Zot6 and ActivityPub-based networks. Macgirvin seems to indicate, in hindsight, that this was a mistake.

Zotiverse in january 2019

Zotiverse is a new word. It is the univesere that use zot protocole. : Hubzilla – Osada – Zap. Zot is much more powerfull than ActivityPub. It allow higher degree of security and anonity. But the best of zot is the nomadic identity.

Hubzilla is the most established product. It should be considered more of an « application platform » or maybe a « publication platform » (kind of like what WordPress has become since it now has plugins that allow you to do almost anything – it’s more than a Content Management System). « Social Media » on Hubzilla was one of the first use-cases adopted by a large number of people – and so many think it is primarily a social media platform. It is not. It is a privacy and security aware application platform that can support a huge number of use cases through the plugin/addon architecture which is lean and efficient.

Osada is more intended for end users interested specifically in Social Media applications that want to be able to communicate with ActivityPub but also have SOME of the privacy and security capabilities offered by Hubzilla. ActivityPub has a larger user base but is fundamentally incompatible with certain privacy and security models. So, anything related to ActivityPub is going to be a compromise. Osada is a social media platform that brings as much of the privacy and security features of Hubzilla as is possible while still providing integration with ActivityPub

Zap is a social media platform for those who are privacy and security minded and are not willing to compromise privacy and security just because « everybody is doing it. » It has the full range of privacy, security, and censorship resistant features inherent in the Zot protocol as Hubzilla (without Federation addons).

If you are an « end-user » of social media and want to be able to seamlessly communicate with ActivityPub, you want to use Osada. If privacy, security, and censorship resistance is important to you and you’re willing to give up access to other protocols in order to maintain those things, you probably want Zap. If you are primarily interested in providing content and data to others on an extensible and robust manner with privacy, security, and with built in ability to provide redundancy in case of failure or as a censorship resistance feature, you want to consider Hubzilla.

In other words, Hubzilla, Osada and Zap are the same kind of application with different tasts.

Now we are in transiton period. Because Hubzilla use an old version of zot. Osada and Zap use a new version (zot6). Once the Zot6 implementation on Hubzilla is complete, all of these projects will be able to intercommunicate with users on each of the others with fine-grained access control.

Source : a post of M Dent

Add ActivityPub to your wordpress blog

Matthias Pfefferle annouce the avaibility of the plugin ActivityPub for wordpress.

This plugin implements the ActivityPub for your Blog. Your readers will be able to follow your Blogposts on Mastodon and other Federated Plattforms that support ActivityPub.

You can follow new post from any other activitypub account and comment. The comments comes directly to your wordpress comments.

Hubzilla 3.8 out

Mario announce in a post the availibility of Hubzilla 3.8

As you can see from the changelog, Hubzilla has gone through a very busy development cycle. To simplify the settings and improve the general UX, we have re-organised the entire apps and settings infrastructure.
Some features from the « Additional Features » section have been transformed to stand-alone apps and will need to be installed by the channel owner. Other features have been moved to the per app settings pages which are now easily accessible from the navigation bar or the app store.
Some addons have already been ported to the new apps infrastructure. This work is ongoing and will be completed during the next development cycle.

Other notable changes:

 

    • Remove tech-levels
    • Markdown table support
    • New addon (channelreputation) which provides a reputation system for community channels
    • Implement a subscriptions submodule for the cart addon
    • New addon (hsse) that implements a WYSIWYG editor
    • Experimental queue worker improvements (off by default)
    • Many under the hood improvements and bugfixes

 

As always, a big THANK YOU! to the translators and everybody who is helping to improve Hubzilla.

Howto upgrade:
Due to some profound changes to the addons it is necessary to follow this update procedure:

 

  • util/safemode on this will disable all enabled addons
  • util/udall the actual update which executes git pull for core and addon repos
  • util/safemode off this enables the previously disabled addons again
  • Install the upgrade info addon (optional) – this will show some info about the upgrade to your community members

Osada decentralised social networking

After Gnusocial, after Diaspora, After Friendica, hubzilla, Mastodon and others an new social network is coming.

OSADA

Osada is a decentralised social networking application more familiar to refugees from Facebook and other conversational style social networks than it might be to those migrating from microblogging social applications such as Twitter.

Osada is very easy to use and provides a range of features either natively or through standard ‘Apps’. These include photo albums and file storage managers, events with attendance support, and topical groups/forums, all of which respect your personal privacy groups (such as Friends, Family, Coworkers, you name it).

ActivityPub Support

Osada has native support for the ActivityPub protocol (W3C standard) as well as the more advanced but lesser known Zot6 protocol. It can inter-operate with other social networking applications and projects in either of these spaces; for instance Mastodon, Pleroma, Pixelfed, PeerTube, Funkwhale, Zap, Friendica, Hubzilla, and many more.

Hyper-drive

A novel Osada feature which is unique to Zotlabs projects is the built-in hyper-drive social engine. This technology is essentially the secret sauce behind Facebook’s meteoric growth over a decade ago and this is the first time we’ve managed to replicate the essential bits using a decentralised protocol.

Public servers

There are a small but growing number of public servers available if you would like to try Osada without providing your own personal or community server environment. A list of these is available here. Only sites on this list with « Osada » in the « Software » name are compatible with projects using the W3C ActivityPub protocol. As the project is still in its infancy, we welcome additional public servers. There is a lot of interest in the project and we could use some help spreading the load.

Free and Open Source

The architecture supports themes and addons and a number of these are available today. Osada is open source under the permissive MIT license and runs on most modern LAMP servers, using MySQL/PostGres and Apache/Nginx. We are passionate about providing ethical and decentralised services running on open source platforms.

If you want to install it go to

https://framagit.org/macgirvin/osada

PeerTube 1.0 : a free and federated video plateforme


Peertube is a federation of sites that host videos. PeerTube uses WebTorrent technology. Each server hosts a torrent and each web browser viewing a video reshares it. This allows to share the load between the server itself and the clients as well as the bandwidth used through P2P technology.

The system works via a federation of instances run by independent entities. Each PeerTube server can host any number of videos by itself, and can additionally federate with other servers to let users watch. This federation permits to collectively host a large number of videos in a unified platform, without having to build an infrastructure comparable to that of the web giants. Each server is operated by and stays under the sole administration of a distinct entity.

PeerTube uses the ActivityPub protocol, in order to allow decentralization and compatibility with other services such as Hubzilla, Mastodon

15th of October 2018 the first version 1.0.0 has been relases.

If you want to know more about peertube and join an instance : go to https://joinpeertube.org/en/

 

Osada social network compatible with ActivityPub and Zot6

Osada is a social network compatible with ActivityPub (Mastodon, Pleroma, Peertube, pixelfed, Hubzilla etc… ) and zot6. It is based on the Hubzilla framework. That means if you are familiar with Hubzilla you will not be lost. The founder of Hubzilla never called Hubzilla a social network but a powerful platform for creating interconnected websites featuring a decentralized identity, communications, and permissions framework built using common webserver technology.

Osada is quite new in october 2018 and you will not find many information on search engine now. So if you need to know more I can give you a link on conversation about osada.

conversation 1 Conversation 2

Now let’s talk technicks

 

Osada is a gateway server between nomadic and non-nomadic networks (such as between Zot|Zot6 and ActivityPub|Diaspora|Ostatus). A reference implementation is available at https://framagit.org/macgirvin

The purpose of Osada (« gypsy settlement ») is to resolve the dilemma that software which was not designed around nomadic identity won’t actually work correctly with software that is nomadic. The only other alternative is for all web communications software and protocols to be nomadic-aware and this is unlikely to happen.

In prior efforts such as RedMatrix and Hubzilla, federation with non-nomadic networks was offered as a choice. You could choose federation or nomadic identity. Choosing both leads to a situation where expected communications are not delivered and both federation and nomadic operation are flawed in basic ways. Osada resolves this basic dilemma by providing a gateway service between the two incompatible paradigms.

At a high level, Osada provides a non-nomadic server which can federate with all existing networks (to the extent that those networks permit federation; ActivityPub and Diaspora have limitations on their ability to federate third-party messages between incompatible protocols).

On the nomadic side, Osada does not allow nomadic operation itself, but it supports nomadic communication. It uses a Zot6 concept called « linked identities » to transfer information into and out of the nomadic network. The linked identity on the Osada side is not a clone and has a distinct non-nomadic identity. It can be bound to a nomadic identy on the Zot6 network. All federation and cross-protocol communication occurs at the bridge. If the linked identity relationship is severed for any reason (including failure/shutdown of the bridge), all bridged communications will cease.

Osada identities can be moved/relocated and connections on non-nomadic networks which support account moves will be retained. Connections on services which do not allow moves will be lost.

People inside the nomadic network will make connections to the nomadic identity. People on outside networks will make connections to the Osada identity and will be (likely) unable to resolve the internal nomadic identity as something they are able to federate with

If you want to try osada : https://osada.usezot.net/ the-federation.org have not added that project yet. I hope it will be added soon

 

 

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.

So what does that have to do with Hubzilla? And for that matter, what is Hubzilla anyway? Hubzilla is free and open source software designed to support your freedom and privacy; anyone can run it on their own server and inspect the code to learn how it works. It is an advanced platform for online communications and content publishing that provides decentralized access control. That last bit is the critical difference between Hubzilla and all the other blogging platforms, social networking sites, and messaging systems that dominate the web today, and it is precisely the motivation for inventing Zot instead of choosing from the plethora of existing communication protocols. To appreciate what is so innovative about Zot, we need to explain first what « access control » means and then why « decentralized » makes the problem of access control challenging.

Like protocols, the world has no shortage of access control. Does your house have locks on the doors? Do you let everyone watch you take a shower, or do you prefer to control access to that activity? How about conversations about your finances? I bet you publish those on billboards, right? Of course not! We all constantly control access to things for many reasons.

And sometimes you want to have a private conversation with someone that no one else should read.

Electronic publications and communications are no different. You may want to publish an article like this one for the whole world to read, but you may also want to participate in a restricted access forum online where members of your neighborhood can discuss community issues. And sometimes you want to have a private conversation with someone that no one else should read.

The traditional centralized solutions to these problems have existed for many years and are what virtually everyone currently uses online. This is because it is relatively easy to manage access control when you have one central authority acting as the gatekeeper to content. Facebook is the most influential example of this model. If you send a message to a select group of friends, only they have access to it because Facebook (1) authenticates them by identifying who they are based on their knowledge of their secret account password and (2) authorizes them to access the message by verifying that they are on the message’s access control list (ACL), which is the technical term for what you created when you « sent » them the message.

There are several fundamental and serious problems with this centralized model. Arguably the biggest problem is that you do not own your identity. But that’s absurd, you might immediately retort, of course I own my identity! Well, let’s consider what ownership means. Ownership of identity means, for one thing, control. If you own your identity, you control it somehow. With Facebook and similar centralized services, they alone have the power to create and delete your online identity. They grant you access to your identity when you log in. As the years roll by and you share all sorts of content with all the people you have connected with, you may be alarmed to discovered that you need the centralized service. If you want to leave, all of that shared content and all those connections vaporize. What’s worse, you can’t even share something privately with people unless they also allow their identities to become hostage to the platform. It’s like some kind of pyramid scheme.

They grant you access to your identity when you log in.

Now we can begin to appreciate some of the benefits of decentralization in our online communications. When you register an account on a “hub” — a server running Hubzilla — you can make connections with other people and share things even when they are on completely independent hubs operated by different companies or organizations. This is the essence of what it means when we say Hubzilla is a decentralized network. We like to call the network of Hubzilla-powered websites “the grid”. There is no single entity that controls the network or, by extension, you. It is ironic that this needs explanation, because the most ubiquitous and long-lasting online communication system — email — is a shining example of decentralization. Anyone can run an email server and exchange emails with other people, even if they are using an email server hosted by a separate business or university. As robust as email has been historically, however, it lacks a lot of capabilities that we want in modern communication. It is designed for passing small messages back and forth; it is not designed for controlling access to published content hosted on a modern website using secure encryption methods. This is what Hubzilla is designed to do. Hubzilla lets you do things like share photos privately with only your family and friends, or publish news articles only to paying subscribers, even if none of these people have an account on the server hosting the content.

What makes Hubzilla truly unique is combining the ideas of decentralized access control and identity ownership. The result is something that is frankly revolutionary: it’s called nomadic identity.

To be clear, providing decentralized access control is an impressive feat per se. There are only a few other platforms available that provide this capability on the « standard » internet of websites accessible by browsers over HTTP. What makes Hubzilla truly unique is combining the ideas of decentralized access control and identity ownership. The result is something that is frankly revolutionary: it’s called nomadic identity. Truly owning your online identity means that you maintain your contacts and access to the things people have shared with you even if you change accounts on different servers. It means that you can have clones of your identity on independent hubs allowing you to maintain your online presence and continue communicating even when one of your servers is unavailable (temporarily or permanently). No other platform provides this level of robust identity ownership.

Visit http://hubzilla.org to learn more about what Hubzilla can do for you…

Podcast about funkwhale

Funkwhale is a modern, self-hosted, free and open-source music server

 

Funkwhale is a music plateforme federated by Actitiypub

 

  Unlimited music

Funkwhale is designed to make it easy to listen to music you like, or to discover new artists.

  • Click once, listen for hours using built-in radios
  • Keep a track of your favorite songs
  • Playlists? We got them

  Clean library

Funkwhale takes care of dealing with your music.

  • Import music from various platforms, such as YouTube or SoundCloud
  • Get quality metadata about your music thanks to MusicBrainz
  • Covers, lyrics, our goal is to have them all 😉

  Easy to use

Funkwhale is dead simple to use.

  • No add-ons, no plugins : you only need a web browser
  • Access your music from a clean interface that focus on what really matters

  Your music, your way

Funkwhale is free and gives you control on your music.

  • The plaform is free and open-source, you can install it and modify it without worries
  • We do not track you or bother you with ads
  • You can invite friends and family to your instance so they can enjoy your music

You’re interested? Some things are still missing to make the project easily installable, but this is moving fast. We’ll be publishing installation instructions soon, stay tuned!

Nomad mobile application for hubzilla

Nomad is an application for Hubzilla. It  You can install it from the Fdroid application.

 

It’s currently under development and should be used with that in mind. Please submit any bugs you might find. We are basing our work on the dandelion* app. The is a webview based app developed as a WebApp

Why is a WebApp better than using the mobile site on a browser? Basically it provides better integration with the system (events coming into and going out of the app), customized interface and functions and a nice little icon that takes you directly to your favorite social network 🙂

Follow news from the Nomad Channel nomad@hub.disroot.org

 

Go to this page to download it

 

Maybe this application works with Osada and zap

Articles plus anciens «