310
results for "alternate"
-
[preview] [snarfed] @kwaa reminded me in https://github.com/snarfed/bridgy/issues/1441 of an alternative approach for original post URLs, instead of serving or redirecting to AS2 based on conneg: add `<link rel="alternate" type="application/activity+json" href="https://...
Loqi
at
2023-03-23 20:21
-
I'd love to see something come of this. I have been doing an overhaul of the recrawl logic for IndieWeb search and ran into a bit of an issue with how exactly I should go about identifying rel="alternate" h-feeds.
capjamesg[d]
at
2021-10-01 11:39
-
[Rose] I was adding another show to my video page and it has me thinking, wow I do put feeds everywhere, I have rel=alternate links in my header to places everywhere, links to webpages with feeds in my h-card cuz why not, feeds for every single video show on my video page, and feeds to common hashtags in the footer of my Known blog
[jgmac1106]
at
2020-02-06 22:37
-
things like rebuilding all tag pages (and archives) are why i want to have more control over when things happen. first build and publish the permalink page and start sending webmentions. then update any "main" feeds (and send websub notifications). then start the longer process of building out alternate views like tags, archives, indexes, ...
[schmarty]
at
2021-04-29 18:52
-
Srcset looks promising because the social sharing ratios are typically wide (like 1.91:1 in FB’s case) and that coincidentally has the same cropping and scaling issues as large images on laptops, so you could make those wide images the default and then have backup alternate images that are square or tall to uncrop them for mobile, tablet, etc.
[Al_Abut]
at
2024-02-12 20:12
-
cal, for your case I think that most in the community here would consider the copy that @threadreaderapp posts to one's website to be the canonical version (and it would likely be marked up on most CMS platforms as such), and the copie(s) that live on Twitter and on the threadreader website to be alternate copies.
[chrisaldrich]
at
2020-03-15 01:18
-
i guess i am saying a lot of little misgivings about this aloud, but let me work it a different way: there are a couple of examples of consuming cases for this (e.g. jamietanna's self-configuring client). are there alternate approaches that might make more sense than coding up a discovery service centered inside the micropub server?
[schmarty]
at
2022-10-18 19:13
-
[tantek] it is a good question though. for this counting, should we identify h-feed support as just the presence of an h-feed element on the home page? and/or rel-alternate with type text/html? (not sure how many of those in practice would be h-feeds...?)
[snarfed]
at
2021-09-27 19:41
-
snarfed, does this mean we need to be recommending rel="feed" (thought it was rel=alternate with type="..." (some feedtype) for both RSS2 and Atom?) for h-feed as well, even if the href is to a "#stream" element right there on the home page?
[tantek]
at
2021-09-27 18:21
-
jacky, I wouldn't use rel=alternate on a link to something you don't control / own, or rather, something where another party (owner) could change the content arbitrarily. E.g. exceptions might be an IPFS copy of the page/post, or perhaps more useful/reliable, the internet archive snapshot of your post, but only if you're already linking to it for other (user-centric) reasons
[tantek]
at
2022-03-19 22:33