Conversation
Notices
-
Oneesan succubus (lain@pleroma.soykaf.com)'s status on Thursday, 19-Oct-2017 09:00:29 EDT Oneesan succubus The OStatus federation:
- Only half-defined standard
- One big implementation only
- Features are added ad-hoc, whatever GNU Social wants becomes the standard later
- To be compatible, you gotta do everything exactly like GNU Social, reading the standard documents isn't enough.
The ActivityPub federation:
- Only half-defined standard
- One big implementation only
- Features are added ad-hoc, whatever Mastodon wants becomes the standard later
- To be compatible, you gotta do everything exactly like Mastodon, reading the standard documents isn't enough.-
Michael Vogel (heluecht@pirati.ca)'s status on Thursday, 19-Oct-2017 12:40:56 EDT Michael Vogel @lain This is why I like the Diaspora protocol. Although it isn't a product of any "standard defining commission", it is well defined and documented: http://diaspora.github.io/diaspora_federation/index.html
The biggest implementation is Diaspora, but there are (defined) Feature that aren't supported by Diaspora by now, but by Friendica (and vice versa). Features are added after discussions and are implemented in a way that the other implementers can always keep track. -
INACTIVE (deadsuperhero@social.nasqueron.org)'s status on Thursday, 19-Oct-2017 12:57:48 EDT INACTIVE The Diaspora federation:
-I don't know how the hell we initially defined this standard, our docs were terrible forever and someone just reverse-engineered everything themselves.
-Numerous implementations in Python, Ruby, and PHP
-After an amazing refactor, main federation calls of the platform abstracted into a reusable gem.
-Features are pretty much 1:1 between instances
-Added bonus that every status is able to properly reflect a corresponding thread of comments-
Michael Vogel (heluecht@pirati.ca)'s status on Thursday, 19-Oct-2017 13:23:08 EDT Michael Vogel @deadsuperhero Yeah, @Benjamin Neff did an amazing job. And it was great to see how he managed the protocol change. This was a several months lasting process - and he always had an eye that other implementors were able to keep track. And the new protocol is now extensible and much easier than the old one.
-
-
التنينوكس (dragnucs@social.touha.me)'s status on Sunday, 27-May-2018 14:14:29 EDT التنينوكس @lain Is all of this not enough to be more than 5% documented? https://www.w3.org/TR/activitypub/
-
Oneesan succubus (lain@pleroma.soykaf.com)'s status on Sunday, 27-May-2018 15:20:06 EDT Oneesan succubus @dragnucs you can't implement a server that actually federates by just implementing this standard. -
التنينوكس (dragnucs@social.touha.me)'s status on Sunday, 27-May-2018 15:37:20 EDT التنينوكس @lain what about activitypub.rocks then? It checks if your implementation is compliant.
-
Oneesan succubus (lain@pleroma.soykaf.com)'s status on Sunday, 27-May-2018 15:38:26 EDT Oneesan succubus @dragnucs sure, but your implementation being compliant doesn't mean it'll federate with the network. -
التنينوكس (dragnucs@social.touha.me)'s status on Sunday, 27-May-2018 16:13:51 EDT التنينوكس @lain wat?
-
Oneesan succubus (lain@pleroma.soykaf.com)'s status on Sunday, 27-May-2018 16:14:08 EDT Oneesan succubus @dragnucs wat wat? It's true. -
التنينوكس (dragnucs@social.touha.me)'s status on Sunday, 27-May-2018 16:32:32 EDT التنينوكس @lain this is a subject I don't fully grasp. I need to dig deeper. But, isnt fetching remotes up to the server, either by polling of if the remote provides push notifications? Also, in #OStatus, isnt that managed by pubsub?
-
Oneesan succubus (lain@pleroma.soykaf.com)'s status on Sunday, 27-May-2018 16:36:56 EDT Oneesan succubus @dragnucs the main problem is that mastodon (and most other fedi software) require things that are not in the spec to federate, like webfinger and http signatures. Mastodon also used to have some rather big federation protocol bugs before 2.4.
-
-
-
-
INACTIVE (deadsuperhero@social.nasqueron.org)'s status on Sunday, 27-May-2018 16:15:30 EDT INACTIVE
-
-
-
-
-