We Distribute
 Map last edited: Wed, 23 Nov 2016 14:07:29 -0600  
Jason RobinsonJason Robinson wrote the following post Sat, 19 Nov 2016 06:13:51 -0600
[FOSDEM] #Decentralised #Internet devroom - CFP

Call for proposals open for the #FOSDEM decentralized internet devroom until 4th December. Would be cool to see some social media projects like #diaspora, #friendica and #hubzilla tell a bit about themselves there.

Brussels / 4 & 5 February 2017

Stand proposal form

Submissions are now closed for 2017.
To late possible next year

We Distribute
 Map last edited: Sat, 19 Nov 2016 20:42:13 -0600  
Riot is a instant communication tool, and can be used in a similar fashion to Slack or IRC. As a protocol, it leverages Matrix.


Riot's main benefits lie in its designs, protocol usage, and client implementation. Clients are available for iOS and Android; a web UI is also available. Regardless of the device you access Riot on, the UX experience remains consistently the same. As an added benefit, the clients are fairly speedy in presenting real time updates.Users interested in hosting their own server can learn about Synapse, the server reference implementation run by Matrix.org.


Riot's UI is simple and animated, reflecting updates to real time communication. Read receipts are provided for every message sent, and used as a type of visual pointer to show how far in the conversation a person has read.


Riot provides a directory to connect with rooms across different servers. One unique aspect of this is that it is also possible to search for rooms on IRC and Gitter, allowing for a seamless experience that bridges all three systems at the same time.


The value proposition here is interesting. In a sense, individual rooms in Riot can be bridged with an IRC Channel, a Slack room, or a Gitter community. From a practical point of view, this can be used to connect several hubs on community conversations together, and provide a type of graceful degradation for anyone who would rather use their existing IRC applications to communicate.


Small community channels have popped up on Riot, and many of them are provided for free by the Matrix.org service. However, it is possible to self host an instance and federate available rooms to the Matrix.org directory. Users logged in to their own instances will be able to seamlessly connect with whatever room you're hosting.


Finally, the real killer app of Riot may be its provisions for data integrations.  It can provide bots to integrate with a Github repository, GIF sharing services, Continuous integrrations for code testing, and RSS feeds. A particularly compelling case could be made here for integrating a series of self-hosted apps such as #Loomio, #NextCloud, and #WeKan. In doing this, a group or organization could keep track of updates from each app in real time.

In short, Riot is extremely promising and presents a great UI for the web and mobile devices. It can be used for ad hoc communication
 Riot  Matrix
We Distribute
is matrix something in relation with redmatrix?

