Skip to content

Live testing of remote categories

ActivityPub Test Kategorie
63 10 1.8k
  • Unicode in handles

    ActivityPub unicode activitypub
    15
    0 Stimmen
    15 Beiträge
    69 Aufrufe
    julian@community.nodebb.orgJ
    לאצי the usernames work fine locally (that is, on the site itself). It's when interoperating with other sites not running NodeBB where there are issues, it seems
  • 0 Stimmen
    6 Beiträge
    86 Aufrufe
    julian@community.nodebb.orgJ
    feditips@social.growyourown.services ahaldorsen@tutoteket.no feel free to reach out if you have trouble setting up or administering NodeBB. We're on the fediverse, and happy to be here!
  • 0 Stimmen
    17 Beiträge
    139 Aufrufe
    julian@community.nodebb.orgJ
    Hey rimu@piefed.social thanks for responding (and sorry for the late reply!) I am not married to the Announce([Article|Note|Page]) approach, so I am definitely open to Create([Article|Note|Page]) with a back-reference. I think I went the former direction because there is a known fallback mechanism — the Announce is treated as a share/boost/repost as normal. However, sending the Create also is fine I think. However, do we need a backreference? In my limited research, it seems that Piefed, et al. picks the first Group actor and associates the post with that community. If I sent over a Create(Article) with two Group actors addressed, could Piefed associate the post with the first, and initiate a cross-post with the remaining Group actors? Secondly, is how to handle sync. 1b12 relies on communities having reciprocal followers in order for two-way synchronization to be established. On my end since I know it is cross-posted I will now send 1b12 activities to cross-posted communities, but can Piefed, et al. send 1b12 activities back as well, in the absence of followers? cc andrew_s@piefed.social nutomic@lemmy.ml melroy@kbin.melroy.org bentigorlich@gehirneimer.de
  • 0 Stimmen
    17 Beiträge
    202 Aufrufe
    julian@community.nodebb.orgJ
    @esoteric_programmer@social.stealthy.club that's likely because GtS handles summary as a content warning for everything. The whole summary and content warning business is in flux right now, so hopefully a standard will be set soon.
  • 0 Stimmen
    8 Beiträge
    111 Aufrufe
    julian@community.nodebb.orgJ
    @evan@cosocial.ca hmm. I agree in the sense that any combination of recipients can be addressed, but the specific term "follower only" (to the exclusion of the public pseudo-user) isn't AP specific... could be wrong on that one. Either way I do think it's a good courtesy to assume equal or narrower visibility when replying to any post. The specific issue you outlined in OP seems to be a Mastodon bug for sure.
  • 0 Stimmen
    3 Beiträge
    63 Aufrufe
    julian@community.nodebb.orgJ
    @mastodonmigration@mastodon.online while this is a known workaround, I don't think it's a tenable long-term solution. You can have "real decentralization" without the quirks, too.
  • Updates to the world page

    ActivityPub Test Kategorie nodebbactivityp nodebb
    32
    2
    1 Stimmen
    32 Beiträge
    519 Aufrufe
    julian@community.nodebb.orgJ
    @projectmoon@forum.agnos.is said in Updates to the world page: > > > Also, are there plans to merge the federation synchronization and new remote category following stuff together into one cohesive set of functionality? Yes... the remote category functionality supercedes the category sync functionality in some ways, but there is still a use case for it. Most likely I will need to develop proper support for cross-posting (at least locally), and that would work well with the remote category functionality, so that topics are cross-posted to the synchronized category, instead of moved.
  • Reconciling ActivityPub Deletes with NodeBB deletion

    ActivityPub Test Kategorie activitypub
    16
    0 Stimmen
    16 Beiträge
    225 Aufrufe
    julian@community.nodebb.orgJ
    Angus, while I haven't made the appropriate changes to NodeBB's implementation yet, I did draft an FEP including the changes we discussed. https://github.com/julianlam/feps/blob/main/fep/15c5/fep-15c5.md It is not PR'd upstream yet, but I will do so in the coming days unless there are some concerns.