Föderation DE Fr 02.08.2024 12:01:10 One reason why previous social media is difficult to replace with the Fediverse is the fact that images eventually stop loading. This occurs with both @pixelfed and @Mastodon . Unfortunately, the visibility of posts is not permanently guaranteed and societies & organisations are even harder to convince when they see something like this. (Medien: 1) |
Föderation · Fr 02.08.2024 12:19:18 @Real Social Networks Good thing Friendica, Hubzilla and the streams repository work so much differently.
For starters, unlike Mastodon, Pixelfed and probably others, the instance cannot force-delete your content against your will. Not your posts and not the images and other files in your file storage either. You and you alone decide what's being deleted when, if at all. Posts and DMs from outside are being deleted after a certain period. You can shorten it for yourself. But when you have interacted with something (replied to it, liked it, starred it, repeated it, saved it in a folder), it will not be deleted. Comments from outside are only automatically deleted along with the posts they comment on. On Friendica, Hubzilla and (streams), you are the owner of the whole thread following any of your posts, all comments included, and you decide what'll happen to the comments. If you don't delete the post or have it automatically deleted, all comments will persist along with the post unless you manually delete them independently from the post, one by one. Unfortunately, this does not translate to Mastodon which entirely relies on downloading and caching everything. So even if you keep your posts and your pictures and everything indefinitely, Mastodon instances will eventually purge them from their caches. Vice-versa, while Friendica, Hubzilla and (streams) keep copies of posts, comments and DMs, they don't cache images and hotlink them instead. So when an image is purged from a Mastodon or Pixelfed instance, they can't show it anymore either because it's gone at the source. #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Pixelfed #Friendica #Hubzilla #Streams #(streams) |
Föderation EN Fr 02.08.2024 13:38:27 Yes, this has been flagged beforeβI was told a while ago it had been fixed but it clearly hasn't. If a toot with media is shown when the cached media (on the instance being viewed) has expired, it should be re-fetched from the originating instance, or perhaps some kid of notice added or the whole toot removed if the original is unavailable. If it worked like that, #MastoAdmin folks could set their caches to expire earlier, too. |
Föderation EN Fr 02.08.2024 13:41:12 @tokyo_0 @fediverse_connection We really need that to work! |
Föderation EN Fr 02.08.2024 15:12:34 @tokyo_0 @fediverse_connection @andypiper If you haven't already, please consider opening an issue on Github so it can be fixed. |
Föderation EN Fr 02.08.2024 18:28:44 @legume I think multiple people have already. I've seen people talking about it in the past and I'm pretty sure I've seen Github issues linked. I guess if we could just go and browse the few open issues it'd be easy to know for sure, but there seem to be 3,791 open. @fediverse_connection @andypiper |
Föderation EN Fr 02.08.2024 16:55:04 @tokyo_0 @fediverse_connection @pixelfed @Mastodon @andypiper they should refetch if the media has been pruned. |
Föderation EN Fr 02.08.2024 18:26:33 @colinstu Yes, they should. They don't, but they should. @fediverse_connection @pixelfed @Mastodon @andypiper |
Föderation EN Fr 02.08.2024 18:46:09 @tokyo_0 @fediverse_connection @pixelfed @Mastodon @andypiper anything get logged? Have not encountered this issue. Github link on issue? Not finding it. |
Föderation EN Fr 02.08.2024 18:59:43 @colinstu I don't run an instance, so I have no idea what the log says. And it's kind of a fallacy to suggest this would actually be any different based on whether a github issue was open or not. Github issues for Mastodon have been open for literal years without ever being taken seriously. It's hard to imagine anyone involved in Mastodon development doesn't see this in their feed the same way I and others do. @fediverse_connection @pixelfed @Mastodon @andypiper |
Föderation EN Fr 02.08.2024 19:07:55 @tokyo_0 well if it's been fixed then the issue would've been closed. If the issue is still open then I would expect the issue to persist. Was curious to find out why the issue would still be around / what folks are reporting as a cause. Not saying it's a fallacy, I just want to learn more about this issue. It could be an instance-specific issue? I wouldn't put it past them for never seeing it, especially if it's never been reported on GH. |
Föderation EN Fr 02.08.2024 19:15:23 It's not specific to an instance. It's been happening at least since November 2022 (in terms of what I've seen personally). When people talk about it, they're often dismissed with comments like "it should refetch". But I'm not sure which Mastodon instances people are using that they don't see this routinely. |
Föderation EN Fr 02.08.2024 19:15:37 Re Github, I had a look, out of curiosity. Here are some open issues related to media not showing or being refreshed correctly: https://github.com/mastodon/mastodon/issues/9668 - opened Dec 2018, closed but not resolved https://github.com/mastodon/mastodon/issues/21625 - opened Nov. 2022, no comments, updates or triage, remains open and unresolved. |
Föderation EN Fr 02.08.2024 22:27:32 @tokyo_0 @colinstu @fediverse_connection thanks for digging these up. I do not know what the status is on this, but I can certainly confirm that I've seen the issue myself (my three pinned posts all seem to have that problem with media from links, for example); I do not run my own instance so I can't check the logs. We're hard at work on the 4.3 release at the moment, but I will see if we can look into it at some stage. |
Föderation DE Fr 02.08.2024 19:07:18 @fediverse_connection@vivaristics.net @pixelfed@mastodon.social @Mastodon@mastodon.social Welcome to the real world societies & organisations β |