@nprofile1q... That's an old article that probably predates Ghost's implementation of FEP-b2b8. The recent stuff you see e.g. on @nprofile1q... is a better representation of Mastodon's support for long-form articles. Showing the preview text as an inline post is a different approach than a buffed-up link card, but it's no less integrated.

@nprofile1q...

@silverpill Good to know, thank you! IMO there should be no restrictions on the two domains – I use two subdomains for convenience reasons, but platforms should support two completely different domains as well.

At least in my opinion. The vocal opponents of split-domain handles say that a user's handle should tell you where their profile is hosted, and there are nuances around things like domain blocks.

But if you ask me, I should be able to set a custom handle domain in my profile settings. 😄

@Mitra @silverpill Congrats on the split-domain support! I have added Mitra to https://correct.webfinger-canary.fietkau.software/#implementation-status

The only feature it's missing for an all-green table row is per-user custom WebFinger domains. I am on a long-term side mission to advocate for ActivityPub platforms to enable personal custom handle domains this way. ☺️

@nprofile1q... In the long term, @nprofile1q... will most likely focus on capabilities outside of the design of Mastodon Collections: longer lists, curation by multiple owners, etc.

Smaller packs more personal in scope might make sense to be moved to a Mastodon Collection. We'll leave it up to everyone to decide which service fits their needs better.

The safety features mentioned in the post (be notified when you are added, ability to remove yourself) will also be provided by our implementation.

@nprofile1q... Speaking as a contributor of @nprofile1q... which currently hosts Mastodon “starter packs” at https://fedidevs.com/starter-packs/

We're working on interoperability with Mastodon Collections and will use the same technical mechanisms in the future, but completion of this work is months away. We endorse people migrating their Fedidevs starter packs to Mastodon Collections wherever that makes sense.

We were involved with the backend tech behind Mastodon Collections. No competition and no bad blood! 🙂

@nprofile1q... What is the rationale for “Clients MUST NOT embed non-anonymous collections in objects”?

I see the potential for cache poisoning etc. if we inline collections owned by someone else, but what's the harm in inlining my own collections?

@nprofile1q... @nprofile1q... Probably very unlikely as long as the vocabulary isn't in Fedify: https://github.com/fedify-dev/fedify/issues/452 But now that the interaction policy vocab is in, it might not take too much longer.

@nprofile1q... I saw this post when it was new, and two days later I am remembering to come back and tell you that MDN is at @nprofile1q.... 😃 Or did you know that and there's a layer of meaning to your post that's going over my head?

@nprofile1q... I can believe that easily, especially since it seems every encoder has its own CRF range. With SVT-AV1, the default is 35, but I'm usually still mostly fine with 40. My low quality preset for archived live streams uses 50. 😄 A lot about quality is subjective and use-case-specific. Best of luck!

@nprofile1q... Ah cool! Yeah, that's always the trade-off isn't it. My own use case leans quantity over quality, but if you make videos for redistribution then maybe you actually want slower encoding for a better quality ratio.

Here's my full conversion script btw: https://stuff.jfietkau.me/toav1

In my experience, reencoding old H264 videos to equivalent-ish AV1 is still vastly cheaper than buying additional storage. Running that script for a week or so got me nearly a TB back.