@Glorfindel Can you please exempt your broken image fixer script from fixing old automatic bounty community promotion ads?
Those images were dynamic by nature and having them replaced with a static copy isn't helpful.
I've pinged the maintainer of that ad in a comment. If they don't respond or if they respond saying it's dead, would someone else like to make a new version? @rene perhaps?
@JourneymanGeek think it's finally dead for real, it didn't even onebox xkcd which is new (negative) record.
@Spevacus glad you like it! :D
@EleezatheOtherWorldWizard yeah, @SPA is evangelist of it, which is fun to see, and some results aren't so terrible. ;)
@NordTheStarWizard the danger isn't the AI, it's the people misusing and abusing it in terrible ways. Using something meant for casual chats to write actual essays for you is clear example of that abuse, and it will only get worse.
@EleezatheOtherWorldWizard it's not, it has been removed. But I think someone copied the code into some external site, will look later if I won't forget.
@SonictheAnonymousHedgehog what are you talking about? You commented on wrong post, there's no mention of any application so most likely that person won't have any idea what you mean either.
@ShadowWizardChasingStars One of my posts on Puzzling Meta (a post of that bounty ad to the 2019 Community Promotion Ads there) was edited by his script today
@ShadowWizardChasingStars No, it's not a static image. They ran an application that would serve a dynamically-generated image to indicate the number of active bounties on a given site. That application seems to have gone down, resulting in broken images on older Community Promotion Ads answers and the inability to use it in the future.
@JourneymanGeek If the application subsequently goes up again (if the original maintainer brings it online or someone else acquires the domain), these posts that were edited to have static archived copies will need to be mass rolled back.
Much better to replace it with text indicating it formerly contained a dynamic image but that it's broken now that the application serving it has gone down.
en.wikipedia.org/wiki/Heroku "In August 2022, Heroku announced that its free plans would be discontinued, citing fraud and abuse as reasons for the change, leaving many customers upset.[14]"
@ShadowWizardChasingStars Heh, I'll be honest, I've used Dall-E before to generate some background references and things, and it works quite nicely, but other than that...well my mixed feelings lean slightly towards the negative :,)
Oh also! I finished vocals for that song I sent the other day, if it's okay for me to send here?
@JourneymanGeek we don't have a way to know if a status review is actually on the board for the team, right? Like this one for example: meta.stackexchange.com/q/295173
@SonictheAnonymousHedgehog so you want Glorfindel to leave broken images around just because it's dynamic? I don't think that's a good idea. It does not matter why it's broken.
If whatever generates it is ever fixed, you can always edit back the dynamic image.
@EleezatheOtherWorldWizard awesome!!
@rene with 4200 items network wide, it really won't matter, it's just a drop in ever growing sea.
And it's literally months since I saw even a single bug fixed outside their planned projects.
So as time goes by, I can see how the whole concept of the review queue is dwindling into the void.
So, there is only one possible conclusion, one thing to do. Last resort. I hate to do that, but....
@JourneymanGeek I look for status-completed tags. They do fix bugs in the new features they push, true, but there are hundreds of other bugs awaiting a fix, with status-review on them, and it just keeps growing, never shrinking.
In the past they had developer on 'bug watch", who could pick bugs from the queue and fix them, that's simply gone.
Also, some monthly stats about the percentage of status-review being, well, reviewed, and needless to say that also stopped, they won't put "0% done". lol
Much better to replace it with text indicating it formerly contained a dynamic image but that it's broken now that the application serving it has gone down.