@jon You can follow me on BlueSky as @james.crid.land - and here on Mastodon by searching for @james@crid.land (which mostly works). Disappointingly, therefore, this isn’t going to fly…
Top-level
@jon You can follow me on BlueSky as @james.crid.land - and here on Mastodon by searching for @james@crid.land (which mostly works). Disappointingly, therefore, this isn’t going to fly… 5 comments
@opendna @jon @james@crid.land Oh, thank you. What path does the ActivityPub API look for, so I can forward that? (I do the .well-known on those two domains anyway) @james@bne.social @jon @james@crid.land As far as I can tell (on mobile), ActivityPub behaves as expected. It just doesn't failback to html for non-ActivityPub browsers. I'll take a look later. @opendna @jon @james@crid.land I don't forward the base URL. There is an old (cached in some places) result for James(at)crid.land which once lived at socl(dot)crid(dot)land - which broke - and I'd love to somehow clear the fediverse's cache. It doesn't show up on my home server but does in other places. I'm curious to work out how I can convince it to go away. @james @jon The cache auto-expires after enough time (weeks or months, depending on the host). You have active .well-know for every combination of domain and subdomain I tested, but they're not all the same. All the jon@ Mastodon queries point to your bne account, which is expected behavior. Your sites all seem ActivityPub-compliant to me. The only reason OP's suggestion doesn't work for you yet is that you don't have a non-ActivityPub landing page on the base domains. |
@james@bne.social @jon @james@crid.land It would work fine if you fixed your dns so crid.land and cridland.net forwarded to the active subdomain instead of returning an Error 403.