That makes sense to me. The <title> is metadata, and often includes context that isn't necessary in the article body.

I'm definitely thinking as much about what should be as what is. Since seeing this specific group launch, I've been through a few variations of "how can I keep up with the conversations that interest me?" I'm already cycling through many clients, and it seems like the models are not quite right yet.

I'm posting here from a Lemmy client through my Midwest.social account, but I check my Mastodon.social account more often. I'm mostly shifted to Phanpy, which distinguishes group posts nicely... so I've subscribed to these Lemmy groups from my mastodon account as well. Not a universal client, but maybe better than checking many clients.

I still might miss things; when I think to "check what I've missed", it's probably easier to do in Lemmy's forum model. I haven't seen Phanpy make "look through my groups" a first-class UX use case.

Also thinking about recent readings on fediverse identity and Lemmy cross-posting/group federation and thinking we have a lot still to figure out. (I really have a lot of doubts about the centrality of "instances", but can't say clearly what's better rn)

But, specifically thinking about Ghost's announcement, I'm interested in hearing what people see as the issues and opportunities so will try to figure out how to keep up

Or an opening statement?

i spoke up because this is at least connected to what I've been thinking about, which is whether/when there's a value in a universal ActivityPub client and whether/when there's value in specialized AP apps tuned for distinct use cases.

I'm all for it. Is there any background reading I could do?

I've been thinking a lot about the modality differences between microblogging and forums, and still working out my thoughts, but I definitely agree that generic solutions end up failing everyone.

I'd like to believe that today's practice isn't yet so cemented that we can't aspire to better. I think there's a lot of interop work even among conceptually aligned projects -- there are a couple of FEPs i haven't digested yet, eg FEP-1b12: Group federation (as well as, I just found, one about URLs)

I think the targets I'm looking for are a unified feed that can fan out to specialized clients for detail, and a system that embraces the power of links with minimal friction. EDIT oh, and maybe something that makes it easier to follow specific people across different modalities without having to rediscover them -- although maybe that's adjacent to the topic of this thread

I was pointed to this proposal for fedi: from Tim Bray, which I'd missed, and found a commenter pointing back to this advocating for acct:, which leaves the question of linking to posts kinda vague

EDIT: adding FEP-07d7: A Custom URL Scheme and Web-Based Protocol Handlers for Linking to ActivityPub Resources ( discussion )

Thanks for the thoughtful response.

You can’t exactly expect the URL to indicate the type

Yes, this seems like one of the bigger hitches. I've never investigated, but I wonder if the git+ssh plan is formalized, and whether it is an option

A smarter app could detect the type of server responsible for managing certain things (i.e. when you’re following a Lemmy community, treat posts in it as such, and not as a flat timeline), …

Seems a mistake to me too imagine that the future of ActivityPub is servers limited to specific certain content types?

Need to think more about the client/server parts of your post, but again, thanks for taking the time

https://antidepressantsortolkien.vercel.app/