Welcome to the Power Users community on Codidact!
Power Users is a Q&A site for questions about the usage of computer software and hardware. We are still a small site and would like to grow, so please consider joining our community. We are looking forward to your questions and answers; they are the building blocks of a repository of knowledge we are building together.
Post History
Based on seeing other website auth and metadata protocols only, I'm expecting this to be of the form <head> ... <meta rel="me" href="https://mastodon..."> ... </head> . When I fe...
#1: Initial revision
by
mcast
·
2025-04-09T21:21:34Z (9 days ago)
Based on seeing other website auth and metadata protocols only, I'm expecting this to be of the form `<head> ... <meta rel="me" href="https://mastodon..."> ... </head>` . When I fetched the page and looked at the source (with curl or in Firefox dev), and I only see mention of `mastodon` further down, and there it is encoded in a `<div ... data-code="<a rel="me" ..." ...>` element which surely makes it invisible to anything doing meaningful authentication. You do have other metadata there, such as `<meta itemprop="description" content="Hi, I'm Mithical, a writer and community enthusiast. ">` so writing to head is possible; but these standard fields may be from a limited menu? I haven't looked at the docs for Mastodon or Google Sites. If you'll excuse my laziness in not going and finding them, then I'll excuse yours in not pasting the link in the question. 😜 > Now, by default, Google Sites turns links into a Google redirect (i.e. it doesn't link directly to the target page, but links to `google.com/url?=linkwithatracker` instead. Ugh. I guess it's to reduce splog referrer farms? Sure seems like the wrong way to do that. However that didn't apply to the `<meta itemprop="url" content="https://www.superplane39.com/">` you have. Again, possibly generated from a limited menu. > If you embed a link within HTML, though, it does link directly to the page that you want. It's encoded for the consumption of Javascript; which when I visited with NoScript didn't even run. I think it's invisible there.