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
There are at least a couple of Riverworld attempts. Haven’t seen either
https://en.wikipedia.org/wiki/Riverworld_(2003_film) https://en.wikipedia.org/wiki/Riverworld_(2010_miniseries)
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