currently, I am running a script to clean up tags related to source_request, unavailable_at_source, and crossed out sources.

logic runs like :
if a post has source crossed out, tag unavailable_at_source and source_request
if a post has one or more source, but does not have unavailable_at_source, remove source_request

aiming to clean up post that are re-sourced and posts that lost source

Discord direct attachment links may appear to be "unavailable", but this is due to the some shenanigans with the authentication parameters attached to the links.
Placing the direct links back into Discord (e.g., a random chat) and re-copying the links would make them (temporarily) available again and not necessarily "unavailable_at_source".

I don't think source_request should be used for posts that at one point had a valid source.

Also you said "a" source crossed out, hopefully you mean all. Still not a good idea, though.

quite a few discord sources starts with '-' which crosses out while displaying, I would trust who marked them with '-' on source prefix meant to mean that particular source is unavailable. I also did some due diligence and checked a few, they are all no longer available.

scth said:
I don't think source_request should be used for posts that at one point had a valid source.

Also you said "a" source crossed out, hopefully you mean all. Still not a good idea, though.

my apologies, it's all source.

so you do mean:
once had a valid source, but no longer -> unavailable_at_source
never had a source -> source_request

but source_request are reapplied once links become invalid again by some, and it is reasonable to do so.

thegreatwolfgang said:
Discord direct attachment links may appear to be "unavailable", but this is due to the some shenanigans with the authentication parameters attached to the links.
Placing the direct links back into Discord (e.g., a random chat) and re-copying the links would make them (temporarily) available again and not necessarily "unavailable_at_source".

actually, checked some of the newer ones, and it's true that when pasted in Discord it would appear back as an image. it is somewhat tricky since the tagging of '-' in front of source seemed automated too.

eiffelwong1 said:
actually, checked some of the newer ones, and it's true that when pasted in Discord it would appear back as an image. it is somewhat tricky since the tagging of '-' in front of source seemed automated too.

That's because it (kinda) is, by @Donovan_DMC

eiffelwong1 said:
so you do mean:
once had a valid source, but no longer -> unavailable_at_source
never had a source -> source_request

Yes. Otherwise they have effectively the same meaning, since unavailable_at_source should only be used if all sources are unavailable. It was also from my interpretation of the source_request wiki, since "knowing where an image came from" has been satisfied.

Although, the wiki for unavailable at source does seem to agree with your interpretation.

scth said:
Yes. Otherwise they have effectively the same meaning, since unavailable_at_source should only be used if all sources are unavailable. It was also from my interpretation of the source_request wiki, since "knowing where an image came from" has been satisfied.

Although, the wiki for unavailable at source does seem to agree with your interpretation.

I wonder if we can find some staff on this topic, making it either way wouldn't be difficult

snpthecat said:
That's because it (kinda) is, by @Donovan_DMC

I run a script every so often which parses the url parameters to check if the url is expired yet, and if so it sanitizes the parameters (they're useless after expiration), and disables the source
These expire after 24 hours so it's very quick

donovan_dmc said:
I run a script every so often which parses the url parameters to check if the url is expired yet, and if so it sanitizes the parameters (they're useless after expiration), and disables the source
These expire after 24 hours so it's very quick

currently, I skip handling posts with sources starts with 'https://cdn.discordapp.com/attachments'
where they remain crossed out, but no unavalible_at_source nor source_request is added