It would be good if Mastodon have some sort of cache for those.
(and I have 0 idea how ANYTHING in Mastodon works, so I might be "talking s**t")
Just an idea.๐ค
this post was submitted on 27 Aug 2024
2 points (100.0% liked)
News from fediverse
0 readers
1 users here now
founded 10 months ago
MODERATORS
@[email protected] the issue is, every server that the link lands on, requests a link preview. My instance is federated with 15,000+ instances.
There's not really a way, that I know of, to cache something like that cause each link is different and could be new to the instance or just a new link altogether.
Can't cache something that hasn't existed before.
Thank you for explanation.๐
As I said before I don't know anything from internal working of Mastodon.
(I might be completely wrong and saying something stupid, as I do most of the time ๐)
Could it be possible to transfer "link preview" inside the toot?
What I mean - server on which toot was created would also create "link preview" and distribute it with toot.
@[email protected] that's a good question I didn't think of, when you mentioned caching. I was under the impression you meant caching in a traditional sense. Because normal caching is done on a per server basis.
My cache doesn't interact with anyone else's cache.
@[email protected] @[email protected] Yes this is possible and I think it's been discussed as a solution. The concern, last time I was reading about it, is that malevolent servers could poison a link preview and send fake images along with the url (the argument against this is you're already 'trusting' the server if you're federating with them, so that trust should extend to link previews)
Another proposed solution was just having servers wait a random amount of time before fetching the link preview so not every server is requesting the preview at the same time
@[email protected] @[email protected] there is, but the issue could be...
I share a link to a site. My instance generates a preview card and caches it, then my post gets federated to 5k additional servers, but only the URL, not the cached preview card. So other instances generate their own preview cards and cache them.
Individual viewers are not necessarily creating extra traffic, but each instance is.