Iām still looking for a low priced annual payment VPS provider that has a somewhat lower risk (of closure, hardware failure, etc) than most LEB hosts, so I can launch temporary testing instances (for example, the upgrade of GS to the #ActivityPub enabled 2.0 branch, and looking at how well #Zap, #Pleroma, #Friendica instances fit into the !FNetworks roadmap).
Iām also considering adding a Federati #Pump.io instance, but I need to talk with the Pump.io project about SSO options. Since they use Node.JS, Iād want it on a completely separate VPS, with some restrictions to prevent incidents. Also, if utilization is too low, that would likely close.
Currently, everything is still coming out of my pocket.
Caution: this episode is over three hours long, so I have not listened (and will likely only listen to a fraction of it).
I wish @tio had also brought someone from #GNU_Social and someone from #Pleroma (and maybe @mike@loadaverage.org @mike@z.macgirvin.com to represent #Hubzilla and #Zap (and #Mistpark, #Redmatrix), and @dansup developer and project founder / leader of #PixelFed, and perhaps someone from #PeerTube, #Misskey, and so on). The other thing I wish had been done is to slice this far-too-long episode into four pieces, each an hour or less in length.
Sorry, Michael, I don't know whether you're officially the project leader, so I left that unsaid.
@wyatwerp not necessarily. #Hubzilla can federate over AP though, depending if the federation plug-in is installed on the instance or not. Hopefully some of the work @mike has done implementing native AP support in #Zap will be backported to Hubzilla, allowing AP support to be on by default in all hubs, without breaking #NomadicIdentity.
@slimeblob yes, Dispora has it's own federation protocol (a variant of #OStatus), and last I checked its core team adamantly refused to consider adding #ActivityPub. I can see why in a way. D* works quite differently to Titter-a-likes like #Mastodon and #Pleroma. But that didn't stop Mike McG from supporting AP in #Hubzilla and later #Zap. @lnxw48a1
@xavavu given this, how likely is it that the work done on #Zap to develop newer version(s) of #Zot, and move AP support into core, will be backported to #Hubzilla? I've heard that when Hubzilla hubs use the federation plug-in to support AP, Diaspora, and OStatus, it breaks #NomadicIdentity. @lightone
@jessmahler the reason I specify the "AP fediverse" is that some of the other networks that now seem to be included under the conceptual umbrella of the fediverse work quite differently. #Diaspora for example, has always allowed users to choose between posting to public, followers, or subgroups of them (like the "circles" concept in G+), but isn't compatible with AP apps like Masto. #Zot apps (#Hubzilla and #Zap) have a totally different and amazingly granular privacy model, but few users.
@z428 there are various ways to address this. OWS doesn't let clients older than 3 months connect to their servers. A secure chat federation protocol could include refusing to connect to another server that hasn't been updated for more than 3 months. There are all sorts of systems you can use to ensure security across a federated network (ask Mike from #Hubzilla / #Osada / #Zap about it). The only main problem with XMPP is that until recently security wasn't a design goal, but now #OMEMO exists.
@LWFlouisa Mike seems to have moved on to developing #Osada and #Zap, so I'm not sure who the active maintainers of #Hubzilla are these days. Any idea @bob ?
@dwmatiz yes, as a plugin. The platform is stable and federation is currently tolerably good, but will likely improve greatly after Zot6 gets implemented.
@jgmac1106@neil@bhaugen@KevinMarks@cwebber this is already possible with #Hubzilla, using #Zot. Your private posts and shared media stay on the server(s) you host your channel(s) on, and you can decide which other Hubzilla users to share them with. Once Hubzilla is upgraded to Zot/6, it will also federate with two newer Zot apps, #Osada and #Zap.
@macgirvin OK, so once that happens, and #Zap, #Osada, and #Hubzilla are all ready to use together with #Zot/6, there will be 3 reference implementations of Zot, which will hopefully help other projects implement it. But will Hubzilla still have federation plug-ins for #ActivityPub etc? Or will HZ users who to connect with users outside the Zot network need to clone their channel(s) onto an Osada server?
One interesting new development is something called #Osada, which effectively bridges Zot to other protocols like ActivityPub. Not really sure how, but it's interesting: https://framagit.org/macgirvin/osada
"Osada is ultimately designed to bridge #ActivityPub with #Zap, which is a pure Zot/6 social network application; however you might find that it is a quite capable ActivityPub client on its own."