Show Navigation
Notices by Maiyannah Bishop (maiyannah@plateia.org)
-
@lnxw37b1 @hobbithabit ActivityPub is basically ostatus v2 with no real gains IMO over just using ostatus so it isn't a priority. Diaspora federation support is in active development - or as active as I can be with my state of health presently.
I am also looking at also supporting the zot and dfrn protocols but those are longer term goals.
-
Hubzilla is completely self-healing in its own network (with about a 24 hour granularity), but for other networks it only probes and corrects once a month because probing for all the different protocols involves a fair bit of resources.
Diaspora will never correct "basic communication data", caching it forever. That's why my home site can only talk to newer Diaspora instances; as it was once a Friendica site and they are still holding the old public key for my webfinger address. Hopefully I'll be able to correct this by sending an account_migrate message once they finally make that work.
GS also holds basic comms data forever from my experience; hopefully this has been fixed but I haven't seen it from here. We changed our feed url slightly a year or two ago and many GS sites still insist on using the old one, so it seems pretty slow to correct.
I can't comment on Friendica or Mastodon.
-
@mike The bug incidentally was that feeds placed in an 'inactive' state would end up stuck such that they couldn't be corrected.
-
@mike Feeds should self-heal in GS when they renew the hubsub since it basically deletes and recreates them when it renews it. But GS has a bug where it can get stuck on old ones, that got fixed a bit ago. A lot of GS instances are pretty dated though.
Mastodon basically keeps hubsubs forever and ever though unless a renew request is explicitly set so yeah.
-
@hobbithabit No, with Mastodon's approach, not mine. The problem is that I receive so many malformed notices (with what is to the specification extraneous data), that my queue for processing notices gets tied up with dealing with those.
-
@hobbithabit Trying to add stuff that isn't in the specification to things and fucking everything up as a result.
-
Incidentally, there are proper ways (ie a script) to retire and relaunch a node that you can do, as long as the node is still operating of course. So you can just do that to salt the earth and it should be fine as long as it federates. If it doesn't, GS/pA should correct data if there's issues. No idear about Hubzilla or Friendica or Mastodon in that regard though.
-
Gonna be honest, 99% of the reason I keep this instance is up is for all the bitching about Mastodon I do occasionally take a hack at trying to fix how it's fucked up federation again.
But it's been an uphill battle. For each mastodon federation problem that I fix, there's 10 more that are just as bad to fuss with. And sometimes the fixes that would be easy would break federation with other things.
This is a lot of the reason I get pretty sour about Mastodon, personal experiences aside.
I'll probably relaunch plateia when the Diaspora federation is complete and let it re-network.
-
@deutrino Newer mastodon has a lot of problems with ostatus, so that's not terribly surprising.
-
@jrmy There shouldn't be, but that plugin is not maintained and could have problems with newer software. If you have error log information related to failures it might help debug them.
-
That said, the network is grown by you following people, so follow more people and you will populate the timeline. You can create an alternative account for this purpose if you do not want to clog up your main timeline with it.
-
@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.
-
@kristofmaven Public Timeline is just people from here, which is just a handful of people. The Whole Known Network will have people from other sites. Most postActiv users just run their own site, and then connect using the network.
-
@jrmy You and I both. Thanks
-
@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.
-
@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.
-
Not too much to report on the postActiv front with me being in the hospital and all, but it hasn't been forgotten. Hopefully when I get out I can get back to it. I've been slowly chipping away at implementing the Diaspora protocol as a module, though.
-
There, manually renewed the cert here. Not sure why the cron didn't work.
-
Should be back up, but I might have to give Federation a few kicks to work itself out.
Maiyannah Bishop
mike
All Jonkman Microblog content and data are available under the