{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
- 2y ·
-
Public·
-
mastodon.social
@atomicpoet Something has to change about how link previews are generated.
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@atomicpoet Something has to change about how link previews are generated.
@Gargron @atomicpoet why not compute them at poster's instance and then just publish the metadata found?
@Gargron @atomicpoet Is there a way to make them grab from the nearest server to them geographically and spread them from the main instance outward? Then no one is taking too much of a hit at any given time.
Like how windows updates work.
Have each instance keep a cache for a certain period of time, removing entries after a week or so?
I won't pretend I understand how to set that up though.
@Gargron @atomicpoet
is it possible to pre-generate them on receipt of post? clients can refresh them on viewing if needed.
@Gargron @atomicpoet since the *link* to the source post and/or other media is included, why *not* trust the originating instance's preview? If trust is an issue, the *link* can be followed later to verify.
If an added technical feature is needed, it should be a toggle flagging the post for inaccurate preview. That would likely shut down distribution, and problem solved.