No, they are separate projects. (RedMatrix also is primarily identified as #Hubzilla now).

With that being said, the core difference between #Matrix and #Zot are primarily in what they are used for. Matrix is geared more for decentralized instant messaging in a chat like form factor, with data integrations from practically any source. Some of these integrations serve as bots, whereas others might extend the interface or set how certain link previews work. With some work, oembed previews could also be made available from a number of sources.

#Zot is geared more towards a personal data store with an identity provider and privacy settings for content. While there's no reason you couldn't use Zot for instant messaging (Hubzilla comes with a fairly instantaneous chat system of its own, for that matter), the design behind Matrix is intentionally suited for passing messages quickly in an interface intended for instant updates. Some of Matrix's protocol seems to be built around rooms as a fixture, in the sense that the spec models itself for chatting.
Andrew Manning
Unfortunately Hubzilla can't take the high ground when it comes to public, accessible and current documentation. In open source land it's really hard to persuade the people knowledgeable enough to write technical documentation to do so instead of improving the software itself. I struggle with this frequently.
Letter Bomber
@Andrew Manning While it's true Hubzilla leaves a bit to be desired in that department, I feel like it gets a pass since it can't seem to accrete more than 5 developers at a time. I think diaspora has many more than that, and they also get large donations and funding and such, and then there's matrix which probably has even more developers and more money. And here's the thing about matrix that makes me so critical, they advertise themselves as being a protocol. If that's your centerpiece then make it a documentation priority. But of course it's a lie as with all things from silicon valley. What they really want is a userbase. In this case I suspect a userbase of talented developers is what they are trying to snag.

We Distribute
 San Francisco, CA (Map) 
Due to the impending shutdown of DeadSuperHero.com, We Distribute will now be located on LastAuth.com instead. You can find us at wedistribute@lastauth.com.
We Distribute
  last edited: Tue, 16 Aug 2016 16:02:53 -0500  
Great work from @Jason Robinson on his project, SocialHome, a federated web project powered by #Django.

Django application that provides users the ability to create content for their profile which is then displayed in grids. Content can be Markdown or HTML, featuring a WYSIWYG editor.

All content is designed to be federated using the Diaspora protocol. In addition to profile content, users will be able to create non-profile content (in a more traditional status message way) and read streams of other user content from local users or other nodes via the federation layer.

Jason RobinsonJason Robinson wrote the following post Tue, 16 Aug 2016 15:42:10 -0500

Having fun with #Django Channels and #Websockets.

#Socialhome getting some push-to-view for new posts in stream. When new posts are available, a "posts available" label will pop up. Clicking it will make the new posts visible.

Popping-up-label not in included #gif since waiting for #federation would make a too large gif :)
Jason Robinson
 from Diaspora
Thanks man! :D

We Distribute
Community developer @Kent Shikama has written up an interesting post about the possibility of integrating the Vector client and and Matrix protocol with Diaspora pods.


...I just love Vector-web’s UI, and thus I tried integrating Vector. I currently have Vector integrated into Diaspora to the point where Diaspora can automatically create a Matrix user based on the current user’s username in a similar fashion to how the current chat with JSXC/XMPP works.

I think the greatest challenge would be helping finish the Matrix-XMPP bridge and figuring out how seed migration for chat history would work (or if it is even possible). While I am pretty motivated to continue down this road, I just want to confirm that there aren’t more efficient alternatives of obtaining a full-page front-end chat client within Diaspora.

It's nevertheless a very interesting development, and raises questions about how the chat and private messaging system could be unified further down the road.

#Diaspora #Vector #Matrix
 from Diaspora
My problem with this is that adding more protocols to the mix will inevitably create more fragmentation. And fragmentation is exactly the opposite what the FLOSS decentralized federated social networks need.
 from Diaspora
I am pretty sure the exact same UI can be used for XMPP by the way.
Mike Macgirvin
I would comment, but I believe that flaws in the protocol that Michal is using will prevent him from seeing it. How ironic.

We Distribute
The rewrite of Diaspora's federation system has been a long time coming - within the Diaspora developer community itself, there has long been a held consensus that the underlying federation system required a lot of love. In particular, much of the federation system was hard-wired for Diaspora's specific federation protocol.

A GitHub issue opened on August 12th, 2014 has documented the long-running discussion and leg-work involved for this kind of transition. Since the opening of the issue, a series of rewrites, system fixes, testing tools, and the compartmentalization of federation calls have all been incorporated along the way. A pull request was finally merged on June 25th, 2016.

A huge shout-out goes to @Benjamin Neff for the main work, as well as @Jonne Haß , @Dennis Schubert , and @Senya all giving extensive amounts of feedback and testing on the PR. This is probably one of the biggest changes #Diaspora has merged in for some time.

The Magic Moment - merging the federation rewrite
by denschub on YouTube

Benjamin Neff
 from Diaspora
All changes are documented in the federation-repo: https://github.com/diaspora/diaspora_federation/issues (note that the merged code only is the first step: add forward compatibility)

also I'm currently writing a complete documentation/specification for the future-federation-protocol, after all planned changes.
Mike Macgirvin
There could be one or two surprises but hubzilla should be mostly OK with this round of changes. There were a couple of new protocol changes that just showed up in the last week or two but we should be covered for all the earlier changes. There's another cutover down the road that will require some additional work when the old compatibility layer is removed.
 from Diaspora
diaspora-fr soon updated to the new federation implementation :D

We Distribute
Mike MacgirvinMike Macgirvin wrote the following post Sun, 19 Jun 2016 21:30:25 -0500
Announce: Hubzilla 1.8
Hubzilla Community Server release 1.8 is now available.


Hubzilla 1.8
        Cleanup and resolve some edge cases with addon repository manager
        Provide sort field and direction on all fields of account and channel administration tables
        Rename 'user' administration to account administration to reflect its true purpose
        'safemode' tool to quickly disable and re-enable addons during a hypothetical upgrade crisis
        Edited comments to private posts could lose their privacy settings under some circumstances
        Provide zot-finger signatures to prevent a possible but rare exploit involving DNS spoofing and phishing
    ACL selections:
        Various improvements to the ACL editor to further simplify the concepts and make it more intuitive
        Notifications of chatroom activity using standard browser notification interfaces.
        Allow a theme:schema string to represent a valid theme name. This fixes issues with setting schemas on site themes.
        Show server role (identify UNO or basic sites as opposed to hubzilla pro) and link to statistics
        Clarify privacy rights of commenters w/r/t conversation owners, as this policy is network dependent.
    Wiki (Git backed):
        Brand new feature. We'll call it experimental until it has undergone a bit more testing.
    Account Cloning:
        Regression on clone channel creation created a new channel name each time.
        New issue (fixed) with directory creation on cloned file content
    Content Rendering:
        Add inline code (in addition to the existing code blocks) to BBcode
        Add emoji reactions
        Add emojis as extended smilies with auto-complete support
        Emoji added as feature so it can be enabled/disabled and locked
        Ability to configure the standard reactions available on a site basis
        Disable 'convenience' ajax autoload on pgdn key, as it could lead to premature memory exhaustion
        Change album sort ordering, allow widgets and plugins to define other orderings
        Synchronise app list with changes to system apps
        Preserve existing app categories on app updates/edits
        Regression: fixed translated system app names
        Provide autoloaded class files and libraries for plugins.
        Further refactoring of session driver to sort out some cookie anomolies
        Experimental PDO database driver
        Creation of Daemon Master class and port all daemon (background task) interfaces to use it
        Create separate class for each of 'Cron', 'Cron daily', and 'Cron weekly'.
        Always run a Cron maintenance task if not run in the last four hours
        Refactor the template classes
        Refactor the ConversationItem mess into ThreadItem and ThreadStream
        Refactor Apps, Enotify, and Chat library code
        Refactor the various Config libraries (Config, PConfig, XConfig, AConfig, AbConfig, and IConfig)
        Created WebServer class for top level
        Remove mcrypt dependencies (deprecated in PHP 7.1)
        Remove all reserved (including merely 'not recommended') words as DB table column names
        Provide mutex lock on DB logging to prevent recursion under rare failure modes.
        Remove db_close function on page end - not needed and will not work with persistent DB connections.
        Undefined ref_session_write
        Some session functions needed to be static to work with CalDAV/CardDAV
        CLI interface: argc and argv were reversed
        HTML entities double encoded in edited titles
        Prevent delivering to empty recipients
        Sabre library setting some security headers for SAML after we've emitted HTML content
        Always initialise miniApp (caused obscure warning message if not set)
        Block 'sys' channels from being 'random profile' candidates
        DB update failed email could be sent in the wrong language under rare circumstances
        Openid remote authentication used incorrect namespace
        URL attached to profile "things" was not linked, always showing the "thing" manage page
        New connection wasn't added to default privacy group when "auto-accept" was enabled
        Regression: iconfig sharing wasn't working properly
        CalDAV/CardDAV plugin provided
        Issue sending Diaspora 'like' activities from sources that did not propagate the DCV
        Allow 'superblock' to work across API calls from third party clients
        statistics.json: use 'zot' as protocol
        Issues fixed during testing of ability to follow Diaspora tags
        Parse issue with Diaspora reshare content
        Chess: moved to main repo, ported to 1.8

#announce #hubzilla
We Distribute
diaspora* HQdiaspora* HQ wrote the following post Mon, 20 Jun 2016 07:17:59 -0500
It was a long weekend for #diaspora!
  • ​@Dennis Schubert reviewed and integrated a lot of pull requests (including those listed below) and corrected a potential security problem #6872
  • ​@Senya corrected some internal diaspora* problems #6812, #6844
  • ​@Augier started to work again on the new publisher with a markdown editor integrated #6551
  • ​@Benjamin Neff corrected the "What's new?" URL which was broken in some situations #6869 ...
  • and he especially opened the most important pull request for diaspora* ever (?) : the total extraction of the federation code in a separate layer, meaning the federation should now work waaaay better and sould be easier to patch. He spent more than one year on this task and we should thank him veeery much. Dennis and ​Jonne Haß immediately started to review his work to try to integrate it as quickly as possible. #6873
  • ​@Steffen van Bergerem corrected a mention problem in the publisher #6870 ...
  • ... migrated our test suite from Selenium to poltergeist (phantomJS). It is now faster to execute #6768 ...
  • and wrote a new default home page for users and styled the one for podmins #6268
You will be able to enjoy all these improvements in the next major version of diaspora*,, hopefully coming this summer if the integration and the tests of the new federation are completed without a hitch.

You can follow every commits made in the project directly in diaspora* by sharing with ​​@Commits to Diaspora (commits@social.mrzyx.de)

#diaspora-dev #diaspora-federation

We Distribute
The recent announcement of the OwnCloud Foundation followed by the announcement of fork of OwnCloud is bound to raise more than a few eyebrows. What happened? How did things get to this point?

Catching the Next Cloud
Earlier today, Frank Karlitschek, co-founder of #OwnCloud, made an announcement about the formation of a new project. Five weeks prior, he had left the company that he had helped start, and some of the core development team have followed him to their new project, NextCloud.


Frank describes a vision for what he wants out of this new project and its respective community: a project that does development out in the open, without any contributor agreements or dual-licensing schemes, with a new trademark held by an independent foundation. A better company culture where shares are equally held by employees, with the hand of development decisions guided by the community-at-large rather than a disconnected small team.

To paraphrase Frank, the best parts of OwnCloud are to be extended to fully support what the community has been asking for: better apps, with features that previously only existed for enterprise customers. In his own words:

We will release a drop in replacement for ownCloud in a few weeks so that users and customers can easily upgrade to Nextcloud to benefit from the new bugfix and security improvements and features. Nextcloud GmbH will provide free support for all current ownCloud customers to simplify a transition.

The OwnCloud Foundation

"One of Frank’s criticisms concerned the need to strengthen the Community. In this regard, we have been working on the creation of the ownCloud Foundation, the formation of which we announced earlier this week."

Recently, the OwnCloud project announced that it was setting up a foundation. While this is a welcome event for any Free Software project, it immediately raised eyebrows. Some of the main criticisms were focused on the nature of the board itself (only 2 seats are elected by the community - the other four are coporate), whereas others have pointed out that only OwnCloud Inc itself appears to have any sponsorship in the foundation.

Meanwhile, a handful of developers of the OwnCloud platform announce that they are leaving their projects. Their announcements can be found on Planet KDE. The general theme appears to be that OwnCloud is putting its corporate needs above its community needs.

The OwnCloud Foundation's had this to say on the matter:
Today’s announcement by our former colleague Frank Karlitschek, that he intends to launch a competitive product to ownCloud into the market using recently poached developers, has both surprised us and – admittedly – disappointed us. In the past, Frank has made a wealth of contributions to the development of the ownCloud Community Edition. With today’s announcement, he is no longer related to the ownCloud project and has started a competing community.

This ends on a particularly strange note, as OwnCloud finally concludes that it has to close its doors after their main lenders cancelled their credit. 8 employee contracts were terminated in the process, and the company will be forced to close its doors. Paradoxically "The ownCloud GmbH is not directly affected by this and the growth of the ownCloud Foundation will remain a key priority."

Andrew Manning
Personally this saddens me, because ownCloud has been one of the rare success stories for free and open source software. Excellent software, widespread usage, consistent and rapid improvements. I hope that this schism does not doom the non-commercial project.
Sean Tilley
It makes me sad too, but it sounds like OwnCloud inc had some internal problems, and the platform as a whole started to have some Diaspora-like community management problems (small core team making all the decisions, community requests drowned out because it didn't align with core team, etc).

At the very least, it will be interesting to see where this ends up.
Sean Tilley
No. It's a volunteer-only project with no corporate backing.

We Distribute
Pirate Praveen** (j4v4m4n)Pirate Praveen** (j4v4m4n) wrote the following post Mon, 21 Mar 2016 09:42:33 -0500
Now you can install diaspora with either #postgresql or #mysql as database using diaspora-installer packages (which use rubygems.org to satisfy dependencies). Earlier we supported only postgresql.

# apt-get install diaspora-installer

for diaspora with postgresql and

# apt-get install diaspora-installer-mysql

for diaspora with mysql

You can install them on current debian stable #jessie from https://people.debian.org/~praveen/diaspora-jessie/

I hope to upload to to official jessie-backports soon, once my key is added to backports acl.

Note: there is also a native debian package which installs everything from debian repositories.


We Distribute
Congratulations to @Senya on meeting his IndieGoGo Campaign goal early! The campaign managed to raise €3500 EUR with over 7 days to go! You can still donate here.

SenyaSenya wrote the following post Sun, 13 Mar 2016 15:19:20 -0500
We have done it!
Hey, people! Just a short note - a few minutes ago a message has arrived from IGG that my goal was reached!

I don't ask of anything more, 3500€ is just enough, however if anything more is donated, I'll stretch my work time respectively and work on some more issues of diaspora*.

Thank to everyone who helped to make that real :)



We Distribute
Debian contributor Laura Arjona will be speaking about #pumpio at Procomuns, an event in Barcelona that may best be described as the following:

An encounter which aims to highlight the relevance of the commons-oriented approach of peer production and collaborative economy, while proposing public policies and providing technical guidelines to build platforms for collaborative communities.

During the weekend there are also lightning talks where I'll try to show also GNU #MediaGoblin and #GNUSocial.

If you're in Barcelona this week for #Procomuns, you should definitely check it out. Federated technologies are a great fit for Free Software, and it's important that people continue to learn about what these technologies can do for them.
Letter Bomber
oh. Can hubzilla connect with those channels then? can redmatrix?
Mike Macgirvin
  last edited: Fri, 11 Mar 2016 16:57:50 -0600  
You can cross-post with the pumpio plugin (which uses oauth and atompub so it's one side of a working protocol stack). Some basic ActivityStream2Json-LD translators are available in include/items and you're free to work on improving these. I started on it long ago, but stopped further federation work until we had a solution for the nomadic identity incompatibility. I may or may not get back to that sometime after the GNU-social plugin is completed and at about the same priority; which is to say it's on the bottom of the list.
Sean Tilley
Hypothetically, you could connect them. I recall Mike was experimenting with Pump.io federation a long time ago.

In general though, an ActivityPub implementation would allow for federation with any other platform that implements it, under the assumption that other applications implemented the protocol spec with matching application policies. (For example, private posts cannot be re-shared by the app).

Incidentally, Christopher Webber from MediaGoblin has been doing a lot of work on his end to provide a good implementation of it. There's a reference implementation or two for ActivityPub, and work is ongoing for MediaGoblin to adopt it as well.
We Distribute
diaspora* HQdiaspora* HQ wrote the following post Tue, 08 Mar 2016 16:13:32 -0600
diaspora* security release
We just released diaspora* version which disables post fetching for relayables. Due to an insecure implementation, fetching of root posts for relayables could allow an attacker to distribute malicious/spoofed/modified posts for any person.

Disabling the fetching will make the current federation a bit less reliable, but for a hotfix, this is the best solution. We will re-enable the fetching in when we moved out the federation into its own library and are able to implement further validation during fetches.

Please update as soon as possible. Update instructions are available as usual in the wiki.

#diaspora #announcement #release  #0571
Nice but have you make more easy to install is always a nightmare install and upgrades
Sean Tilley
Not necessarily. I will admit that it is different from maintaining a PHP app, but running a Ruby webapp or a Python webapp just have discrete ways of doing things that differ from framework to framework.
I install ones I upgrade ones and broken down I no install more. And I believe I am not the only got issues with installs and upgrades for the seam reason I left owncloud is php

We Distribute
@Mike Macgirvin released an updated plugin for the #Wordpress platform recently. Allegedly, it allows for the federation of posts and comments between #Hubzilla and Wordpress.

This is an update of the excellent redmatrix_wp plugin to connect WordPress and Hubzilla posts and comments. This is installed on the WordPress site and the wppost plugin should be installed in Hubzilla. The plugins communicate with each other to share posts and comments between both programs.

At the moment, the plugin is informally attached to this post. We hope to see continued development in a repo soon, and look forward to testing it with a Wordpress installation.
We Distribute
 Map last edited: Sun, 06 Mar 2016 14:37:30 -0600  

We Distribute
Here's the latest user stats for people connecting with We Distribute. This is just for fun - it's always interesting seeing what parts of the federated web our channel connects with. This is not necessarily representative of each platform's amount of active users.

At the moment, Diaspora is currently in the lead with the most followers, with Pump in second place, and Hubzilla in third.
Yes, but  libertree has not contacts virtually, ALL are  contacts ;-), how you can define your followers?
Sean Tilley
Actually, Libertree does have contact lists. I will admit that I'm uncertain as to how I got that number - in reviewing things, I cannot find the figure anywhere. But it was somewhere within Libertree that I did find this information. :P
in libertree  is impossible to define how many people follow you, truly even those people who do not have put you on their list of contacts can follow you and read you, so that number could be much larger in reality.

We Distribute
 Map last edited: Mon, 20 Jun 2016 10:10:37 -0500  
A recent plugin was added to the Hubzilla Plugins Repo called Pubsubhubub.

PubSubHubbub is an open protocol for distributed publish/subscribe communication on the Internet. It generalizes the concept of webhooks and allows data producers and data consumers to work in a decoupled way.
PubSubHubbub provides a way to subscribe, unsubscribe and receive updates from a resource, whether it's an RSS or Atom feed or any web accessible document (JSON...).

This protocol is used as the subscription component of OStatus, which #GNUSocial supports. I enabled the plugin on my personal channel, which required no setup or configuration of any kind. After entering my handle into GNU Social's remote subscription form, my name and avatar appeared instantly.


I decided to take things a step further by sending over a test post. At the moment, it appears that old posts created before a connection is made don't get federated over. Still, it can correctly reflect any status I post on #Hubzilla.


Unfortunately, comments do not appear to federate back or forth at the moment.

Still, it's clear that this plugin is showing a massive amount of potential in connecting different parts of the federated web together.
there is a problem when  I try using gnusocial:

he takes the avatar picture and the name of the last channel that has posted in the wall.
for example, if I want to follow the ONE  forum, gnusocial  takes as an avatar picture and name (of ONE forum) that of the last person (channel) that wrote in the wall page.
So I follow ONE but  in  my list of /subscriptions  I see  misterX.
Sean Tilley
That's interesting. I suppose this is mostly happening to forum channels, since GNUSocial's assumption may be that it is supposed to treat the connection like a single user stream.
We Distribute
LibrePlanet 2016LibrePlanet 2016 wrote the following post Mon, 29 Feb 2016 15:00:00 -0600
Christopher Webber - Federation and GNU (LibrePlanet2015)

(if you can't see the embedded video in this post, you can watch it directly here:
Christopher Webber - Federation and GNU — GNU MediaGoblin)

The effort to re-decentralize the web has been under way for a number of years, but what's really happening under the hood? Various projects like #Diaspora, #GNUsocial, #MediaGoblin, #Friendica, and #Pump all exist, but not all these projects can talk to each other. How can we fix that? A demo of PyPump will be given, as well as a rundown on the progress of the W3C Social Working Group.

Chris does a great job detailing the history of projects within the space, as well as the underlying concepts as to how most of them work.
Brandon Smith
 from Diaspora
Yeah I already noticed it. I thought I deleted that comment? Wth?
Sean Tilley
Eh, deletion is not always an assured thing with federation, especially when its across different platforms. That's hopefully something that can change as time goes on.

We Distribute
(originally shared on the Pump.io network by the #MediaGoblin project)

It might not look like much, but the screenshot above is the first demo of federation in MediaGoblin. This is using the Pump API, with MediaGoblin talking to Pump.IO!


The Mediagoblin project has been making great strides in incorporating the upcoming ActivityPub standard, and have gone as far to have developed a related toolkit for Python called ActivityPy. One noteworthy feature of the ActivityPy toolkit involves its ability to load both ActivityStreams and Microformats side by side and convert both things into into Linked Data. The Mediagoblin blog had this to say of it:

The agreement that ActivityStreams, Linked Data, and the “IndieWeb Stack” (for lack of a better term) were not required to work together, and that we could produce multiple deliverables, has eased that tension in the group and allowed us to work collaboratively.

The project has reiterated that there is still much work to be done. However, it is very exciting to see their progress.
Michael Vogel
 from Friendica
@Letter Bomber What do you mean with "never gave any details"? Do you mean this - public available - specification: https://www.w3.org/TR/2016/WD-activitypub-20160128/

Or do you mean this one? https://www.w3.org/TR/activitystreams-core/
Letter Bomber
I mean when everyone always kept talking about this "new standard" that everyone was working on, no one ever answered WHICH ONE was supposedly the new one, even when directly asked at CCC. They always changed the subject. You're focusing on attacking my comment instead of answering my question, what's the point and how is it any different than pubsubhubhbubububub
Letter Bomber
The really sad part is, if you jumped in a time machine and went back 16 years, then published that standard, everyone would've been like "sounds reasonable, let's implement it". There's really nothing groundbreaking, unusual, or remarkable in any way. In a lot of ways, it's a throw-back to the old way of doing things. That's just so so sad. So sad that it took this long...

We Distribute
CLICK HERE to support Account backup and restore for diaspora*


My name is Senya and I am a software developer from Russia with 7 years experience of commercial software development. I've been participating in diaspora for the past six months and already have some code merged in the upstream (and here is some from the diaspora_federation gem). There are a plenty of jobs available for a programmer such as myself, but I dream of doing something fundamentally important and don't wish to waste my time participating in yet another company's commercial product.

The feature I propose to implement is an account backup/restore (also referred to as account migration). This is one of the oldest open issues on the issue tracker. In a federated social network such as diaspora, you choose a node in the network (a ‘pod’) on which to open your account and store your personal data. Over time, however, you might want to move your data to another pod: perhaps a pod has opened for a community you’re involved in, perhaps your current pod isn’t performing so well, or perhaps you want to set up a pod of your own so that you have complete control of your data.

Best of luck on your campaign @Senya ! :)

-Aucun autre réseau fédéré ne le propose, nous serons donc à la pointe.-

evidently a statement such as this must be based on information and not on imagination.
The intentions are good, but you have to be careful what you write, not to hurt the intelligence and the work of other people.
Mike Macgirvin
On the other hand, maybe we at Hubzilla are spoiled with someone like Mike that does this all (and a lot more) for free.

You may possibly just be oblivious to the exchange of resources and consideration which keep projects like this viable. There is definitely a cost, and it is *huge*.
Yes for you and that's why I said 'spoiled'.