Probably something that could be submitted to github somehow if I cared enough to sign into that account, if someone else wants to snipe this go ahead.
Anyways facebook sources on here are often gross links like https://www.facebook.com/DateALiveFC/photos/rpp.142604822590116/776432789207313/?type=3&theater which has a whole lotta junk data that isn't super relevant. You can however hop over to the post and go through some boring back and forth pagination wizardry to get the URL https://www.facebook.com/photo/?fbid=776432789207313&set=rpp.142604822590116 which is still kinda gross, but can then get normalized by Danbooru to just be https://www.facebook.com/photo?fbid=776432789207313. As you may have noticed, all the data to get those second and third link versions are all there in that first link.
So, hypothetically, when given a URL formatted
https://www.facebook.com/PAGENAME/photos/bunchanumbers/photoid/?unecessarytrackingdata=anddisplayformatstuff
you can pretty easily get to
https://www.facebook.com/photo?fbid=photoid&set=bunchanumbers
or just https://www.facebook.com/photo?fbid=photoid
without even having to potentially get jumpscared by AI shrimp jesus posts.
i dont know what the bunchanumbers there is meant to indicate tbqh. it doesn't seem to match the internal numerical ID of the facebook page or anything.
I've just been doing this manually by going through the posts using my old facebook account from high school (gross) for like 20 posts or something, but considering there's a way to fanangle it out of the URLs as-is I'm gonna pause and let Daniel Booru decide if anything on the backend wants to happen in this regard. Or of some other random user feels like messing around with a mass-updating bot, idk.
