Let’s consolidate all issues with proof verification (“can’t find the snippet”) in this topic.
Right now, I’m aware of the issue with Instagram. Let me know what others you run into! This will help me either make the checking process more resilient or contribute to a list of known services where we’ll have to check for snippets manually.
@ame, still working on YouTube. Google’s not making it easy! I saw that your proof was still on the page, though, so I just took care of it manually for you.
@melanie, can confirm that this is an issue — ko-fi doesn’t like my automated browser setup. Hopefully this will be addressed when I have a better crawling option in the near future. Until then, if you want to add the proof snippet back to your page, I’ll be more than happy to verify it manually.
@chrismetcalf, looks like QRZ.com does some weird things with content population via JS, and proven.lol’s headless Chromium setup isn’t being served the full output (even with a 10 second affordance for DOM generation). Weird! I ran this through the manual verification process though, so you’re all set.
Putting a proven.lol link in an akkoma profile field(such as my akkoma profile) isn’t shown, as those are only populated when JS is enabled. Also, if the user bio is too long and you put the proven link at the end, it’s cut off. In this case, the first characters are shown in the site description, but if you put it at the end of a bio, it’s not shown in the description tag and cannot validate.
Let me know if I can help describe this a bit better.
They’re probably blocking inbound connections in the IP range where the omg.lol server runs — this happens from time to time. Eventually when I have the proof checking setup a little further along, we’ll hopefully be able to dodge that somewhat — but until then, I’m glad to verify it manually. I don’t see the snippet anywhere in the page source currently, but if you add it and let me know I can take care of it from there!