Anyway, here's my thought: make collection pages real, stable objects, with fixed contents and real modification dates. Return only references, not embedded objects. Do filtering, though. And make pages big -- 100 items or more.
@evan mastodon’s approaches is interesting in this regard, it returns embedded objects for local items, and references for remote objects. Best of both
@django it's good in some ways, but they still don't return Last-Modified headers.
@shinmera oh I missed that, awesome!
@shinmera There is only a proposal:
@shinmera GoToSocial has a Mastodon migration tool, I see it’s archived though https://github.com/VyrCossont/slurp/
@shinmera when my main acces domain moved from mastodon to social I just changed the settings and made everything redirect there. Probably only broke the I stances that can't handle webfinger and the alias domain stuff thingy
@technical-discussion @julian @Edent @silverpill I think it is @melvincarvalho
@django @technical-discussion @julian @Edent @silverpill yes socialdocs is something i help look after. Anything needed?
@julian I can read the outbox and activities 👍
There is a minor problem with Like activities, which don't have a to field (this means nobody should be able to see them).
And while we're at it: when NodeBB sends a signed GET request, does it add a Digest header? I see warnings in my log due to invalid header value.
Starting in Firefox version 142, Mozilla released a “Link Previews” feature.
While the feature is problematic, commenters post pointed out that some previews are helpful – e.g. on Wikipedia, where a preview will appear when people hover over a wiki-linked page.
Other commenters pondered about some minimal way to replicate this elsewhere, and it seemed to be worth investigation. Read on as I propose an enhancement to the Fediverse (and maybe even web standards) to make Link Previews great: the Link Preview Manifest.
One thing that I neglected to mention is that since the SRI hashes are calculated, previews can be cached by peers other than the originating host - since they are verifiable, anyone can pass them along and the client can verify the payload.
Not something I really fleshed out in discovery, but if there is interest, that might make it more production ready.
Man, I am a cranky bastard sometimes. Shouldn’t post when I’m tired.
How about - the origin server, the place where the post was originally created, gets all the metadata (og:image, og:title, etc) and includes that in the Activity that tells other instances about the post? That way there is only one request made to the link and receiving instances can use that to make their preview?
It does mean that receiving instances will need to trust the sender so there’s potential for some misrepresentation but that seems acceptable to me.