Skip to content

OK Fedifriends, I need your help with some complex ActivityPub stuff.

ActivityPub Test Kategorie
14 6 185
  • Backfilling Conversations: Two Major Approaches

    ActivityPub activitypub fep 7888 f228 171b
    26
    0 Stimmen
    26 Beiträge
    317 Aufrufe
    julian@community.nodebb.orgJ
    > One weakness I have noticed in NodeBB's current federation is that posts which are in reply to a topic (e.g. a Lemmy comment) show up as individual threads until (or if) the root post of that topic shows up in the local NodeBB. No, Lemmy does not implement either strategy, they rely on 1b12 only. If NodeBB is receiving parts of a topic that don't resolve up to the root-level post that might be something we can fix. I'll try to take a look at it.
  • Fun with Federation: Lemmy edition

    ActivityPub nodebb lemmy activitypub
    5
    0 Stimmen
    5 Beiträge
    66 Aufrufe
    julian@community.nodebb.orgJ
    nutomic@lemmy.ml let me know if I got any of the details wrong. Much thanks to your team for the assist in debugging!
  • 0 Stimmen
    2 Beiträge
    71 Aufrufe
    julian@community.nodebb.orgJ
    rood@aus.social that... is actually not a bad idea If every account exposed their time zone, then your client or server could simply delay the post the appropriate amount until it's your time zone... 10pm their time, shows up 10pm your time. oooooh.
  • I wrote a #FEP about actor statuses.

    ActivityPub Test Kategorie fep activitypub
    2
    1
    0 Stimmen
    2 Beiträge
    92 Aufrufe
    julian@community.nodebb.orgJ
    Man!!! That screenshot takes me back..
  • 0 Stimmen
    17 Beiträge
    532 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
    8 Beiträge
    285 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
    9 Beiträge
    198 Aufrufe
    julian@community.nodebb.orgJ
    @philipp@social.anoxinon.de I kind of think this is really missing the forest for the trees if your rational is CO2 emissions... I mean, a far greater generator of CO2 emissions would be every single Mastodon instance caching every piece of media it sees...
  • Example Class

    Angeheftet Python3 python json
    3
    0 Stimmen
    3 Beiträge
    245 Aufrufe
    FrankMF
    In meinem PywebIO Projekt tauchte heute ein alter Bekannter auf. Wenn ich einen Eintrag (innerhalb der Liste) löschte, war das etwas durcheinander Ja, den Fehler kenne ich schon was länger und stolper immer mal wieder drüber. Heute z.B. Also mal grübeln Das mache ich, wenn ich einen Eintrag lösche case 'Yes': # delete entrie BackupList.delete((line - 1)) # save json BackupList.save_json() # Load data from filesystem BackupList.load_json() # Reload Tab Backup backup() Ich mache folgendes lösche den Eintrag speicher die Liste lade die Liste baue den Tab wieder auf Das führt aber dazu, das meine Liste die als Objekt im Speicher steht nicht aktuell ist. Im Gegenteil, da ist dann etwas Unordnung. Ich brauchte also die Möglichkeit mein Objekt backups irgendwie zurückzusetzen. Mal gegoogelt und die Dinge sind manchmal wirklich total easy # clear dict backups.clear() Das leert das Objekt und im nächsten Schritt kann ich es wieder befüllen. Lösung case 'Yes': # delete entrie BackupList.delete((line - 1)) # save json BackupList.save_json() # clear dict backups.clear() # Load data from filesystem BackupList.load_json() # Reload Tab Backup backup() Problem erledigt. Damit ich das noch finde, wenn mein Kopf das nicht mehr hergibt, notiere ich das hier.