Works Hubzilla@Home -solution? Hubspace as distributed Hubzilla runtime environment

Wed, 10 May 2017 06:30:17 +0200 last edited: Wed, 10 May 2017 18:31:36 +0200

I have an Idea: Workflow for develop and use on demand of Hubzilla plugins immediate on #Hubspace. I publish details to that on my "Feies Internet" (Free Internet) -Channel -s. Works Hubzilla@Home -solution? Hubspace as distributed Hubzilla runtime environment and I am excited about your feedback and above #Hubzilla@Home works !

#HubzillaRuntimeEnvironment #SETI@home #distributedHubzillaEngine #HubzillaProzessor #HubzillaDistributedProzessor #HubzillaBigCloud #HBC #BittorentServer #BittorentServerPlugin #downloadOnDemand #blockchainTechnology #blockchain #HubzillaBlockchain

@Hubzilla Development+ @Hubzilla Support Forum+ @Zot universe NEWS+ @René Röderstein

show all 6 comments

neue medienordnung plus

Wed, 10 May 2017 07:06:24 +0200 last edited: Wed, 10 May 2017 07:25:46 +0200

However, is it not true, that Hubzilla@Home -solution already with feature "Add app" -> Create new app" at least initial implement is?

neue medienordnung plus

Wed, 10 May 2017 08:03:12 +0200 last edited: Wed, 10 May 2017 18:17:22 +0200

Use case for distributed Hubzilla runtime Environment:

Mary installed one BittorentServer plugin fork (BSP-fork)with web interface
Mary enable access for BSP-fork for signed in Hubzilla member
Gustav develop any pluginXYZ
Gustav connected with shimriez@lastauth.com
Gustav signed in on shimriez@lastauth.com
Gustav distributed pluginXYZ on Hubzilla Big Cloud via BSP-fork-web interface on shimriez@lastauth.com -channel.

Mike Macgirvin

Wed, 10 May 2017 10:33:41 +0200

So the only difference between this and what we're doing today is using webtorrent instead of http/dav as a distribution method? Somewhere earlier it looked like you wanted to implement a distributed execution platform like ActiveX and/or DCE/COM/RPC/SOAP. These are interesting but have a number of security issues - and you really don't want to be mixing them with social communications. Otherwise you can easily turn the entire network into a mafia controlled distributed spam-bot which is able to lock you out of your own server. I'm interested to see where you're going with this, but want to make sure you're aware that there are a number of landmines to consider.

Andrew

Wed, 10 May 2017 12:11:15 +0200 last edited: Wed, 10 May 2017 14:20:37 +0200

I do not understand what you are proposing. Hubzilla plugins can use the Zot to allow access to (1) local hub members only, (2) only authenticated members on the network, (3) all visitors including non-authenticated, or (4) some custom access list that the plugin supports on its own. A plugin does not necessarily have to be installed locally on a hub for someone to use it. An example is my Rendezvous plugin. Anyone visiting the plugin with the "secret link" may participate in the map, but only local members can see the page that allows you to create maps.

If you are talking about allowing non-admins to download and install plugins (even cryptographically verified ones), then this will not be allowed because plugins have unrestricted access to the database and web root files.

Edit: I didn't see Mike's comment until a few hours after I posted this reply)

neue medienordnung plus

Fri, 12 May 2017 17:07:56 +0200

@Mike Macgirvin

So the only difference between this and what we're doing today is using webtorrent instead of http/dav as a distribution method?

My goal is in Hubzilla-ecosystem together with other Grid-member such workflows and infrastructure to establish, whereby is it possible:

time-saving distributing, quality check und quick availability of new Hubzilla-Features, for example plugins
quick availability of new Hubzilla-Features for interested members

I thing important difference is, that distribution with webtorrent decentralized is.

However, I strive only for solutions, these satisfied the safety requirements of Hubzilla-project.

neue medienordnung plus

Fri, 12 May 2017 17:29:15 +0200

@Andrew Manning

A plugin does not necessarily have to be installed locally on a hub for someone to use it. An example is my Rendezvous plugin. Anyone visiting the plugin with the "secret link" may participate in the map, but only local members can see the page that allows you to create maps.

Ma Idea is, one workflow with BittorrentServer plugin how with Rendezvous plugin. One member, for example Mary can install BittorentServer plugin and Gustav can test the functionality of this plugin.