Back

@pfefferle@mastodon.social nice, congrats!

Who does your art assets (like the cover photo)? We'd love to work with them too.

@julian it was done by a colleague at #Automattic :)

@AdamStuartSmith they are only for authors for now and you can find them on the profile settings and/or as profile submenu.

@pfefferle Ah, that explains it, I'm using blog profile. Thanks!

@silverpill@mitra.social Whoa, thanks for highlighting this line in the changelog!

I wasn't aware of fb2a until just now, and after reading it, I 100% support it. Was hesitant to follow Mastodon's lead due to the schema.org bit, but this FEP handedly sidesteps it using existing AP vocabulary. Love it. Nice work @trwnh@mastodon.social

@julian @trwnh It is also implemented in Streams. I think implementation list would be useful: https://codeberg.org/fediverse/fep/pulls/375

(my server can parse fb2a attachments, but it doesn't create them yet)

@trwnh@mastodon.social odd... How about this one?

@julian same issue with this one! only shows up on your profile, not in my home feed or mentions. i’m not sure if you made a change recently or if m.s did!

@trwnh @julian this FEP sounds like it wouldn't be too hard to start supporting in Mastodon, though will clients deduplicate based on `name` ?

@thisismissem@hachyderm.io backfill and sync are two components of an overall implementation of resolvable contexts. The context id itself would be the discriminator between different contexts, but there are further discussions to be had (and agreed upon) regarding what a canonical context is, and how contexts relate to each other.

e.g. a given conversation may contain objects that report several different contexts, how do we reconcile that for backfill and sync?

So these issues I'd like to discuss at next ForumWG before I start drafting a report or FEP.

@thisismissem@hachyderm.io lol crap, I thought you were referring to a different FEP altogether.

Nevermind!

@trwnh sorry, I meant other consumers of AP data

@thisismissem well, you either understand the old mastodon format or you understand the new fep format or you understand both or you understand neither.

old: you will ignore Note/Link attachments
new but not old: you will ignore the invalid PropertyValue attachments
new and old: you deduplicate
neither: ignore everything in attachment

@trwnh yeah, so I'm wondering how new + old deduplicates, I think that'd be good to have in writing

@julian speaking of things not federating correctly, i responded on socialhub to a post of yours and it doesn't seem to have made it across: https://socialhub.activitypub.rocks/t/changing-the-domain-of-an-existing-instance/4373/2

@trwnh@mastodon.social thanks, manually pulled it in. @silverpill@mitra.social mentioned the same, but I thought I fixed it.

Looks like I'll have to look into it again. It might be related to how Discourse currently reports the NodeBB topic as the context (since the original thread was from NodeBB) but since it's not actually in the collection it doesn't get added. Chicken-egg problem...!

@trwnh@mastodon.social Okay, so I've tried debugging this a bit and I'm at a loss as to why the notifications don't show up on Mastodon.

I can confirm that:

• The mention is an anchor in content
• It has a corresponding entry in tag
• Each mention in tag is of type Mention with the user's ID (not url!!) as href, and name is their full handle with @ prefix and domain.

Not entirely sure when it stopped working either, and notifications also do not appear on ActivityPub Academy (running v4.1.18).

@carsten welche App in welche App? ActivityPub ist nur das Protokoll zum verteilen der Posts. Du kannst also weiterhin die WordPress App zum Posten benutzen!

@carsten