Conversation
Notices
-
@banjofox @mayel how does #Fedibook differ from #Diaspora, #Hubzilla, #Friendica, #NextCloud and all the other projects with similar goals?
-
@banjofox @rysiek #Diaspora is compatible with #Friendica and #Hubzilla, although they reverse-engineered the #DIaspora protocol to get this
-
@banjofox I guess I'm asking why start a totally new project, instead of adding the features you want to one (or more) of the existing ones?
-
@banjofox there's a consensus emerging that full compatibility will be achieved by moving protocol support into shared modules ...
-
@banjofox like a Ruby gem that supports any federation protocol via plugins. Or the Federation library in Python
http://qttr.at/1zsf
-
@banjofox language choice is a totally valid reason for a new project :) A Rust module/ library for federation protocols would be great!
-
@banjofox true, but that was due to the #Diaspora protocol specs being under-documented, having only been used internally up to then
-
@banjofox awesome! Look forward to testing #FediBook when you've got an alpha ready :)
-
@zatnosk @banjofox have you looked into #ActivityPub or #Zot @fla ?
-
@fla @zatnosk @banjofox a bicycle and a monster truck can use the same roading protocol. A bike, being smaller, can be accepted more places
-
@zatnosk @fla @banjofox the truck, being larger and heavier, can carry more stuff, and climb rougher terrain.
-
@zatnosk @fla @banjofox different destinations, different carrying capacities, common carrier. Does that make sense?
-
@zatnosk @fla @banjofox an app defines an API for each data type, connecting to the module, and plugins translate for different protocols
-
@zatnosk @fla @banjofox protocols used in parallel, so every available service is covered by at least one of the protocols, maximum peering
-
@zatnosk @fla @banjofox sorry it's late. Rambling incoherent shower thoughts. Others can explain the proposition better (@deadsuperhero?)
-
@fla @zatnosk @banjofox the difference is that email is a discrete and finite set of functions (send, receive, attachments etc)
-
@zatnosk @fla @banjofox you can't have multi-function client X, and expect all functions to work with all contacts, unless they all use X
-
@zatnosk @fla @banjofox yes, good #UX requires that clients are able to signal to users when a contact can and can't use a service
-
@zatnosk @fla @banjofox but imagine if you couldn't add a new function to any client until you added them in all clients. This is unworkable
-
@fla @zatnosk @banjofox most of the #fediverse / #federation clients now support more than one protocol. I'm not sure exactly how they do it
-
@fla @zatnosk @banjofox most of the #fediverse / #federation clients now support more than one protocol. I'm not sure exactly how they do it
-
@zatnosk @fla @banjofox maybe ask @maiyannah or @gargron or @mike how multi-protocol support works?
-
@fla @zatnosk @banjofox "I hate this branch thing" you can't have or follow meaningful conversations without preserving a sequence of posts
-
@zatnosk @fla @banjofox the inability of most #fediverse / #federation clients to preserve continuity between posts is a major #UX fail IMHO
-
@strypey @zatnosk @gargron @fla @mike @banjofox Short answer: "very poorly"
The thing with Mastodon is that it doesn't follow either standard (OStatus or ActivityPub) particularly well.
-
@zatnosk @gargron @strypey @fla @mike @banjofox As far as doing multiple protocols within postActiv, they're just modules. You can enable one or more and that's the language your instance speaks. Right now postActiv just has OStatus. I have an experimental Diaspora module but it's not tested well enough I'd feel comfy putting it in production. I know someone is working on something for the Friendica thing too.
-
@zatnosk @gargron @strypey @fla @mike @banjofox As far as federating messages outwardly, I need to tighten up version detection of instances but it basically looks at what software your instance is running if its not postActiv, and makes an assumption based on that (OStatus for StatusNet/GNU social/Pleroma/Mastodon, Diaspora for Diaspora, etc). postActiv will have (when these changes are done and pushed to the repo) an option to set which federation module is the "native" one and the internal representations are set accordingly and there is an endpoint postActiv uses to identify this for external instances or clients.
-
@banjofox @zatnosk @fla you could open some Issues, but why GITHub? Why not, say, a Discourse instance
-
For example, the #Diaspora team run their own instance of #Discourse. Here's one run by #Disroot.org
http://qttr.at/1ztn
-
@banjofox @zatnosk @fla I don't understand. Do you want to run your own #Discourse instance? Or move this discussion to an existing one?
-
@zatnosk @fla @banjofox sorry I might have been better to ask clarifying questions when you brought up GITHub ;)
-
@zatnosk @fla @banjofox are you already using GitHub for #FediBook dev and wanting to document this discussion there for reference?
-
@zatnosk @fla @banjofox some of us prefer to avoid #GitHub due to the chunks of code they refuse to liberate
http://qttr.at/1zvb
-
@zatnosk @fla @banjofox that's why I thought of moving the discussion to Diaspora's forum, or setting one up on Disroot (both use Discourse)
-
@zatnosk sure, apologies for tofu ;-P
Danyl Strype
Maiyannah Bishop
All Mike Gerwitz's GNU Social Instance content and data are available under the